The 30-Minute Agentification
One of 12 value streams, mapped to 10 steps and rebuilt as 5 people and 7 agents. Every node carries a reason for existing and every permission carries a reason for being granted.
At a glance
Every step of the rebuilt stream in one screen. Each card says what the step is and what happens to it; click one to jump to it in the detail below.
The company
Lines of business
Systems of record
The vocabulary
Where the leverage is
A value fulcrum is a pivot point in the operating model where a small applied force moves a disproportionate amount of value. These were found before the value streams were derived, which is the order that matters: find the streams first and you pick the one you already had in mind. Each carries a lever, a load, a pivot, and the arithmetic of its mechanical advantage. The ones marked confirmed are the ones the business said were real.
The business, end to end
A value stream starts with a trigger from outside the business and ends with value delivered to a customer and captured by the company. These are all of them. Everything below this section is the one marked chosen.
Which one first
Every confirmed stream scored on seven criteria and weighted seven different ways, each weight defended from what the research established about this business. The point of scoring is not the number: it is that seven criteria force seven different conversations that otherwise collapse into one conversation about enthusiasm. A 5 on business impact carries the confirmed fulcrum it stands on, because a business impact score with nothing behind it is an opinion.
This section is live. Move any weight, click any score, re-plot the two by two on any pair of criteria, and everything recomputes. A weight you can move is an argument you can have; a weight you cannot move is a number you will quietly distrust. Edits stay in this browser and never leave it.
The chosen stream
How it runs today, and what each step becomes in the rebuild. Blue is a rule: the same procedure reaches the same answer every time. Amber is a judgment: two competent people could reasonably differ. A red edge on the right means the step cannot be taken back, so a person stays on it however routine it looks. Every step also carries the call the whole exercise turns on: whether a human or an agent should do it, which side of the Delimitation of Value it sits on, and which velocity-variance zone that puts it in. A step on the architect's side is one an agent does not take, because liability cannot be delegated.
The rebuild
Carbon nodes are people, silicon nodes are agents, and they are on one chart because an architecture that draws only the agents has the accountability cropped out of it. Every edge carries a written justification. A grant nobody can defend is meant to be visible.
Hover any node to isolate what it can reach and read its role definition. Click to pin it. People carry their AI-native job description in the same panel, because the node and the role definition are the same artifact in two shapes.
The people alongside them
Written for the organization being designed, not the one that exists. If one of these reads like the same job with fewer hours, it is wrong: what is left should be the work that needed judgment, authority, or accountability in the first place, plus the new work of operating the agents.
Inputs and outputs
Every node on the map converted into the two units a business decides with. A person is available 8 hours a day and about 230 days a year; an agent is available 24 hours a day and 365 days a year, which is roughly 4.8 times the annual availability. Availability is not throughput, and the page says so where it matters.
Every figure carries its basis. A number with no basis is an opinion with a decimal point, and this is the section that gets challenged hardest.
The change
The map is a design. This is the plan, the checklist somebody works from on a Tuesday morning, and a memo for every person on the org chart whose job it touches. An architecture nobody was taken through is an architecture that does not happen: the agents work, and the organization routes around them, because the people whose work changed found out from a diagram.
What you can now do
Between the stream and the agents. A step map answers what happens here; an agent answers what is being built. This answers the question the person paying asks, which is what the organization can do now that it could not do before. One capability is often several agents, and one agent often serves several capabilities.
The data underneath
Most data programmes produce a four-hundred-row heat map sorted by how bad the data is, and nobody starts. This is sorted by how much of the rebuild leans on each asset multiplied by how far it is from ready, at the grain of a sheet rather than a system, because "clean up the CRM" is not a piece of work anybody can pick up on a Monday.
What can go wrong
Per agent, per capability, per stream. A risk written once at the wrong altitude reaches nobody. Every row names how you find out it is happening, which is the field that gets skipped and the one that matters: most agent failures are quiet and continuous, and a mitigation with no detection is a plan that starts after somebody notices.
The pre-mortem
The only part of this document written in the past tense, and that grammar is the whole technique. A team asked to list risks produces a cautious list, because doubting the plan in front of the person who owns it is a loyalty test. A team told the plan already failed produces a different list, because the failure is now a fact to explain. Each one carries the earliest thing you would notice and the line at which you stop.
Your first agent
Pick any agent on the map to read its complete role definition and the code generated from it. The one marked ran is the one that executed against the workbooks.
What actually happened
In your body, memory lives in the brain. In an agent it does not. The brain is rented and wakes up with amnesia every session. Memory is an organ you have to build, and it lives outside the model.
The trace
The systems it touched
The workbooks stand in for the company's systems of record and carry their real product names. The agent reached them at the level its grant allows, through the connector on its role definition. Open the files to see the same colours in the cells.
Cheek LLC · The 30-Minute Agentification · v1