01
Understand the operation
Start with the work before proposing a system.
Will you understand what is actually happening here?
What this means
Frame learns how work moves between people, tools, and decisions—and where context, ownership, or momentum is being lost.
- 01
Follow the work as it is actually carried out.
- 02
Separate the visible symptom from the constraint carrying weight.
- 03
Do not recommend a system before the operation is legible.
What gets attention here
See the work before trying to change it.
Depth comes from making the conditions of work visible—not arriving with a ready-made answer.
- 01
Work in motion
Where a request starts, who carries it forward, and which tools or conversations keep it moving.
- 02
Handoffs and decisions
Where ownership shifts, what someone needs to know next, and which decisions wait for missing context.
- 03
The constraint beneath the symptom
A delayed update or missed follow-up may be visible; the question is what makes that failure repeat.
What this stage establishes
A shared view of the work worth understanding.
The aim is not to diagnose from a distance. It is to give the people closest to the operation a clearer language for what is happening.
- 01
A working picture of people, tools, decisions, and handoffs.
- 02
A distinction between isolated friction and the constraint carrying weight.
- 03
A grounded basis for deciding whether a meaningful change is worth pursuing.
How the work takes shape
A stage that makes the next move clearer.
- 01
Follow a real path
Frame traces a piece of work through the operation rather than asking the team to describe an idealized version.
- 02
Compare accounts
Different perspectives expose where the work is understood differently or responsibility is assumed rather than explicit.
- 03
Name what remains unclear
Uncertainty is recorded instead of hidden. The next step earns clarity through a written account of the operation.