Every popular problem-solving method begins with the problem already defined. The team sits down to brainstorm solutions, weigh options, apply criteria. Nobody asks whether the problem itself is the right one. Problem framing is the act of defining what you are actually deciding and why, clarifying purpose, opportunity, outcome, context, and time horizon before evaluating options or gathering data. In the Universal Decision-Making Method that Roger Estall and I set out in Deciding, framing is Step 1: the decision that shapes every decision after it.
I have spent nearly fifty years helping organisations make consequential decisions. The ones that fail most expensively are not the ones that choose the wrong option. They are the ones that solve the wrong problem, because nobody stopped to question the frame before the work began.
What is problem framing?
In design thinking and product development, "problem framing" usually means a workshop exercise: gather the team, write problem statements on sticky notes, vote on which one to pursue. That is not what I mean. Problem framing, as a decision discipline, is the structured work of establishing what you are deciding, why you are deciding it, what outcome you intend, how long the outcome matters, and what conditions surround the decision right now. It is not a brainstorming activity. It is the most consequential step in any decision, and in most organisations it receives the least rigour.
The Universal Decision-Making Method treats framing as Step 1 with five distinct substeps. Each substep asks a specific question. Each question produces a specific output. The result is not a problem statement on a whiteboard. It is a documented frame that the Decider and everyone involved can examine, challenge, and revise.
There is no shortage of problem-framing advice in the design thinking world. Workshops, canvases, facilitation techniques. What most of it lacks is a repeatable structure that produces a frame you can hold accountable. A frame produced in a two-hour workshop lives as long as the sticky notes on the wall. A frame produced through five documented substeps can be tested against reality when conditions change.
Why problem framing comes before problem solving
The instinct in any organisation is to solve. A problem appears, and the room fills with solutions before anyone has tested whether the problem is the right one. I have watched this pattern in boardrooms and project teams across industries and continents. The group leaps to options, evaluates them against criteria that feel rigorous, selects the best one, and implements it. Six months later the project stalls or fails, and the post-mortem reveals that the problem was defined too narrowly, or simply wrong.
This is not a failure of intelligence or effort. It is a structural gap. Most decision-making frameworks treat problem definition as a single box in a flowchart, then dedicate eighty per cent of their steps to solution generation and evaluation. The ratio is backwards. Framing the problem is where the real work is, and where most complex problem solving goes wrong.
I have often put the following question to clients: "If risk management is the answer, what was your question?" The response is usually puzzlement, followed by a slow realisation that they had adopted a methodology without ever defining the problem it was supposed to address. They had been solving without framing for years, and it had never occurred to anyone to question it, because the discipline had its own vocabulary, its own conferences, its own professional certifications. It looked like rigour. It was rigour applied to the wrong question.
The five steps of problem framing
Step 1 of the Universal Decision-Making Method has five substeps. Each addresses a dimension of the frame that, if left unexamined, will distort everything downstream.
1a. Clarify Purpose. State the reason the organisation exists. Not the mission statement on the wall, but the actual reason people show up and the work gets funded. A statutory public safety body in Australia spent 0.03% of its budget on its legislated prime consideration function. When the gap between stated and actual Purpose was corrected and the allocation raised to 0.5%, loss of life fell by sixty per cent within two years. Purpose is not decoration. It is the foundation the frame is built on.
1b. Be explicit about the Opportunity. What opportunity does this decision exploit? Why now? Opportunities are not fixed. An opportunity that exists today may close next quarter, and a decision framed around a vanished opportunity is a decision framed around nothing.
1c. Be specific about the intended Outcome. What is to result from this decision? Selecting the outcome is itself a decision, and too often teams treat it as obvious when it is not. I have sat in meetings where, forty minutes into a discussion about options, it became clear that half the room was optimising for market share and the other half for margin. They had never agreed on the outcome. The options they were evaluating could not all serve both.
1d. State the intended Duration. Over what period will the outcomes of this decision be experienced? A decision with a five-year horizon requires different monitoring and a different tolerance for uncertainty than one with a five-week horizon.
1e. Establish the Context. Roger and I developed a three-band model for this. Internal context covers the organisation's own features: its policies, staffing, culture, and working capital. External context covers stakeholders and dependencies: suppliers, customers, and regulators. Wider context covers forces beyond anyone's direct control: regulatory changes, economic shifts, and technology trends. For each band, you estimate the probability, speed, timing, and detectability of change. The output is a succinct, dated description of the conditions surrounding this decision right now. Context relates to the decision, not to the organisation in general. Two decisions made by the same organisation on the same day may operate in entirely different contexts.
These five substeps are what distinguishes a framing discipline from a framing exercise. A decision-making process model that collapses all five into "define the problem" is not defining the problem. It is hoping the problem defines itself.
What is an example of framing a problem?
A national postal service saw letter volumes falling year after year and framed the challenge as a letter-volume problem. The frame made sense on its face: letters were the core product, volumes were declining, and the business needed to arrest the decline. Teams produced efficiency programmes, cost-reduction plans, and campaigns to encourage letter writing. Every initiative addressed the frame as given.
The frame was wrong. Letter volumes were not falling because of a marketing failure or a service deficiency. They were falling because digital communication had replaced the need. The same digital shift that reduced letters had created an explosion in parcel deliveries as online shopping grew. The postal service sat on a national logistics network perfectly suited to parcels: sorting facilities, vehicles, daily routes to every address in the country. The opportunity was visible in the organisation's own data. But the letter-volume frame excluded it.
When the frame shifted from "how do we protect letter revenue?" to "what is a national postal network actually for in a digital economy?", the answer changed completely. The same assets and the same workforce. A different frame produced a fundamentally different business. Sorting facilities that were underutilised for shrinking letter volumes became parcel hubs. The postal service that reframed around parcels thrived. Others that held the letter-volume frame and kept cutting costs within it shrank.
The reframe did not require new technology or new capital. It changed the question. Step 1a would have surfaced the gap: what is this organisation actually for? The stated Purpose was letter delivery. The actual capability was national logistics. The decision that needed framing was not "how do we save the letter business?" It was "what business are we actually in?"
The framing effect: how framing distorts decisions
Daniel Kahneman and Amos Tversky demonstrated in 1981 that the way a problem is presented changes the decisions people make, even when the underlying facts are identical. A medical treatment described as having a ninety per cent survival rate is preferred over one described as having a ten per cent mortality rate. Same fact, different frame, different decision. They called this the framing effect, and it has been replicated in hundreds of studies across medicine, finance, and public policy.
I have written about how the framing effect operates in committees and what you can do before the room starts arguing about the wrong question.
The conventional response is awareness: know about the framing effect, watch for it, ask whether you are being influenced by how the problem is presented. Awareness is a reasonable starting point. It is not a countermeasure. You cannot watch for framing bias in real time any more than you can watch for your own blind spot while driving. The bias enters through the frame itself, before you start evaluating options.
Step 1 of the Universal Decision-Making Method does not ask you to watch for framing effects. It asks you to build the frame yourself, substep by substep, before evaluating anything. When you have independently clarified Purpose, Opportunity, Outcome, Duration, and Context, the frame is yours. It was not handed to you by the first person who described the problem or inherited from a project brief. It was constructed deliberately, and every element can be examined and challenged. That is the difference between knowing about cognitive biases in decision making and having a method that catches them.
Common problem framing mistakes
Nearly fifty years of practice have shown me the same framing mistakes recurring across industries and continents. Seven are worth naming here.
The first is starting with the answer. Organisations adopt methodologies, frameworks, and belief systems, then work backwards to define problems those tools can solve. Belief systems inevitably start with the answer rather than with careful and objective definition of the problem. An entire industry of risk management was built this way: the methodology came first, the question it was supposed to answer came never.
The second is confusing stated Purpose with actual Purpose. What the organisation says it exists to do and what it actually does with its resources are often two different things. The disconnect between the two is where framing fails silently.
The third is treating context as background rather than decision-specific input. Context relates to the decision, not to the organisation in general. A single organisation may face entirely different contexts for two decisions made in the same week.
The fourth is goal fixation. Pilots call it got-to-get-there-itis: under pressure, the immediate goal replaces the overarching Purpose. The pilot who presses on through deteriorating weather has substituted "arrive at the destination" for "arrive safely." The executive who pushes a product launch past safety warnings has made the same substitution with different consequences.
The fifth is failing to see apparently unrelated changes combining into a single force. Each change, viewed individually, is manageable. Together they create conditions that the current frame cannot accommodate.
The sixth is allowing context awareness to fade. Context established once and never revisited becomes a fiction. The gradual change that nobody notices is the one that invalidates the frame.
The seventh is failing to recognise a decision as a decision at all. Air New Zealand Flight 901 crashed into Mount Erebus in 1979. Two hundred and fifty-seven people died because amended navigation coordinates were never communicated to the flight crew. Nobody treated the coordinate change as a decision that required framing. It was treated as a data entry. That failure cost two hundred and fifty-seven lives.
A problem framing canvas for leaders
If you take nothing else from this page, take these five questions. They are derived from Step 1 of the Universal Decision-Making Method, and they will catch most of the framing mistakes I have described.
First: what is the Purpose this decision serves? Not the project objective. The reason the organisation exists that makes this decision worth making at all.
Second: what Opportunity does this decision exploit, and why now?
Third: what specific Outcome do you intend, and how will you know you have achieved it?
Fourth: over what Duration will the outcomes be experienced? A decision with a five-year horizon requires a fundamentally different frame from one with a five-week horizon.
Fifth: what is the Context right now, across all three bands: internal, external, and wider? What has changed since this decision was first discussed?
These are not brainstorming prompts. They are governance questions. The answers should be documented, dated, and revisited when conditions change. A frame that cannot survive being written down is a frame that has not been examined.
I have watched organisations spend half a day in a facilitated workshop producing a problem statement, then proceed to make the decision without ever asking these five questions. The workshop produced alignment. It did not produce a frame. Alignment on a poorly defined problem is not progress.
How to reframe when the frame is wrong
Framing would be straightforward if you only had to get it right once. You do not. Conditions change, assumptions collapse, and the frame that was sound six months ago may be the reason the project is now failing.
The signals are consistent across every case I have seen. Assumptions are failing faster than the team can replace them. Stakeholders in the same meeting are solving different problems. Data that contradicts the original premise keeps being explained away rather than addressed. The team cannot agree on what success looks like.
These are not execution problems. They are reframing signals. The instinct is to work harder within the current frame: more data, more analysis, more meetings. But when the frame itself is wrong, working harder within it only accelerates the journey in the wrong direction.
Step 1e of the Universal Decision-Making Method builds reframing into the method through Context monitoring. The three-band model requires periodic review: has internal context changed since the frame was set? Has external context shifted? Have wider forces moved? If the answers have changed materially, the frame must be revisited. Not because someone feels uneasy. Because the conditions the frame was built on no longer hold.
The taxi industry illustrates the cost of refusing to reframe. GPS navigation, smartphone adoption, mobile payment systems, and gig-economy labour markets each developed independently over a decade. Each change was individually manageable within the existing business model. The operators who monitored wider context recognised the combined effect and reframed early. The ones who treated each change as a separate concern and held the old frame lost the business entirely.
Problem framing is not something you do once at the start of a project and file away. It is the discipline that determines which problems get solved and which assumptions pass without scrutiny. Everything that follows the frame is execution, and no amount of good execution recovers a bad frame.
Grant Purdy is the co-author, with Roger Estall, of Deciding (2020), and the architect of the Universal Decision-Making Method.
If you have a decision you are working through, the Walk can help.
Start a Walk