Run a capacity experiment and read its record honestly
Examine the book’s strength-first argument through its narrative contrasts, philosophical account of courage and proposed stress model. Design a proportionate three-domain practice, preserve recovery and genuine limits, and evaluate whether repeated action serves a useful purpose rather than treating discomfort or ledger scores as ends in themselves.
Allow about 100 minutes for reading, learning and immediate practice. Multi-day exercises run alongside later lessons.
Learning objectives
Construct a complete six-step implementation plan using the chapter’s exercise set.
Interpret adherence and consequence records without causal overclaiming.
Distinguish a thirty-day capacity pilot from Chapter 9’s larger-project system.
Read before practising
Assigned source readings
The book text is the source. The lesson, invented cases and practice tasks are accompanying teaching material. Page numbers below refer to the downloadable full-book PDF, whose pagination can differ from the manuscript’s printed contents.
Source: The Architecture of Excellence: Habits, Virtue, and the Making of a Life Worth Judging. The supplied source text has not been rewritten.
Develop the argument
The lesson
Audit situations rather than global identities
The exercise set begins with three lists: physical, psychological and moral situations that currently overwhelm the learner. A situation is more informative than a noun. Administration does not reveal the task, while opening an overdue renewal letter and identifying its next deadline does. The source then asks which situations a slightly stronger version of the learner could handle. Use that question to locate feasible development opportunities, not to assume that every difficulty is caused by personal underdevelopment. Some situations require changed conditions, shared responsibility or specialised support rather than individual effort alone.
The second and third steps turn the audit into a physical base and voluntary-hardship choices. The book proposes a thirty-day physical commitment, one daily small useful action and one weekly larger step. Record these as separate commitments with realistic frequency. A three-times-weekly practice should not generate four apparent failures on its unscheduled days. If load increases, it should follow evidence that the current practice is suitable and manageable, not a requirement to make every day harder. A longer observation window does not require a larger dose.
Repair, specify and differentiate the system
Step four selects a moral correction with a deadline. The important distinction is between repairing an actual wrong and performing self-punishment. A useful repair identifies the affected commitment, the action within the learner’s authority and the evidence that it occurred. It does not require public disclosure, unsafe confrontation or acceptance of blame unsupported by facts. In a course exercise, learners may use an invented case. A learner’s grade should never depend on revealing personal health, financial or relationship information.
Step five specifies the three Morning Tax components and records them; step six distinguishes this micro-practice from Chapter 9’s larger Hard Thing system. The distinction prevents scope creep. This chapter establishes the principle of purposeful, repeatable difficulty and a small daily start. It does not require every avoided project to be resolved in a month. A coherent contract names what is being tested, what is outside scope, how missed days are handled and when the plan will be reviewed. Signing a plan can signal intention, but the signature is not evidence of implementation.
What the ledger can and cannot conclude
The closing narrative projects the opening contrast across a decade. The author imagines avoidance narrowing a life and repeated capability-building producing greater steadiness. This supplies a long-horizon argument about accumulation; it is not a validated forecast for an individual. A dense ledger may show consistent practice, but it cannot guarantee safety from illness, bereavement, economic shock or overwhelming conditions. Likewise, an incomplete record can reflect illness or disrupted opportunity rather than the future collapse predicted by the rhetoric. Treat the narrative as a prompt to examine trajectories, not a prophecy.
At review, ask four separate questions. Were the agreed actions performed? Were they appropriate for the learner’s circumstances? Did a relevant capability or obligation improve? What costs or unexpected effects appeared? These questions can yield different answers: high adherence with no useful result suggests redesign; low adherence during a genuine emergency suggests a smaller restart or different support. Preserve the actual record rather than retroactively changing the completion rule. Compare the plan with its outcome, identify a plausible explanation and state what remains uncertain. The defensible product is a better next experiment and an honest account of this one, not a verdict on the learner’s value.
Worked example · invented for this course
Original course example: A pilot that needs redesign
In this invented case, Theo plans three weekly movement sessions, a daily ten-minute archive task and one correction to an inaccurate club inventory. After a week, the movement routine fits, six archive sessions are logged, but no archive item can be found more easily.
Verify the record: scheduled movement opportunities and actual sessions are counted separately; six archive sessions really occurred.
Inspect the archive outcome: Theo has repeatedly renamed folders without defining a retrieval system.
Keep the useful movement commitment and the completed inventory correction; do not discard the whole plan because one component failed.
Revise the archive action prospectively to index ten items using an agreed naming rule, then run a retrieval check.
What follows: The review distinguishes adherence from effectiveness. Theo has evidence of effort and of a design problem, not evidence that effort guarantees improvement or that the entire experiment failed.
Train the skill
Practice and evidence
1. Build the complete six-step plan
Use a fictional adult with two fixed obligations and one material constraint. Complete the strength audit, base, daily and weekly hardship choices, moral correction, Morning Tax and Chapter 9 distinction.
Deliverable: A two-page thirty-day plan with a seven-day pilot and review criteria.
Identify a specific situation in each domain.
Specify frequency, cue, completion evidence and permissible adaptations.
Include a stop or redesign rule and protect recovery.
Review criteria
Total available: 10 points
Coverage 4 points
Includes all six source steps and their distinct purposes.
Design 4 points
Makes commitments testable, feasible and proportionate.
Boundaries 2 points
Avoids unsafe prescriptions and compulsory disclosure.
2. Interpret an imperfect ledger
Invent a fourteen-day record with scheduled rest, a genuine interruption, a completed task with no benefit and an avoided useful task. Explain the different implications.
Deliverable: A fourteen-day record plus a 400-word review.
Do not count unscheduled days as failures.
Keep completion data distinct from context and consequences.
Recommend one continuation, one change and one unresolved question.
Review criteria
Total available: 10 points
Data integrity 4 points
Preserves actual events and denominators.
Reasoning 4 points
Separates adherence, suitability, effectiveness and external constraints.
Revision 2 points
Proposes a justified change without universal forecasts.
Transfer the learning
What evidence would persuade you to change a practice you have followed faithfully?
Notes remain only in this tab. They are not submitted or saved automatically. Download a copy before leaving. Use a fictional case if you prefer not to record personal information.
Formative self-check
Test your understanding
Choose an answer, then check your reasoning. These open practice questions show their explanations and do not count towards a secure examination or certificate. Nothing you enter is sent to a server.