{"id":21377,"date":"2026-06-16T10:01:48","date_gmt":"2026-06-16T14:01:48","guid":{"rendered":"https:\/\/notes.math.ca\/article\/on-finding-inverse-functions-and-the-swap-and-solve-disconnect\/"},"modified":"2026-06-16T10:28:38","modified_gmt":"2026-06-16T14:28:38","slug":"on-finding-inverse-functions-and-the-swap-and-solve-disconnect","status":"publish","type":"article","link":"https:\/\/notes.math.ca\/fr\/article\/on-finding-inverse-functions-and-the-swap-and-solve-disconnect\/","title":{"rendered":"On Finding Inverse Functions and the \u00ab\u00a0Swap and Solve\u00a0\u00bb Disconnect"},"content":{"rendered":"

The Procedural Trap vs. The Conceptual Reality<\/strong><\/p>\n

In mathematics classrooms in North America, an algebraic techniques is deeply entrenched as the standard algorithm for finding an inverse function: \u00ab\u00a0Switch \ud835\udc65 and \ud835\udc66, then solve for \ud835\udc66.\u00a0\u00bb While algebraically efficient in simple, unconstrained linear cases, this mechanical routine frequently strips away the actual meaning of the function. It leaves both students and teachers disoriented when they encounter domain restrictions or real-world contexts where variables hold fixed meanings (Paoletti et al., 2018).)<\/p>\n

The conceptual reality is that an inverse function reverses the process of the original function – it maps outputs back to their original inputs. When instruction prioritizes procedural fluency over this logical foundation, the switching technique turns into a mathematical \u00ab\u00a0trick\u00a0\u00bb rather than a structural consequence. In fact, what escapes most students and teachers who rely of the swapping procedure is that it \u201cworks\u201d based on the mathematical definition if inverse.<\/p>\n

Furthermore, this procedural focus often breeds a deeper cognitive avoidance of non-invertibility. For instance, when presented with a quadratic function over an unrestricted domain \u2013\u00a0 such as \ud835\udc53(\ud835\udc65)=(\ud835\udc65+1)\u00b2\u00a0 for all real numbers \u2013 many students and teachers experience a strong resistance to declaring that \u00ab\u00a0the inverse does not exist.\u00a0\u00bb Instead of recognizing that the function fails injectivity, they often succumb to a \u00ab\u00a0space of fuzziness,\u00a0\u00bb providing a \u00ab\u00a0slanted parabola\u00a0\u00bb or writing down a flawed +\/\u2212 \u00a0square root expression (Marmur & Zazkis, 2018). Even those who recognize the issue often feel compelled to artificially restrict the domain on the spot just to avoid the claim of inexistence and revert to the known algorithm.<\/p>\n

To explore what happens when a domain restriction is an inherent part of the problem, let us analyze a specific illustrative example that exposes the fragility of procedural automatism.<\/p>\n

Consider the following problem: Find the inverse function of \ud835\udc53(\ud835\udc65)=(\ud835\udc65+1)\u00b2 given the restricted domain \ud835\udc65 \u2264 \u22122.<\/p>\n

Mathematically, there is no difference in the underlying logic whether one chooses to express the variable first or swap them first in case when variables hold no fixed meanings. However, the order in which a solver executes these procedures fundamentally alters the cognitive load and the visibility of the functional relationship. How do you expect your students will approach the task? For our students, the swapping approach appeared to be a preferred one, which often led them astray.<\/p>\n

Swapping \ud835\udc99 and \ud835\udc9a first (The Procedural Trap)<\/strong><\/p>\n

We have observed the cognitive stupor that frequently occurs when a student immediately applies the school curriculum convention of swapping the variables at the very first step:<\/p>\n

\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \ud835\udc65=(\ud835\udc66+1)\u00b2<\/strong>\u00a0<\/p>\n

The goal is now to isolate the \u00ab\u00a0new\u00a0\u00bb y and state the domain of the inverse. It is precisely here that the technique often breaks down into disconnected silos:<\/p>\n