“Engineering is slow” sounds like a problem statement, but it may be a conclusion with the investigation omitted. The team could be waiting for approval, reworking unclear requirements, or delivering slowly for reasons within its control. Each explanation calls for a different response.
Start with a verified observation, then test competing explanations. Reframing is not a way to excuse poor performance. It is a way to apply accountability to the part of the system that is actually producing the problem.
Replace the label with something observable
A useful observation includes the work, the relevant period, and the event you can inspect. “The last three release candidates waited for approval after engineering marked them ready” is more specific than “the team lacks urgency.” It does not yet explain why they waited.
Do not invent precision. If the record is incomplete, say so and gather enough evidence to investigate. A frame built on a confident but unverified number is still an assumption. The objective is not a dashboard full of measurements. It is a question that can change the next action.
Separate descriptions from explanations. A queue is an observation. “Nobody cares about the queue” is an explanation that needs evidence. Keeping them distinct makes it possible for someone to challenge the explanation without denying the problem.
Test more than one plausible explanation
Illustrative scenario: Mateo is told that engineering is holding up a client release. Yuki reviews the release records with him. The latest candidate was ready for review, but approval depended on a control owner who was unavailable. Another candidate returned to engineering because acceptance criteria changed during review.
They consider three frames: engineering execution is too slow; approval capacity is the bottleneck; acceptance criteria are unclear. These can all be partly true. The team should not select the friendliest explanation before checking the work.
For the next bounded release, the sponsor names an available approval owner and agrees on acceptance criteria before implementation. Mateo records when the candidate is ready, what the reviewer needs, and any returned work. Yuki checks the review queue at the agreed point.
If review moves promptly but engineering still misses its own commitment, the execution frame remains relevant. If readiness was mislabeled because evidence was missing, that also belongs in the review. If the wait disappears after ownership is clarified, “work faster” would have targeted the wrong constraint.
This is an illustrative test, not a measured client outcome. Its value is the changed question and the evidence required to answer it.
A compact record for a competing explanation
| Part | Example |
|---|---|
| Verified observation | A candidate marked ready waited for approval. Confirm the dates and required evidence. |
| Current explanation | Engineering execution is the main delay. |
| Competing explanation | Review ownership and unclear acceptance criteria cause waiting or rework. |
| Bounded test | Name the reviewer and agree on criteria before the next candidate. |
| Owner and review | Yuki checks queue and return reasons at the scheduled release review. |
| Action if supported | Keep explicit review ownership and criteria; address remaining execution gaps separately. |
This is an authored investigation tool, not a validated causal model. Do not use it to run an uncontrolled experiment where a mistake could harm people, violate a requirement, or expose confidential data. Use appropriate expertise and approved procedures in those settings.
Look for evidence that would weaken your preferred explanation. If every possible result is interpreted as confirmation, you have not designed a useful test. Name the observation that would make you change your view.
Fairness and accountability belong together
Leaders should make it safe to question the frame without making every responsibility negotiable. A team can be responsible for incomplete evidence while another owner is responsible for unavailable approvals. Identify both rather than asking for one villain.
Also resist a frame that cannot produce action. “The organization is complex” may be true, but it does not name what can change next. Find an owner, a bounded adjustment, and a review point. If authority is missing, escalate that specific dependency.
Reframing is less useful during an immediate emergency when a known response must happen now. Stabilize using the appropriate procedure, then investigate the wider problem. For an urgent decision with missing evidence, use a clear decision boundary.
Test one explanation before prescribing the fix
Take the next complaint about a team or process. Write the observable event without the label. Add one competing explanation and one safe test that could distinguish them.
At the review point, state what the evidence supports, what remains uncertain, and who should act. If the original frame survives scrutiny, address it directly. If it changes, redirect the effort without pretending the original problem never mattered.