Framing Turns Heat Into Movement
Framing is where an organization decides what it will treat as the problem. Without a shared Frame, teams argue in different worlds using the same words.
The argument comes back. It came up in the leadership meeting six weeks ago, it came up in the quarterly review, and now it is here again in a different room with three new people in it, wearing slightly different words. Nobody in the room is unserious. Two teams have prepared thoughtfully and both cases are internally sound.
You can see the residue of it on the calendar. Alignment meetings have multiplied. A decision made in April was quietly reversed in June without anyone explaining why. Escalation has become the most reliable interface between two groups, because escalation is the only channel that produces a ruling. The organization is busy, and the work is not accumulating.
That pattern is not a communication failure and it is not a talent problem. It is what a room looks like when nobody has decided what the problem is.
Why priorities are the wrong argument
The standard reading is that this is a prioritization problem, or a culture problem, or an ownership problem. So the organization runs a prioritization exercise, publishes a clearer RACI, and asks people to assume good intent. The temperature drops for two weeks and the same argument returns.
Watch what capable teams do inside that gap. They build dashboards. They fix the handoff. They tighten the meeting cadence. They optimize throughput. All of it is respectable work, executed well, and none of it helps, because the constraint is upstream of every one of those moves. High-performing teams get exhausted this way — solving the wrong thing with excellence.
Priorities, resourcing, and ownership share one quality that makes them attractive: they are all more comfortable than the trade-off underneath them. Priorities can be ranked. Resourcing can be counted. Ownership offers the comfort of a boundary. A trade-off requires somebody to say out loud what the organization is going to give up.
What is Framing?
Framing is the discipline of deciding what an organization will treat as the problem, choosing the lens that governs what counts, what gets ignored, and which trade-offs have to be faced, so raw uncertainty becomes a shared problem statement sturdy enough for coordinated action. It is the third stage of the Progression of Meaningful Response, and it is the moment a room stops admiring the mess.
Two distinctions make it usable. The first separates Framing from the stage before it. Meaning-Making clarifies what the organization is responsible for protecting. Framing clarifies what problem it is solving in order to protect that. Values do not automatically become a problem statement, which is why a room can have genuine agreement on stakes and still spend two quarters treating symptoms as the work.
The second separates Framing from Solving. Consider Microsoft in the years around Satya Nadella becoming chief executive in February 2014 and his July 2014 memo naming the company as a productivity and platform company for a mobile-first and cloud-first world. “How do we ship Office on the iPad?” is Solving. “What are we optimizing for in a world where customers will not live inside one ecosystem?” is Framing. Underneath sat a choice between two legitimate kinds of safety: control, which makes execution efficient and coordination easy, and relevance, which keeps the organization in contact with where customers already work. The error is pretending both come without cost.
A Frame is not a slogan, and this is the test. A Frame is what makes certain arguments irrelevant and other arguments necessary. It changes what the organization considers betrayal. In a Windows-centered Frame, putting Office on a rival device reads as disloyalty to the center. In a productivity-and-platform Frame, withholding the tools people use to do real work in order to defend a legacy center is the betrayal. The announcement of Office for iPad in March 2014 read externally as product news. Internally it was a Frame made visible through a decision that cost something and could not be explained away as messaging.
How do you know the Frame is missing?
Three signals are worth checking against your own organization this week:
- The debate migrates rather than resolves. The same disagreement resurfaces under new labels in new rooms. People believe they disagree about solutions when they are actually disagreeing about what the problem is, and the conversation accelerates without resolving.
- Decisions reverse without explanation. Not because anyone is careless, but because the problem keeps getting reframed at the wrong altitude and no version of it is ever held long enough to become shared.
- Certainty theater has replaced Framing. People learn that the way to be safe is to sound sure, and the way to sound sure is to shrink the problem until it fits inside today’s comfort. This shows up wherever immediate countable signals are valued and ambiguous emerging ones are not.
The move is to name the trade-off
Walk into the room where the argument is escalating, and do not try to decide who is right. Locate what each side is protecting in time. One person is defending the Present Horizon because delivery is on the line this quarter. Another is defending the Future Horizon because the environment is shifting. A third is defending the Enduring Horizon — identity, legitimacy, what the organization would still recognize as itself — and using safer words, because that one feels too exposed to name directly. Most trade-offs are horizon collisions wearing the costume of a resourcing dispute.
Then say the trade-off plainly, without shaming the people holding either side of it. Something in the shape of: we are protecting the economics of the business that funds us, and we are trying to become relevant in the environment customers have already chosen; optimizing only for control risks irrelevance, optimizing only for relevance destabilizes the machine that pays for the transition, and our problem is to stay solvent while becoming something else. That sentence turns two accusations into one structure.
Then test the Frame before investing in Solving, because a strong team will sprint from a named trade-off into a solution contest in minutes and the sprint feels like momentum. The test is not whether people agree. The test is what happens to the debate. If the debate is unchanged, the problem was renamed rather than reframed, and the old trade-offs are still hidden. If the debate changes shape — some arguments getting smaller, others getting more precise — the Frame is holding.
Heat, and then movement
Go back to the argument that keeps returning. It was never a personality contest, and no amount of assumed good intent was going to end it, because the room was arguing inside two different problems while using one vocabulary.
Framing does not eliminate conflict. It upgrades conflict, and it turns heat into movement. The relief people feel when someone finally names the trade-off cleanly is not relief that the work is over. It is relief that the work has become coherent. A Frame does not make the path painless. It makes the path possible. What decides whether that path accumulates anything is Solving, the move you design once the Frame is clear.
Framing is the third stage of the Progression of Meaningful Response, the flow of four disciplines every level of an organization runs.
Framing is developed in The Capability Advantage by Jose J. Ruiz, Volume I of the Built to Endure series.