The Progression of Meaningful Response

A customer-facing system went down overnight. The frontline team had service restored before sunrise, and the metrics recovered fast enough that the organization could have told itself a clean story: an incident, a response, a recovery. The review meeting still turned sharp.

The operations head opened with the timeline, in the voice of someone who had been awake at three in the morning with their hands on the work. A functional head cut in with a sentence about recurrence. A commercial head asked what customers had experienced, not what the system signals said. A product head asked whether the next release should be paused. Four statements, one incident, and the room split into camps before anyone had time to perform.

The misdiagnosis

The reading in the room was that someone was being difficult. Afterward the labels arrived: the operations head is not strategic, the functional head is relitigating, the commercial head is emotional, the product head is slow. Personality got charged for a problem it did not cause.

Nothing in that room required anyone to be wrong. What it required was translation. Four competent people were running the same sequence of thinking at different speeds and against different evidence, and none of them had said which part of the sequence they were in.

What is the Progression of Meaningful Response?

The Progression of Meaningful Response is the structured flow of four cognitive disciplines, Sense-Making, Meaning-Making, Framing, and Solving, that organizations move through when conditions shift: Sense-Making asks what is happening, Meaning-Making asks what it means, Framing asks what we need to solve, and Solving asks how we solve it. Under stress the progression does not disappear. What disappears is agreement about which discipline the room is supposed to be doing right now.

The first distinction is the one most organizations get backwards. This is not a seniority ladder. Every level of an organization lives the full progression. Nobody gets promoted into Meaning-Making, and nobody is just solving. Every role has to orient to reality, connect that reality to purpose, decide what to do next, and act. What changes across levels is not whether you run the progression. What changes is the lens you run it through.

Two things name that lens. A Level of Work carries a Time Span of Discretion, the length of time you are expected to hold consequences without new direction. A short span forces concreteness, because feedback arrives quickly and precision gets rewarded. A longer span forces you to sit with ambiguity, because feedback comes late and the variables keep moving while you learn. Mode of Thinking names the other half: whether someone works close to discrete facts, combines them additively, reasons in designed sequences, or holds several interdependent variables at once.

Put those together and the incident meeting stops being a conflict. The four executives were not disagreeing about what happened. They were Sense-Making through different time spans, Meaning-Making through different stakes, Framing through different boundaries, and Solving against different definitions of success.

How do you know the room is out of step?

Three signals are worth checking against your own organization this week:

• Lens differences are being described as character. Concrete Sense-Making gets called narrow. Long-horizon Sense-Making gets called theoretical. Meaning-Making gets dismissed as soft. Framing gets treated as stalling, and Solving as rushing. When your vocabulary for disagreement has become a vocabulary for personality, the mismatch is structural.
• Nobody can say which discipline the meeting is performing. Ask, mid-meeting, what the room is doing right now. If half the answers name a stage and the other half name a deliverable, the room is running four private progressions in parallel.
• The loudest demand is always for a solution. Pressure makes people reach for Solving as emotional relief, because a proposal is the fastest way to stop feeling uncertain. A room that cannot tolerate ten minutes of shared sensing will solve the wrong problem with impressive intensity.

The third signal is the expensive one. Skipping upstream does not remove the upstream work; it just moves it downstream, where it reappears as rework, escalation, and a plan nobody can defend.

What to do with it

Name the discipline and the lens out loud, in one sentence, before the room proceeds. That sounds too small to matter and it is the whole move. We are not solving yet; we are Sense-Making, and we are doing it across three different time spans. Our frame is muddy, and we are working hard on several problems because we have not chosen the one worth solving.

Then do Sense-Making across lenses rather than inside one. Let the operations head keep the timeline and have the functional head add the pattern across incidents, the commercial head add what customers actually experienced, and the product head add dependency and release risk. That takes twenty minutes the room does not feel it has, and it is cheaper than a quarter spent solving a problem three of the four never agreed to.

The rule that makes this durable is short: do not correct the person first, correct the mismatch. Correcting the person costs you their contribution and buys compliance. Correcting the mismatch costs you a sentence.

Coherent, not painless

Go back to the meeting that split into camps. It did not become comfortable when the lenses were surfaced. The operations team still had to hear that heroics are a form of debt, and the product head still had to make a release decision with real consequences attached.

What changed is that the room stopped arguing conclusions and started placing the work. Each person got to contribute their full progression without being forced into someone else’s horizon. The Progression of Meaningful Response does not make hard meetings painless. It makes them clean, and clean is the condition under which judgment starts to travel.

The Progression of Meaningful Response is developed in The Capability Advantage by Jose J. Ruiz, Volume I of the Built to Endure series.