Six questions, one workflow, everyone in the room.

No single person can answer all six — that is the design. Engineering knows how fast ground truth arrives. Finance knows what an error costs. Operations knows where the minutes actually go. Where the room disagrees is the finding, and it surfaces in twenty minutes rather than in a post-mortem.

Workflow Canvas
01
Unit of work
What is the countable thing? If none exists, construct one or say so.
▸ Operations
02
Where the minutes go
Shade the split. Coordination is usually larger than anyone expects.
▸ Operations · the people doing it
Production
Review
Rework
Coordination
Waiting
03
Ground truth
What tells you it was right, and how long does that take to arrive?
▸ Engineering · Operations
04
Cost of an error
Stakes · risk tolerance · evidence needed · who is accountable. And: reversible?
▸ Finance · Legal · the function head
05
Context required
Could a competent new joiner do this from written systems alone?
▸ Operations · Engineering
06
Metric owner
A named person who would notice a 15% move without being told.
▸ The function head, in person
Verdict
Reading the six
Mostly strong → automate now, start at the autonomy the error cost permits.
02 or 06 weak → instrument first. Everything else is unprovable without them.
03 or 04 weak → build it, cap the autonomy. Slow feedback and expensive errors are structural, not temporary.
01 or 05 weak → not yet. Construct the unit or capture the context before building.

Both canvases are released under CC BY-SA 4.0. Use them, adapt them, teach them, charge for facilitating them. Attribution required; derivatives stay open. Companions to Building an AI-Native Company and the AI-Native Score.