Reframing

Most teams solve the wrong problem faster than they'd solve the right one slowly. Reframing is the discipline of restating a problem from a fundamentally different angle — shifting the boundaries, the stakeholders, the assumed constraints, or the level of abstraction — to ensure you're directing effort at the thing that actually matters. Use it before any significant resource commitment, whenever the obvious framing feels too comfortable, or when a team has been stuck on the same problem for weeks without progress.

The most expensive mistake in decision-making isn't choosing the wrong solution. It's solving the wrong problem. A brilliant answer to a misframed question doesn't just waste resources — it creates the illusion of progress while the real issue compounds underneath. And the insidious part: the better the team, the faster they converge on a solution, which means the cost of a bad frame scales with organisational competence.

Consider the classic case. An elevator company receives complaints that wait times are too long. The engineering frame: faster elevators, better scheduling algorithms, additional shafts. All expensive. All slow. A reframe — "People are bored and self-conscious while waiting" — leads to mirrors in the lobby. Complaints drop. The problem was never speed. It was the experience of waiting. This story has been told so often it risks sounding like a parable, but the underlying dynamic plays out in boardrooms every week. A SaaS company frames declining revenue as a sales problem and hires more reps. The actual problem is that the product's onboarding flow loses 60% of trial users in the first three days. A hospital frames long emergency room waits as a capacity problem and builds a new wing. The actual problem is that 40% of ER visits are non-emergencies that could be handled by a nurse triage line. Same pattern. The initial frame feels obvious, which is precisely why it goes unquestioned.

Reframing works because it attacks a specific cognitive vulnerability: once a problem is stated, the human brain treats the statement as a constraint rather than a hypothesis. The frame becomes invisible — like the edges of a window you're looking through. You see what's inside the frame and forget that the frame itself was a choice. Psychologists call this "problem fixation" or "functional fixedness." Kahneman would recognise it as a form of anchoring: the first formulation of the problem anchors all subsequent thinking, and even experienced decision-makers adjust insufficiently from that anchor.

The mechanism is straightforward but requires deliberate effort. You take the current problem statement and systematically generate alternative framings — by changing the stakeholder perspective, by moving up or down the abstraction ladder, by questioning the embedded assumptions, by inverting the goal, by redefining what "success" means. You don't discard the original frame. You hold multiple frames simultaneously and ask which one, if solved, would create the most value. That comparative evaluation is the core of the technique. It's not brainstorming. It's not lateral thinking in the vague, "be creative" sense. It's a structured interrogation of the problem itself before you spend a single hour on solutions.

The tool has roots in multiple traditions. Cognitive psychologists like Karl Duncker studied problem reformulation in the 1940s. Design thinkers at Stanford's d.school and IDEO formalised it as a core practice in the 1990s. Thomas Wedell-Wedellsborg brought it to a mainstream business audience with his 2017 Harvard Business Review article "Are You Solving the Right Problem?" and his subsequent book. But the practice is older than any of these codifications. Every great strategist — from military commanders to venture capitalists — has intuitively understood that the quality of the question determines the ceiling of the answer.