Leave with defensible priorities, protected time, and a simple way to review progress.
Module 02 · Playbook
Playbook: from busy to productive
Diagnose, decide, block, execute, and review. Each step leaves an observable artifact.
- Practice
- Observe one week, choose three priorities, protect focus blocks, and define evidence of progress.
- Transfer
- Repeat the system weekly and change one rule when evidence reveals recurring friction.
Make the work that deserves attention visible.
A full calendar does not prove progress. Without explicit criteria, urgent work displaces important work. Missing agreements also scatter team attention.
Diagnose, decide, block, execute, and review. Each step leaves an observable artifact.
Deliver a short activity log, three justified priorities, a protected calendar, and a review with decisions for the next week.
Full index13
00
Starting point
Starting point
Turn a real week into a visible priority system: three justified outcomes, protected blocks, and a final review.
Diagnose, decide, block, execute, and review. Each step leaves an observable artifact.
- Challenge
Constant activity can hide a lack of progress. The challenge is to separate urgency, maintenance, and value-creating work before filling the calendar.
- Practice
Observe one week, choose three priorities, protect focus blocks, and define evidence of progress.
- Evidence
Deliver a short activity log, three justified priorities, a protected calendar, and a review with decisions for the next week.
01
Chapter 01
Governing principle
Principle: Value before volume
Productivity means completing results that serve an explicit purpose.
Go deeperHow to apply it
How to apply it
- Write purpose and definition of done.
- Separate result, maintenance and coordination.
- Remove one activity that changes no decision.
- Name who approves the purpose and who reviews evidence.
Checklist
- Result written.
- Evidence defined.
- Purpose approved and evidence assigned.
- Decision rule
- No task becomes a priority without a result and evidence. Respect rights, sensitive data and shared commitments.
- Example
- Synthetic team example: Replace “answer email” with “resolve the three decisions blocking delivery”.
- Antipattern
- Using task count as proof of productivity.
- Expected evidence
- A defensible priority decision. It is available for the agreed review.
- Limit
- Necessary maintenance may remain; its cost must stay visible. Do not scale without reviewing dependencies and adoption.
02
Chapter 02
Time log
Principle: Observe before optimizing
A time log reduces dependence on vague recollection of the week.
Go deeperHow to apply it
How to apply it
- Capture start, end and output.
- Mark interruptions without judging them.
- Review gaps and doubtful data.
- Assign the record custodian and minimum read rights.
Checklist
- Period identified.
- Activities have outputs.
- Record custody and permissions current.
- Decision rule
- A conclusion requires an inspectable record. Respect rights, sensitive data and shared commitments.
- Example
- Synthetic team example: Record “10:00–10:35, meeting, output: date agreed”.
- Antipattern
- Backfilling the log to confirm a prior impression.
- Expected evidence
- Traceable time log. It is available for the agreed review.
- Limit
- The log describes the observed period, not a universal rule. Do not scale without reviewing dependencies and adoption.
03
Chapter 03
Value map
Principle: Classify to decide
The value map separates creation, support, coordination and reaction.
Go deeperHow to apply it
How to apply it
- Label each activity.
- Justify ambiguous cases.
- Total time only to describe, not promise impact.
- Agree with affected areas how ambiguous cases will be resolved.
Checklist
- Categories complete.
- Reasons concise.
- Affected areas consulted on classification.
- Decision rule
- A category without a reason remains provisional. Respect rights, sensitive data and shared commitments.
- Example
- Synthetic team example: Coordinating access is necessary support when it enables delivery.
- Antipattern
- Calling necessary but less visible obligations “noise”.
- Expected evidence
- Reviewable value map. It is available for the agreed review.
- Limit
- Classification depends on purpose and may change with context. Do not scale without reviewing dependencies and adoption.
04
Chapter 04
Priority matrix
Principle: Compare with shared criteria
The matrix exposes impact, real urgency, effort, dependency and risk.
Go deeperHow to apply it
How to apply it
- Define each criterion.
- Mark missing data.
- Review ties before deciding.
- Document the decision owner and dependency that may change it.
Checklist
- Criteria defined.
- Trade-off explicit.
- Decision accountability and dependencies visible.
- Decision rule
- Scoring informs; the accountable person decides. Respect rights, sensitive data and shared commitments.
- Example
- Synthetic team example: Two results tie: choose the one that clears a critical dependency.
- Antipattern
- Adding scores without explaining meaning or uncertainty.
- Expected evidence
- Three justified priorities. It is available for the agreed review.
- Limit
- A matrix does not replace judgment, rights or existing commitments. Do not scale without reviewing dependencies and adoption.
05
Chapter 05
Work limit
Principle: Limit active fronts
A work limit exposes what is active and what is waiting.
Go deeperHow to apply it
How to apply it
- List active work.
- Set a small limit.
- Define exception and closure.
- Publish the active limit and who authorizes an exception.
Checklist
- Limit published.
- Queue visible.
- Active limit and exception authority published.
- Decision rule
- Every active front has a next action or is paused. Respect rights, sensitive data and shared commitments.
- Example
- Synthetic team example: Keep three weekly results active and an explicit queue.
- Antipattern
- Treating every request as started work.
- Expected evidence
- Fewer simultaneous fronts with clear status. It is available for the agreed review.
- Limit
- The appropriate limit is contextual; no automatic outcome is promised. Do not scale without reviewing dependencies and adoption.
06
Chapter 06
Protected blocks
Principle: Reserve finished work
A protected block links priority, time and a concrete output.
Go deeperHow to apply it
How to apply it
- Prepare input.
- Declare output.
- Reserve margin and review.
- Confirm inputs, block owner and output reviewer.
Checklist
- Purpose visible.
- Output bounded.
- Inputs ready and output acceptance defined.
- Decision rule
- Redesign a block with no output before it starts. Respect rights, sensitive data and shared commitments.
- Example
- Synthetic team example: 09:00–10:30, produce a reviewable draft with five sources ready.
- Antipattern
- Filling the calendar without coordination or contingency capacity.
- Expected evidence
- Executable block. It is available for the agreed review.
- Limit
- A legitimate, documented exception may reschedule a block. Do not scale without reviewing dependencies and adoption.
07
Chapter 07
Interruption protocol
Principle: Respond with a rule
The protocol avoids deciding every interruption from scratch.
Go deeperHow to apply it
How to apply it
- List frequent interruptions.
- Assign response and timing.
- Define who activates an exception.
- Assign each channel an owner and escalation path.
Checklist
- Channels defined.
- Responses agreed.
- Channels, timing and escalation agreed.
- Decision rule
- Every exception records reason and next decision. Respect rights, sensitive data and shared commitments.
- Example
- Synthetic team example: Non-urgent messages are batched; critical incidents use the agreed channel.
- Antipattern
- Blocking requests without a valid urgency path.
- Expected evidence
- Focus protection rules. It is available for the agreed review.
- Limit
- The protocol does not remove surprises or replace response to real risks. Do not scale without reviewing dependencies and adoption.
08
Chapter 08
Weekly review
Principle: Review facts and rules
Weekly review connects results, deviations and adjustments.
Go deeperHow to apply it
How to apply it
- Compare plan and execution.
- Explain one deviation with facts.
- Schedule the next review.
- Give the review to the sponsor with an adoption decision.
Checklist
- Facts separated.
- Decision written.
- Sponsor informed and adoption gate decided.
- Decision rule
- Keep an improvement only while its evidence remains visible. Respect rights, sensitive data and shared commitments.
- Example
- Synthetic team example: Keep prior preparation; adjust message rule; review Friday.
- Antipattern
- Turning review into blame or impressions.
- Expected evidence
- Testable weekly rule. It is available for the agreed review.
- Limit
- One period is insufficient to claim general improvement. Do not scale without reviewing dependencies and adoption.
09
Chapter 09
Visible board
Principle: One view for decisions
The board combines priorities, blocks, status, evidence and next action.
Go deeperHow to apply it
How to apply it
- Publish three priorities.
- Update status and evidence.
- Remove unused fields.
- Configure board access by role and need.
Checklist
- Current status.
- Evidence linked.
- Board access limited by need.
- Decision rule
- The board must be understandable without reconstructing conversations. Respect rights, sensitive data and shared commitments.
- Example
- Synthetic team example: Priority A: active; evidence: draft; next: review Thursday.
- Antipattern
- Building an ornamental board that costs more upkeep than the work.
- Expected evidence
- Visible weekly system. It is available for the agreed review.
- Limit
- Visibility must respect sensitive data and access rights. Do not scale without reviewing dependencies and adoption.
10
Glossary
Glossary
- Result
- Observable change or delivery with a definition of done.
- Priority
- Result chosen over explicit alternatives.
- Protected block
- Reserved time with purpose, output and boundary.
- Dependency
- External condition or contribution needed to continue.
- Evidence
- Observable record used to review a claim.
11
FAQ
Frequently asked questions
Always three priorities?
It is a practice limit that forces comparison; adjust it when context requires and document why. The sponsor documents any change to the limit.
What about a real urgency?
Use the defined exception, record its evidence and explicitly reschedule or remove work. The exception authority records the decision.
How do I know it improved?
Compare equivalent records and decide on one rule; do not turn one week into a general promise. The review team decides before scaling.
May I share the board?
Only with the rights and detail level agreed for the people involved. Permissions determine which detail may be shared.
Repeat the system weekly and change one rule when evidence reveals recurring friction.
Turn a real week into a visible priority system: three justified outcomes, protected blocks, and a final review.
Checklist
From busy to productive- Priorities, owners and reviewers are visible.
- Dependencies and rights were reviewed.
- Exceptions and backup ownership are defined.
- Adoption is reviewed before scaling.