Leave with defensible priorities, protected time, and a simple way to review progress.
Module 02 · From busy to productive
From busy to productive
Turn a real week into a visible priority system: three justified outcomes, protected blocks, and a final review. This guide complements the official PDF without replacing it.
- 11 · Moments
- SHA-256
d728c9a2c7cf…
Official masterclass PDF
The official PDF is not tagged. Use this accessible HTML guide to follow its 11 moments.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.
Accessible HTML guide
Moments
Follow the content moment by moment. This guide accompanies the PDF; it does not replace its content or design.
- Core route
- 78 min
- With extended practice
- 104 min
Moments01 / 11
01 · Diagnose
Agree what activity creates progress and who reviews the evidence.
02 · Design
Assign priorities, owners, dependencies and compatible blocks.
03 · Sustain
Govern exceptions, review, rights and adoption of the system.
From activity to progress
Activity describes movement; progress requires a useful completed result. The team agrees the result and who will check the output.
Go deeperDiagnose
Key points
- Name the result before listing tasks.
- Use observable evidence to recognize progress.
- Application
- Take a recent task and rewrite it as a verifiable result.
- Check your understanding
- What fact would prove that you moved forward? State who will review the evidence.
- Short practice
- Rewrite one activity as result, action and evidence.
- Keep this idea
- Being busy is not the same as progressing.
- Connect to the next resource
- Carry the result into the interruption diagnosis.
From busy to productivePage 1
The cost of reaction
Reaction without a rule fragments the week and displaces chosen results. The interruption response preserves an exception authority.
Go deeperDiagnose
Key points
- Separate real urgency from perceived pressure.
- Record each context switch before explaining it.
- Application
- Review two interruptions and classify them as handle, batch, delegate or defer.
- Check your understanding
- Which interruption changed a justified priority? Name the authority for an exception.
- Short practice
- Set one default response for a recurring interruption.
- Keep this idea
- Reaction needs a rule, not blame.
- Connect to the next resource
- Use the record to identify value-creating work.
From busy to productivePage 2
Value before volume
Task volume does not show value; a result must serve a stated purpose. Affected areas review how their work is classified.
Go deeperDiagnose
Key points
- Separate value creation, maintenance, coordination and noise.
- Do not erase necessary maintenance: expose its cost.
- Application
- Classify five recent activities and justify one uncertain category.
- Check your understanding
- Which activity consumes time without supporting a necessary result? Confirm which area must validate the category.
- Short practice
- Place one ambiguous activity on the map and note the missing evidence.
- Keep this idea
- Value is argued, not assumed.
- Connect to the next resource
- Turn the map into a weekly intention.
From busy to productivePage 3
Intention before intensity
A concrete intention comes before effort: define what must change and for whom. The sponsor confirms purpose before asking for more effort.
Go deeperDiagnose
Key points
- Write a result with a definition of done.
- State the boundary that prevents uncontrolled expansion.
- Application
- Complete: “By week end ___ will be ready, proven by ___.”
- Check your understanding
- Does the statement help decide what stays out? State who approves the scope.
- Short practice
- Write one priority in a sentence and remove vague verbs.
- Keep this idea
- Direction comes before intensity.
- Connect to the next resource
- Test the intention against the real week map.
From busy to productivePage 4
Map the week
A week map turns scattered recollection into a reviewable record. The shared record respects agreed permissions and custody.
Go deeperDesign
Key points
- Include meetings, tasks, blocks and context switches.
- Describe facts before judging them.
- Application
- Reconstruct one day in blocks and mark each block’s output.
- Check your understanding
- Which period cannot be explained with sufficient evidence? Check record custody and permissions.
- Short practice
- Complete a morning, afternoon and close record for one real day.
- Keep this idea
- Observe before redesigning.
- Connect to the next resource
- Use the map to select only three priorities.
From busy to productivePage 5
Three priorities
Three priorities force comparison and make trade-offs visible. Each result keeps an accountable person and accepted trade-off.
Go deeperDesign
Key points
- Justify each priority with purpose and evidence.
- Record what is deferred and why.
- Application
- Rank five candidate results and keep only three.
- Check your understanding
- Which priority would move if a verified urgency appeared? State the trade-off accepted by the sponsor.
- Short practice
- Write three priorities and one explicit trade-off for each.
- Keep this idea
- Prioritizing also means deciding what not to do now.
- Connect to the next resource
- Test the three priorities with shared criteria.
From busy to productivePage 6
Decision criteria
An explicit matrix reduces decisions based only on pressure or preference. Dependencies are validated with those able to resolve them.
Go deeperDesign
Key points
- Compare impact, real urgency, effort, dependency and risk.
- Explain ties and missing data.
- Application
- Score two results with the same criteria and state the trade-off.
- Check your understanding
- What missing fact could reverse the order? Identify the dependency that could change the order.
- Short practice
- Review one priority against five criteria and mark one uncertainty.
- Keep this idea
- Visible criteria make a decision reviewable.
- Connect to the next resource
- Turn the chosen priority into a protected block.
From busy to productivePage 7
Protected calendar
A priority without reserved time loses to immediate work. Each block coordinates accountability, inputs and output review.
Go deeperDesign
Key points
- Each block needs purpose, output and a definition of done.
- Keep space for real coordination and contingencies.
- Application
- Design a 45–90 minute block with input, output and boundary.
- Check your understanding
- What must be ready before the block starts? Confirm who reviews the block output.
- Short practice
- Schedule a real block and record one valid cancellation condition.
- Keep this idea
- The calendar makes a priority executable.
- Connect to the next resource
- Define how you will defend the block.
From busy to productivePage 8
Focus defense
Protecting focus requires agreed responses to predictable interruptions. Critical channels keep an agreed escalation path.
Go deeperSustain
Key points
- Choose what to handle, delegate, batch, defer or discard.
- Make legitimate exceptions explicit.
- Application
- Write one rule for messages, urgent requests and context changes.
- Check your understanding
- Who may trigger an exception, and with what evidence? Define the channel for legitimate urgency.
- Short practice
- Rehearse a short response that protects a block without ignoring real urgency.
- Keep this idea
- A useful boundary includes an exception path.
- Connect to the next resource
- Test the rule for a week and record what happens.
From busy to productivePage 9
Evidence review
Review compares plan and facts; it does not reward or punish the feeling of effort. The review ends in a documented adoption decision.
Go deeperSustain
Key points
- Record results, completed blocks and deviations.
- Keep one useful rule and change one concrete friction.
- Application
- Compare one planned priority with its evidence and choose keep, adjust or remove.
- Check your understanding
- Is the explanation factual or merely convenient? Name the decision that belongs to the sponsor.
- Short practice
- Write one learning, one decision and the evidence behind both.
- Keep this idea
- Review turns experience into a testable rule.
- Connect to the next resource
- Integrate the findings into a visible board.
From busy to productivePage 10
Visible system
The weekly system puts decisions and evidence in one view for action and review. The board shows only authorized, necessary data.
Go deeperSustain
Key points
- Show priorities, blocks, status and next decision.
- Keep the system small and current.
- Application
- Create a one-page view with three priorities and their next evidence.
- Check your understanding
- Can the state be understood without reconstructing conversations? Review the right to access status.
- Short practice
- Remove one field that changes no decision and add the missing fact.
- Keep this idea
- Visibility should serve the next decision.
- Connect to the next resource
- Repeat the cycle with one improved rule.
From busy to productivePage 11
Workbook
Continue with the next resource in the journey.
Masterclass → Workbook