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.
Section 1
What This Tool Does
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.
Section 2
How to Use It — Step by Step
Instructions on the left. Worked example — a mid-stage B2B software company whose board is concerned about slowing growth — on the right.
Step 1 — State
Write down the problem as currently understood
Before you can reframe, you need to see the existing frame clearly. Write the problem statement as the team currently understands it — the version that would appear in a board deck or a Slack message to leadership. Be precise. Include the metric, the stakeholder, and the implied solution direction. The goal isn't to fix this statement yet. It's to make the frame visible so you can examine it.
Worked example
B2B software company — initial frame
"We need to increase our new logo acquisition rate. Net new customers per quarter has declined from 45 to 28 over the past three quarters, and the board wants a plan to return to 45+ by Q3." The implied solution direction: more pipeline, more sales reps, better marketing. The embedded assumption: growth comes from new customers.
Step 2 — Dissect
Identify the assumptions embedded in the current frame
Every problem statement contains hidden assumptions — about who the stakeholder is, what the constraint is, what "solving" means, and what's in scope. List them explicitly. Ask: What does this statement take for granted? What would have to be true for this framing to be the right one? What has been excluded? This step is where most of the leverage lives. You can't question assumptions you haven't surfaced.
Worked example
Surfacing hidden assumptions
Assumptions embedded in the current frame: (1) Growth = new logos, not expansion of existing accounts. (2) The decline is a sales/marketing problem, not a product or market problem. (3) The historical rate of 45/quarter is the right benchmark. (4) All new logos are equally valuable. (5) The board's metric (new logos) is the right metric for the company's actual health. Each of these is a choice masquerading as a fact.
Step 3 — Reframe
Generate 3–5 alternative problem statements
Use specific reframing lenses to produce genuinely different framings — not minor variations. Useful lenses: Stakeholder shift (whose problem is this really?), Abstraction shift (is this a symptom of a higher-level problem?), Inversion (what if the opposite were true?), Boundary shift (what if we expand or narrow the scope?), Goal redefinition (what if success means something different?). Each alternative frame should suggest a fundamentally different solution direction. If two frames lead to the same set of actions, they're not different enough.
Worked example
Five alternative framings
Frame A — Expansion: "Our net revenue retention is 98%, meaning existing customers aren't growing. The real growth opportunity is expanding within our 340 current accounts, not acquiring new ones." Frame B — Churn: "We acquired 45 logos per quarter but were also losing 12. The decline to 28 net new may partly reflect rising churn, not just slower acquisition." Frame C — Market fit: "Our win rate on deals over $80K has dropped from 35% to 18%. We may be losing in a segment where our product no longer fits, not failing to generate enough pipeline." Frame D — ICP drift: "60% of our new logos in the past two quarters churned within 8 months. We're acquiring the wrong customers, not too few customers." Frame E — Metric: "The board is tracking new logos, but our business model depends on expansion revenue. The right metric is net dollar retention, not new logo count."
Step 4 — Evaluate
Compare frames by asking which one, if solved, creates the most value
Lay the original frame and all alternatives side by side. For each, ask: If we solved this version of the problem, what would the impact be? How confident are we that this is the real problem? What evidence supports or contradicts this framing? What would we do differently if this were the frame we adopted? The goal is not to pick the "most creative" reframe. It's to pick the most accurate one — the frame that best describes what's actually happening and points toward the highest-leverage intervention.
Worked example
Comparative evaluation
Frame A (expansion) is supported by data: NRR of 98% is below the 120%+ benchmark for healthy B2B SaaS. Frame D (ICP drift) is alarming: if 60% of recent new logos churn within 8 months, the acquisition engine is actively destroying value — each churned customer costs roughly $14K in fully loaded acquisition cost with zero payback. Frame C (market fit) explains the declining win rate. The team realises Frames C and D may be connected: they're losing upmarket deals because the product doesn't fit, and winning downmarket deals that churn. The original frame — "acquire more logos" — would accelerate this destructive pattern. The reframe that creates the most value: "We're acquiring the wrong customers and under-expanding the right ones. The growth problem is a targeting and expansion problem, not a volume problem."
Step 5 — Commit
Adopt the new frame and redesign the solution space
Once the team aligns on the most accurate frame, rewrite the problem statement and use it to scope the solution search. The new frame should change what you measure, who you assign to the problem, and what solutions are on the table. If the reframe doesn't change the solution set, it wasn't a real reframe — it was wordsmithing. Communicate the new frame explicitly to all stakeholders, including the board. The hardest part of reframing is often political: telling a board that their metric is wrong requires courage and evidence in equal measure.
Worked example
New problem statement and solution direction
New statement: "Our growth engine is targeting the wrong customer segment and under-investing in expansion within our best-fit accounts. We need to redefine our ICP, stop acquiring customers who churn within 8 months, and build an expansion playbook for our 340 existing accounts — targeting NRR of 115%+ within four quarters." Solution direction shifts from "hire more SDRs" to "tighten ICP criteria, build customer success-led expansion motions, and present the board with NRR as the primary growth metric." Entirely different resource allocation. Entirely different team structure. Same company, same data — different frame.
Section 3
When It Works Best
✓
Ideal Conditions for Reframing
Dimension
Best fit
Problem type
Persistent problems that resist repeated solution attempts. If a team has tried two or three fixes and the problem keeps recurring, the issue is almost certainly the frame, not the solutions. Reframing is also essential for novel, ambiguous situations where no established frame exists — new markets, unfamiliar competitive dynamics, or strategic inflection points.
Decision stakes
High. Reframing is overhead — it slows you down before it speeds you up. That trade-off only makes sense when the cost of solving the wrong problem is significant: major capital allocation, product strategy pivots, organisational restructuring, market entry decisions. Don't reframe which coffee machine to buy for the office.
Team dynamics
Most powerful when the team includes people with different functional perspectives — a finance lead, a product manager, a customer-facing rep, an engineer. Each person carries a different default frame. The collision between those frames is where the insight lives. Homogeneous teams tend to converge on the same reframe, which defeats the purpose.
Information environment
Works best when data is available to evaluate competing frames but hasn't yet been marshalled to do so. Reframing often reveals that the data you need to assess the new frame already exists — it just wasn't being looked at because the old frame didn't call for it. The B2B company in the worked example had churn data all along; nobody connected it to the acquisition problem because the frame didn't invite that connection.
Section 4
When It Breaks Down
⚠
Failure Modes
Failure pattern
What goes wrong
What to use instead
Reframing as procrastination
Teams use reframing to avoid committing to a course of action. Every proposed solution triggers another round of "but are we solving the right problem?" The tool becomes an infinite loop of redefinition. At some point, the frame is good enough and the cost of delay exceeds the cost of a slightly imperfect frame.
Reversible vs. Irreversible Decisions to assess whether the decision warrants further deliberation, or whether you should act and iterate
Reframing without evidence
Alternative frames are generated through pure speculation — clever-sounding reformulations that aren't grounded in data or customer reality. The team picks the most intellectually appealing frame rather than the most empirically supported one. Reframing becomes a creative writing exercise.
5 Whys or Ishikawa Diagram to ground the analysis in observable causes before reframing; The Mom Test for customer-facing problems
Contrarian reframing
The reframe is adopted because it's surprising, not because it's accurate. There's a seductive quality to the counterintuitive — "what if the problem isn't X but actually Y?" — and teams can mistake novelty for insight. Sometimes the obvious frame is obvious because it's correct.
The most dangerous failure mode is reframing without evidence — and it's dangerous precisely because it feels like the tool working. The team generates a provocative alternative frame. It sounds smart. It reinterprets the data in a novel way. Everyone gets excited. But nobody checks whether the reframe actually maps to reality. The B2B company in the worked example could have reframed their growth problem as "our brand isn't strong enough" — a plausible-sounding frame that would have led to an expensive and irrelevant brand campaign. The difference between a useful reframe and a seductive one is evidence. Every alternative frame should be treated as a hypothesis, and the evaluation step (Step 4) should be ruthlessly empirical. Pull the data. Talk to customers. Check the churn cohorts. The reframe that survives contact with evidence is the one worth adopting.
Section 5
Visual Explanation
Section 6
Pairs With
Reframing is a problem-definition tool. It tells you what to solve, not how to solve it. The tools you pair it with determine whether the reframe leads to action or just a better-worded problem statement.
Use before
Abstraction Laddering
Abstraction Laddering asks "why?" to move up to a more abstract problem and "how?" to move down to a more concrete one. Use it as a structured input to reframing — it systematically generates problem statements at different levels of abstraction, giving you raw material for the reframing session rather than relying on unstructured brainstorming.
Use before
5 Whys
Before reframing, run 5 Whys on the current problem statement to understand the causal chain underneath it. This often reveals that the stated problem is a symptom of something deeper — and that deeper thing becomes a candidate reframe grounded in causal analysis rather than speculation.
Use after
Issue Trees
Once you've adopted a new frame, use an Issue Tree to decompose it into mutually exclusive, collectively exhaustive sub-problems. The reframe gives you the right question; the Issue Tree gives you the structured breakdown of everything that question contains.
Use after
First Principles Thinking
After reframing surfaces a new problem statement, First Principles Thinking helps you build solutions from fundamental truths rather than analogies. This pairing prevents the common failure of applying old solutions to the newly framed problem — which defeats the purpose of reframing in the first place.
Section 7
Real-World Application
Apple — the iPod and the reframing of the music problem
The scenario
By 2000, the digital music landscape was a mess. Napster had proven that consumers wanted digital music. The recording industry was suing everyone. Hardware companies — Diamond Rio, Creative Labs, Compaq — were building MP3 players. Every one of them framed the problem identically: "How do we build a better portable MP3 player?" More storage. Better battery life. Smaller form factor. The competition was a feature war, and Creative's Nomad Jukebox — with its 6GB hard drive — was arguably winning on specs.
How the tool applied
Apple's reframe, driven by Steve Jobs and a small team including Tony Fadell and Jon Rubinstein, was to reject the hardware-centric problem statement entirely. The problem wasn't "build a better MP3 player." The problem was: "The entire experience of discovering, buying, and listening to digital music is broken." The player was one piece. But the software for managing a music library was terrible (every existing option was clunky). The process of legally acquiring music was worse (no legitimate digital store existed with major-label catalogues). And the connection between computer and device was painfully slow (USB 1.1 transfers took hours for a full library). Apple's reframe expanded the problem boundary from a hardware product to an end-to-end system: device + software (iTunes) + store (iTunes Music Store) + transfer protocol (FireWire, later USB 2.0).
What it surfaced
The reframe revealed that the binding constraint on digital music adoption wasn't hardware quality — it was the absence of a legitimate, frictionless way to buy individual songs. The recording industry's resistance to digital distribution wasn't just a legal obstacle; it was the core unsolved problem. Apple's negotiation with the major labels to sell individual tracks at $0.99 — a deal that took months and required Jobs's personal persuasion — was only possible because Apple framed the problem as an ecosystem challenge, not a device challenge. No hardware company had attempted to solve the content acquisition problem because their frame didn't include it.
The non-obvious factor
Section 8
Analyst's Take
Faster Than Normal — Editorial View
Reframing is the most important tool in this library and the hardest to use honestly. Every other decision tool assumes you've already identified the right problem. Reframing is the only one that questions that assumption. Its power is proportional to the team's willingness to admit that the way they've been thinking about a problem might be wrong — and in most organisations, that admission carries real social cost. The VP who has been championing a particular problem definition for three months doesn't welcome a reframe that invalidates their work. The tool's effectiveness is gated not by intellectual difficulty but by organisational courage.
The failure mode I see most often isn't reframing-as-procrastination or contrarian reframing. It's something subtler: cosmetic reframing. The team goes through the motions — generates alternative frames, discusses them, even selects a "new" frame — but the new frame is just the old frame with different vocabulary. "We need more pipeline" becomes "We need to optimise our demand generation engine." Same problem. Same solutions. Different words. The tell is in Step 5: if the reframe doesn't change who works on the problem, what they measure, or what solutions are on the table, it wasn't a reframe. It was a relabelling exercise. I've watched teams spend two hours in a reframing workshop and emerge with a problem statement that would lead to exactly the same actions as the one they walked in with. That's not a failure of the tool. It's a failure to actually use it.
The highest-leverage technique: bring an outsider into the reframing session. Not a consultant — someone from a different function, a different company, or even a different industry who has no context on the problem. Their value isn't expertise. It's ignorance. They'll ask the questions that insiders have stopped asking because the answers seem obvious. "Why do you measure new logos instead of revenue retention?" "Why do you assume this is a sales problem?" "What would happen if you just stopped acquiring customers in that segment entirely?" These questions feel naive to the team. They are, in fact, the reframes. The outsider's lack of context is the feature, not the bug — they can't see the frame, which means they can't be trapped by it.
Section 9
Top Resources
01
What's Your Problem? — Thomas Wedell-Wedellsborg (2020)
Book
The definitive practitioner's guide to reframing in business contexts. Wedell-Wedellsborg codifies the technique into a repeatable process, drawing on his earlier HBR article "Are You Solving the Right Problem?" The book's strength is its taxonomy of reframing strategies — stakeholder shift, boundary shift, goal redefinition — each illustrated with real cases. Chapter 3 on "framing traps" is particularly useful for identifying when your team is stuck in a bad frame without knowing it.
The scientific foundation for why reframing is necessary. Kahneman's work on framing effects — how the same information leads to different decisions depending on how it's presented — explains the cognitive mechanism that makes problem frames so sticky. Chapters 34 and 35 on framing are directly relevant, but the broader argument about System 1's tendency to accept the first coherent narrative is what makes the case for deliberate reframing as a cognitive intervention.
Lafley and Martin's strategy framework is, at its core, a reframing methodology. Their "strategic choice cascade" — Where to Play, How to Win — forces leaders to reframe competitive problems from "how do we beat the competition?" to "where can we establish a position where winning is possible?" The Procter & Gamble cases throughout the book demonstrate reframing at the corporate strategy level, particularly the Olay and Bounty examples where redefining the competitive set changed the entire strategic direction.
The article that brought reframing into mainstream business vocabulary. Wedell-Wedellsborg's elevator example and his "slow elevator problem" framework are now standard references. More useful than the anecdote is his diagnostic: he surveyed 106 C-suite executives and found that 85% agreed their organisations were bad at problem diagnosis, and 87% agreed that this carried significant costs. The article is a faster entry point than the book and covers the core method in sufficient detail for immediate application.
Christensen's theory of disruption is fundamentally a reframing argument: incumbent companies fail not because they're poorly managed but because they frame competitive threats through the lens of their existing customers and value networks. The disruptor succeeds by framing the market problem differently — serving non-consumers, competing on simplicity rather than performance. Read it as a case study in what happens when an entire industry gets trapped in a single frame and can't escape it.
Timing
Before solution generation. Before resource commitment. Before the team has emotionally invested in a particular direction. Reframing after a team has spent six weeks building a solution is politically brutal and practically difficult — not impossible, but the sunk cost bias works against you. The earlier in the process, the cheaper and more effective.
Organisational culture
Requires a culture that tolerates — or better, rewards — questioning the premise. In organisations where challenging the boss's framing is career-limiting, reframing becomes performative: the team generates alternative frames, then quietly adopts the one the leader already preferred. Psychological safety isn't a nice-to-have here. It's a prerequisite.
First Principles Thinking to build the frame from ground-level evidence rather than from the desire to be contrarian
Frame wars
Different stakeholders advocate for different frames based on their functional interests. The VP of Sales insists it's a pipeline problem. The VP of Product insists it's a product-market fit problem. Reframing devolves into a political negotiation where the winning frame reflects organisational power, not analytical accuracy.
Delphi Method for anonymous frame evaluation; pre-commit to data-based frame selection criteria before the session
Execution-stage reframing
Reframing mid-execution — after resources are committed, teams are mobilised, and stakeholders have been promised a specific outcome — creates chaos. The tool is designed for the problem-definition phase. Deploying it during implementation requires a formal "stop and reassess" decision, not a casual suggestion in a standup.
Pre-Mortem to stress-test the current frame before execution begins; OODA Loop for structured mid-course corrections
Simple problems
Not everything needs reframing. If the server is down, fix the server. If payroll didn't run, run payroll. Applying reframing to problems with clear, unambiguous causes wastes time and signals to the team that you value process over action. The tool is for genuinely ambiguous situations where the problem definition is uncertain.
Cynefin Framework to classify the problem domain first — reframing belongs in the "complex" and "complicated" domains, not the "obvious" one
Reframing process — the B2B software company worked example. The original frame (left) generates one solution direction. Dissecting assumptions and generating alternative frames reveals a higher-leverage problem statement (right) that redirects the entire solution space.
Mental model
Inversion
Inversion is a specific reframing lens: instead of asking "how do we grow?", ask "what would guarantee we stop growing?" The inverted frame often reveals constraints and failure modes that the positive frame obscures. Use it as one of your systematic reframing prompts in Step 3.
Mental model
Ladder of Inference
The Ladder of Inference explains how teams move from raw data to beliefs to actions — and how each rung introduces distortion. Reframing is essentially climbing back down the ladder: questioning the beliefs and interpretations that produced the current problem frame, and checking them against the underlying data.
What makes this case instructive isn't just that Apple reframed the problem — it's that the reframe was validated by a specific, measurable signal that competitors had access to but didn't interpret correctly. Napster's 80 million users had demonstrated massive demand for digital music. Every hardware company read that signal as "people want portable MP3 players." Apple read it as "people want easy access to music, and they'll pay for it if the experience is good enough." Same data point. Radically different frame. The iPod launched in October 2001 and was initially a modest success. The iTunes Music Store launched in April 2003 and sold one million songs in its first week. The store — the component that only existed because of the reframe — was what turned the iPod from a good product into a platform that captured over 70% of the digital music player market by 2006.
