Role lenses

The same course, read four ways

The course reads the same for everyone — one spine, no separate tracks. But the questions land differently depending on what you carry. This page threads four roles through all six modules, so you can follow your own lens from start to finish — or read another's, which is rather the point.

The roles are flattening. In a small business one person often holds several; in a one-person-plus-agents business, one person holds them all. Read them as responsibilities, not ranks — there is no track you are kept out of, and the newest person is meant to read every line.

Why surface roles at all? Because the method depends on it. The triage breaks if those closest to the work do not feed what they know upward; pacing breaks if the people absorbing the change cannot say how it is landing; command breaks if the floor and the record are not visible to everyone the agent's actions touch. Transparency is not a courtesy here — it is what makes the method work.

Direction

A board, the owners — or you. The strategic call: what stays excellent, what we owe our people, and what must remain true of the business.

Module 1

Where would an agent acting on its own carry real consequence in our work — and are we reaching for efficiency when the prize is effectiveness, and the room to do what we could not before?

Module 2

Which of our work is strategically core, and must stay excellent, and which is commodity? And what do we owe the people whose work moves?

Module 3

What do we owe the people whose routine work moves — and is "up, not out" our actual plan, or only a phrase?

Module 4

Which way are we erring right now — haste that outruns our people, or a caution that has calcified into paralysis?

Module 5

Whose infrastructure, jurisdiction and rules does our tool ultimately answer to — and who sets the written floor it can never cross?

Module 6

What do we want to remain true of this business however the technology moves — and where on the shape do we mean to sit?

Stewardship

Whoever runs the change — or you. The hands on the transition: the triage, the pace, the gate and the record, the ground the work runs on.

Module 1

Hold any tool to the two plain tests before it acts: does it exceed a person at one bounded job, and does it hand back, by rule, everything that should stay human?

Module 2

Run the triage; set the readings; plan the "and the person" column; choose the pace, and the ground the work runs on.

Module 3

Plan each person's move before the agent is deployed; face the roles that genuinely cannot be raised early and straight, with the person in view.

Module 4

Choose the first small, reversible step; set the signals that say slow — errors up, trust down, people gone quiet — and the ones that say widen.

Module 5

Build the gate and the record into how the agent works, not into a promise to watch it; change the constitution only in the open.

Module 6

Steer the shape by the work in front of you, not a forecast; keep the written floor and the record intact as the structure thins.

Frontline

Team leads — or you. The ground truth: which processes really work, where they break, and who holds the knowledge no system has.

Module 1

Which of our processes would you not design this way if you were starting today — and where would speeding one up make it harder to change later?

Module 2

Supply the ground truth — which processes really work, where they break, and who holds the knowledge no system has.

Module 3

Whose knowledge would you struggle to rebuild if it walked out the door — and is it held where you'd expect, or somewhere easy to overlook?

Module 4

Which single process would you pilot first — and exactly how would you undo it if it went wrong?

Module 5

For each task you'd give an agent, what is the one rule that must always route to a human — and where would the record be a year from now?

Module 6

What might stop this shape arriving in our business — a market, a dependency, a force outside our control — and what would we do then?

Doing the work

The people closest to the task — including the newest. Two columns at every step: what you can contribute, and what you're entitled to see.

Module 1

Contribute: where you already hold the picture no software has — what this client does, the step that must never be skipped.  See: that the question being asked is "what will it do, and to whom?", not only "is it clever?"

Module 2

Contribute: "I run this — here's where it's broken, and I'd not design it this way" (that is step zero), and "where would I move?"  See: that the triage is being done with you, not to you.

Module 3

Contribute: say where your work could be raised, and where it would simply be lost — you know the difference better than anyone.  See: that the plan for your place is being made before the agent arrives, not after.

Module 4

Contribute: tell us when the pace has outrun the readiness, before the errors show — you feel it first.  See: that "as slow as the people need" counts you among the people.

Module 5

Contribute: flag where a boundary is missing, or where the agent could be talked past its limits.  See: the record of who decided what, and the floor that stands behind your work.

Module 6

Contribute: your knowledge of how the work really goes is what the new shape needs at its edges.  See: that what passes is the form, never the people — you remain among the authors.

Read down a single lens and you have one person's path through the course. Read across the four at any module and you have the conversation that module is meant to start — the same questions, surfaced openly, with no one kept from the harder ones.

Put the lenses to work

The same four roles run down the Process Triage Worksheet and into the capstone — the place to turn these questions on your own business.

Open the worksheet → Go to the capstone →