How a situation becomes a path
Constrange does not start with a platform, a model, or a programme. We start with the pressure as it actually is — then create enough structure for a decision that operations can absorb.
Five stages. One first move.
The same sequence applies whether the pressure is operational, strategic, or technical — because the constraint is rarely the tool that was first requested.
Understand
Work, systems, people, and constraints as they actually are — including unofficial paths.
- Map how work moves today, not how the diagram says it should
- Surface the shadow systems keeping operations alive
Define
A named problem, non-goals, and what would count as better.
- Write non-goals before the next tool is discussed
- Separate a fluent answer from a decision the organisation can own
Explore
More than one credible path, held long enough to compare.
- Hold two or three options without collapsing to the first plausible one
- Doing less remains a valid path
Structure
Architecture, owners, and sequence — the join is designed, not hoped for.
- Name who owns the handoff between teams and systems
- Make trade-offs explicit before a stack is selected
Move
A first action small enough to be real, and a rhythm to review it.
- One move the current operation can absorb
- Artefacts you can challenge without a slide of jargon
How the work is counted
Bring the situation as it actually is
You do not need a polished brief. A conversation is usually enough to name the problem and decide whether there is work here at all.