Office / Simple improvement / worked example

Give the request a clear next step

Bring a familiar frustration and build a small test.

Take the full example with youPhotos. People. A practical plan.

Project timeline, actions for every S and checks before completion.

Open sample PDF Free to read. No sign-in needed.

Generated illustration: Give the request a clear next step, starting condition — Generated illustrations. The concept shows a possibility, not a completed improvement or verified safety result.

Generated concept: a possible improved arrangement for Give the request a clear next step — Generated illustrations. The concept shows a possibility, not a completed improvement or verified safety result.

Learn it, then try it

Understand the method
behind this example.

Two illustrated lessons with practical steps, a question to try and feedback. Read online or follow the teaching pages in the full report.

Read this illustrated lesson →Facilitator guide, workbook & answers →

A clear starting point

Make the problem
small enough to work on.

A fictional office request. Remove confusion while keeping the decisions that matter.

Sample baseline7 handoffsper request

Proposed goal3 handoffsnext-route goal

Illustrative starting figures. The goal has not been achieved.

Office / Simple improvementOPEX field notes

Give the request a clear next step

A fictional office request. Remove confusion while keeping the decisions that matter.

Sample starting point7 handoffsper request

Goal to work towards3 handoffsnext-route goal

01

Follow one request

02

Name the next step

03

Try a simpler route

04

Ask what improved

Follow one requestName the next stepTry a simpler routeAsk what improved

A worked example to learn from. Sample figures and people; targets are not achieved results.

People, timing and a clear finish

A plan the team can follow.

Read the full report ↗

Project completion timeline

Planned finish · Day 10

Follow five requestsEva · Coordinator

Day 1–2 · Record every transfer and required decision.
Agree one ownerKai · Team lead

Day 3–4 · Every request has a visible accountable owner.
Try the new routeSol · Service

Day 5–8 · Keep required approvals and record rework.
Review togetherEva · Coordinator

Day 9–10 · Compare the route and check that quality held.

Proposed timing and fictional owners. Close each action after its check is met; a date alone does not prove completion.

Actions for each S

Planned finish · Day 10

SortSeparate current requestsEva · Coordinator
Identify active requests and obsolete working copies while preserving required records and the current request history.

Day 1–2 · Each of the five traced requests has one current record and no lost required information.
Set in orderMake ownership easy to seeKai · Team lead
Give each request status one receiving owner and a clear place in the shared work queue.

Day 3–4 · The next owner and next decision are visible without an extra handoff.
ShineReset the shared deskKai · Team lead
Clear loose duplicate notes and reset the shared workspace, reporting recurring equipment or access problems.

Day 3–5 · A colleague can take over the work without searching through loose notes or exposed personal details.
StandardizeAgree the handoff checkSol · Service
Write the minimum ready-to-pass information and the receiving acknowledgement for the trial route.

Day 6–6 · Sender and receiver agree the same acceptance condition for the five trial requests.
SustainReview the next requestsEva · Coordinator
Follow comparable new requests through the remaining trial days, retaining their actual handoff counts and comments.

Day 7–10 · Day 10 records what to keep or revise; the three-handoff goal stays unverified until measured.
SafetyProtect information and workloadKai · Team lead
The team lead checks access rights, required decisions and workload before the trial and at its review.

Day 1–10 · Privacy and approval controls remain in place; an unresolved concern has a receiving owner.

Proposed timing and fictional owners. Close each action after its check is met; a date alone does not prove completion.

Bring the idea back to your work

Start the conversation with your team.

Use the report to choose one area, name the next action and agree how you will check it. Try a photo from your own workplace, then turn the possibility into a practical plan.

Try my own workplace ↗Keep this sample report ↗Open my workspace ↗

Keep exploring

Another useful starting point.

See every example →

Give the request a clear next step

Understand the methodbehind this example.

Make the problemsmall enough to work on.

Give the request a clear next step

Follow one request

Name the next step

Try a simpler route

Ask what improved

A plan the team can follow.

Project completion timeline

Actions for each S

Start the conversation with your team.

Another useful starting point.

Find it. Use it. Reset it.

Make the morning easier

Keep the assembly line ready for the next frame

Understand the method
behind this example.

Make the problem
small enough to work on.