An organisation's capacity to improve lives on the floor, in how people do and adjust the work every day. Evident Design makes that work visible and captures the agreements about it so that drift stands out. No new method, no Lean off the shelf.
No one decided it should change. An exception came up, someone found a handy workaround, an agreement wore thin. The work kept going, so no one noticed. The picture in the boardroom stayed put; the floor moved on.
Only when something goes wrong, or when you lay AI over that work, does it show how far the picture and the work have grown apart.
It is not unwillingness and not a fault. People keep things running within what they can oversee. That is how it works, until no one sees the whole anymore.
Evident Design captures how the work actually runs, not as a process description in a drawer, but as a talk-document: a living standard you walk through together. Precisely by discussing it, you see where reality has drifted from the agreement. The document secures the seeing, not the control.
Not a checklist to tick off, but a document to talk with. The drift is not proof that someone failed, it is the starting point of improvement.
We map what the work actually does, in the place where it happens. Not what it should do, what it does.
What the working way is here, we make explicit, together with the people who do the work. Their knowledge, not an import.
The agreement becomes a talk-document: short, tailored, written so that drift stands out the moment reality shifts.
At set intervals we walk through the document. Does it still match the work? What drifts is worth a conversation, not a reproach.
Once the work is evident, a new question becomes possible: which agreements are stable and important enough to secure hard? Where the work sits in software, Invariant Design takes over: the same agreement, now provable at every run. Evident Design makes it visible, Invariant Design keeps it proven.
The talk-document form grew in a large logistics organisation, where standard instructions were used to make the work discussable rather than to enforce it.
We apply Evident Design to ourselves too. This is how a join-the-work engagement runs: we take part in the work, two weeks to a month, and only then propose something grounded in lived experience. The full form stays visible, the why included, for everyone involved in the work, so the value of each step is there to follow.
| Nr | What? (Step) | How? | Why? | SQDC | Artefact |
|---|---|---|---|---|---|
| 1 | Intake conversation | 1. Get one question sharp: which decision is the client about to make, and on which system output is it based? 2. Together decide where we join the work and for how long (two weeks to a month). 3. Agree upfront: we take part, we do not judge. | Without a real decision behind it there is no focus. The question sets where we look, and the no-fault agreement makes people open later on. | Safety - The upfront no-fault agreement takes the fear out. Quality - A sharp question focuses the observation. Delivery - A clear start gives a clear end. Cost - No time wasted on too broad a scope. | The sharp question, written down. |
| 2 | Joining the work | 1. Take part in the work itself, not watching from a distance. 2. Follow the daily flow, including the busy moments and the exceptions. 3. Stay on the same side as the people; no separate observer position. | The capacity and the real logic live in the doing. You only see them by taking part, not from the sidelines. | Safety - Taking part rather than watching keeps the floor at ease. Quality - You see the real work, not a staged version. Delivery - First signals of where picture and work diverge. Cost - No costly observation setup, just joining in. | Field notes from taking part. |
| 3 | Observing and naming | 1. Record what actually happens, per group involved. 2. Factual, without adding interpretation: what was seen, what was said, where the picture diverged from the work. 3. Something out of scope? Name it, do not step in. | No-fault. It is information, not a verdict. Recognition for the people, insight for leadership. A gap between picture and work is the finding, not the reproach. | Safety - Factual and without judgement keeps it safe. Quality - Recording per group makes the picture complete. Delivery - The observation becomes the basis of the proposal. Cost - Role clarity prevents disrupting the work. | Observation document per group involved. |
| 4 | Conversations from taking part | 1. Give back what was observed and walk through it together. 2. As a talk-document, not a report. 3. Discuss the deviations and edge cases and test whether it holds. | The document secures the seeing, not the control. Drift becomes visible in the conversation, not ticked off. | Safety - A conversation, not a reckoning. Quality - Testing with the people sharpens the picture. Delivery - A shared picture enables a supported proposal. Cost - Misunderstandings out before anything is built. | Talk-document (the living SI). |
| 5 | Proposal grounded in lived experience | 1. Make visible and keep alive as a talk-document (Evident Design). 2. What is stable and critical enough, secure hard in software (Invariant Design). 3. The proposal rests on what we experienced, not on an assumption. | A proposal from reality, not off-the-shelf. Does the client want a solution sooner? See first, propose after. | Safety - A proposal the people recognise will hold. Quality - Grounded in what actually happens. Delivery - Concrete: what to see, what to secure, and how. Cost - No investment in something that does not fit. | The proposal, with scope and layers (ED/ID). |
One conversation, no obligation. We start from what is already running.