Work, with its state made explicit.
This is where we show problems addressed, systems built, artefacts, evidence, limits and who retains the system, criteria and operating knowledge. We do not invent cases to fill sectors.
Capability is the unit of value
A capability combines people, process, data, system and controls to make a new, governable operating behaviour possible. A project is temporary work; the capability is what the organisation needs to use and verify.
Declared states, honest differences
A system in controlled rollout, a prototype tested on real documents and an internal research prototype are not the same. Every case carries its state because maturity matters as much as subject.
- Controlled rollout
- The system exists and is in controlled use; that does not mean the engagement is concluded.
- Prototype
- Feasibility has been tested on real material; it is not production.
- Research
- A prototype and technical direction exist; no client deployment is claimed.
Problem families, not a service catalogue
Scattered knowledge, delayed decisions and prototypes that have to become reliable systems are families of problems. Technology is selected only after constraints, data and risk are understood.
Evidence includes what is missing
Every case says how it is checked, where the system, criteria and knowledge remain, and what cannot be published. Names, metrics and outcomes stay out until permission exists.
Want the method behind these cases?
The 38 Way explains how a constraint becomes a capability—and when not building is the right decision.