The team will leave with a common Mini-SOP, review points, accountable owners, and evidence from a bounded pilot.
Workbook: design and test your workflow
Select a workflow, observe variants, agree on the standard, co-design the Mini-SOP, and run a pilot with a human owner.
Turn expert practice into a shared way of working.
When the method lives with one person, handoffs vary, review arrives late, and AI amplifies inconsistency.
Select a workflow, observe variants, agree on the standard, co-design the Mini-SOP, and run a pilot with a human owner.
A Mini-SOP with roles, inputs, steps, criteria, approvals, exceptions, and a team-pilot record.
How to use this workbook
Start in class, deepen through practice, and consolidate only with reviewable evidence.
- 01
Frame the caseState the case, desired result and evidence you want to observe.
- 02
Prepare the inputsGather what is needed, acknowledge boundaries and use the three preparation prompts.
- 03
Work in classComplete the essential practice and retain initial evidence.
- 04
Go deeperOpen each detail to review actions, criteria, examples and connections.
- 05
Consolidate and transferMeet the criterion, review the evidence and test the practice in another context.
Work on a shared workflow
Turn team work into a governed Mini-SOP with roles, rights, and testing.
- Use case
- Prepare and review an internal proposal.
- You are ready when
- Owner, reviewer, scope, and access exist.
Inputs
- Name roles
- Gather process, sources, and policies
- Define data and boundary
Define your case
Write only what is needed to frame the practice. These fields are neither saved nor sent.
Preparation prompts
Go deeper3 · Preparation prompts
Choose a checkable workflow
Bound a task with an observable outcome.
- Receives
- workflow context
- Produces
- Workflow brief
Describe task, frequency, outcome, user, and risk.
Prepare starting evidence
Separate records, sources, and assumptions.
- Receives
- Friction map
- Produces
- Evidence pack
List inputs and mark unsupported items as assumptions.
Set the human boundary
Define decisions, review, and stop conditions.
- Receives
- Mini-SOP v0.1
- Produces
- Assistance boundary
Name what a person decides, AI prepares, and when to stop.
Amplified work
Align owners, controls, and AI use so the team can deliver repeatably without weakening professional judgment.
Before you begin
Prerequisites
- Owner, reviewer, scope, and access exist.
Inputs
- Name roles
- Gather process, sources, and policies
- Define data and boundary
Limits
- Work with a bounded, authorized case.
- Do not include personal, confidential or restricted data.
- Stop when evidence, permission or an accountable reviewer is missing.
Select a workflow, observe variants, agree on the standard, co-design the Mini-SOP, and run a pilot with a human owner.
Prepare
Bound the workflow, roles, and dependencies before redesign.
Observe the current workflow
Reconstruct one case without improving it yet.
Go deeperQuality criteria
How to apply it
- Order real steps.
- Mark friction and handoffs.
- Separate facts from explanations.
Quality criteria
- Real start, finish, and owners.
- Friction linked to a moment.
- Produces
- Current map
- Example
- Business synthetic example: Proposal reconstructed by the team.
- Avoid
- Do not draw the ideal as current.
- Reflect
- What surprised you?
- Connection
- Feeds the diagnosis.
Define outcome and criteria
State why the workflow exists and what good completion means.
Go deeperQuality criteria
How to apply it
- Name user and outcome.
- Write checkable criteria.
- Set boundary and stop.
Quality criteria
- Supports accept or reject.
- Not based on speed alone.
- Produces
- Definition of done
- Example
- Business synthetic example: Proposal with owner and reviewer.
- Avoid
- Avoid “better” without a signal.
- Reflect
- Which criterion rejects the output?
- Connection
- Guides research and design.
Practice
Turn evidence into a governed, reviewable procedure.
Compare practices with sources
Compare practices and conditions with your case.
Go deeperQuality criteria
How to apply it
- Ask from friction.
- Keep source and boundary.
- Adapt, test, or reject.
Quality criteria
- Each practice retains provenance.
- Decision explains contextual fit.
- Produces
- Practice dossier
- Example
- Business synthetic example: Handoff compared with policy.
- Avoid
- Do not copy recipes without comparison.
- Reflect
- Which practice does not fit?
- Connection
- Brings options into the Mini-SOP.
Co-create the Mini-SOP
Turn map, standard, and sources into a concise guide.
Go deeperQuality criteria
How to apply it
- Write input and steps.
- Add criteria and exceptions.
- Assign contributions and review.
Quality criteria
- Can be followed without guessing.
- Includes manual path and version.
- Produces
- Mini-SOP v0.1
- Example
- Business synthetic example: Mini-SOP with RACI and escalation.
- Avoid
- AI does not approve the procedure.
- Reflect
- Which decision remains implicit?
- Connection
- Moves to controlled test.
Transfer
Pilot, transfer, and decide on bounded adoption.
Test, review, and version
Run a case, keep the log, and complete an AAR.
Go deeperQuality criteria
How to apply it
- Keep inputs and deviations.
- Compare with criteria.
- Authorize each adjustment.
Quality criteria
- Reconstructs decisions.
- AAR separates facts and changes.
- Produces
- Test report
- Example
- Business synthetic example: Non-sensitive pilot with independent reviewer.
- Avoid
- Do not hide failures.
- Reflect
- What changed because of evidence?
- Connection
- Needs a second check.
Check transfer
Repeat and observe what depended on the first case.
Go deeperQuality criteria
How to apply it
- Keep criteria.
- Log help and exceptions.
- Retain, adjust, or withdraw.
Quality criteria
- Comparable evidence.
- Changes with reason and owner.
- Produces
- Transfer report
- Example
- Business synthetic example: Another person runs and logs exceptions.
- Avoid
- One test does not prove transfer.
- Reflect
- What was genuinely repeatable?
- Connection
- Bounds adoption.
Test the workflow with a second team member and adjust only from pilot evidence.
Align owners, controls, and AI use so the team can deliver repeatably without weakening professional judgment.
Another person, same standard
Give it to someone who did not design it.
- Confirm permissions and roles.
- Record questions, escalation, and decision.
- Evidence
- Bounded-adoption report.
- Review
- After the transfer pilot.
Closing rubric
In progress
Owner, rights, criteria, or escalation are missing.
Pilot-ready
Assigns roles, protects inputs, and supports review.
Bounded adoption
Another person runs and escalates with evidence.
Playbook
Continue with the next resource in the journey.
Workbook → Playbook