Do the Small Thing Properly
By the end of this blog, you’ll know how to define what “properly completed” actually means, how to verify the small tasks that bigger outcomes depend on, and how to build a standard that survives repetition, fatigue and low visibility. You’ll also have a seven-day drill for improving one ordinary responsibility so nobody else has to repair your work later.
Everyone Remembers the Footprint
Apollo 11 landed on the Moon on 20 July 1969.
History remembers the astronauts.
The lunar module.
The photographs.
The flag.
The footprint pressed into the dust.
What history rarely photographs are the thousands of smaller tasks that made that moment possible.
Wiring.
Fasteners.
Seals.
Navigation.
Software.
Fuel.
Communications.
Spacesuits.
Procedures.
Testing.
Documentation.
Quality assurance.
The Moon landing was one extraordinary moment built on years of ordinary work.
Most of the people responsible for that work would never stand on the Moon.
Many would never appear in a history book.
But their work still had to be right.
That gives us the central principle of this article:
History remembers the footprint. The footprint depended upon thousands of people doing work that history would never photograph.
The Mission Was Larger Than Its Heroes
Neil Armstrong, Buzz Aldrin and Michael Collins accepted extraordinary responsibility.
They were also the visible end of a much larger human system.
Apollo required astronauts, but it also required:
Engineers.
Mathematicians.
Programmers.
Technicians.
Machinists.
Seamstresses.
Test crews.
Medical teams.
Contractors.
Mission controllers.
Administrators.
People building things.
People checking things.
People documenting things.
People noticing when something did not look right.
People passing information accurately to the next person.
That matters because we often misunderstand great outcomes.
We see the final achievement and assume greatness lives only in the visible role.
It does not.
Great outcomes are usually carried by more hands than the final photograph can hold.
Leadership means respecting apparently minor work because somebody else’s major responsibility may depend upon it.
A spacecraft cannot distinguish between famous work and anonymous work.
It only knows whether the component functions.
The same is true in ordinary life.
A customer does not care whether a mistake came from the “important” task or the “small” one.
They receive the consequence either way.
Small Does Not Mean Unimportant
Some tasks look insignificant because they take only a few minutes.
That tells us very little about their importance.
Tightening one fitting.
Entering one figure.
Checking one seal.
Labelling one component.
Returning one tool.
Testing one line of code.
Passing on one warning.
Recording one change.
Confirming one assumption.
None of these sound heroic.
But consequence—not appearance—determines importance.
Ask one question:
What happens downstream if this task is incomplete, inaccurate or unclear?
A five-minute task may protect hours of work completed by everybody who follows.
One wrong figure can corrupt a report.
One unlabeled file can waste half a day.
One unchecked link can break a customer’s path through a website.
One piece of equipment left unsafe can injure someone.
One promise not recorded can become somebody else’s surprise.
A small task often looks small only to the person performing it.
The person receiving the consequence may see it very differently.
Properly Must Be Defined
“Do a good job” sounds useful.
It is also vague.
What does good mean?
When is the task complete?
What has to be checked?
Who needs to know?
What evidence remains?
A proper standard should define:
The required result.
The method or boundary.
The accuracy required.
The safety requirement.
Who must be informed.
What evidence must be recorded.
When the work is genuinely complete.
Compare:
Check the equipment.
with:
Inspect the cable, connection, guard and emergency stop. Record any fault and remove unsafe equipment from use.
The second standard can be followed.
It can also be verified.
That matters.
A standard becomes useful when two people can look at the evidence and agree whether it was met.
Without a definition of done, people finish work at different points.
One person thinks the task is complete when the action stops.
Another thinks it is complete when it has been checked.
Another thinks it is complete when the next person can use it safely.
Leadership requires removing that ambiguity where consequence matters.
Workmanship Begins Before the Work
Quality does not begin with the first movement.
It begins before it.
Before starting:
Understand the requirement.
Gather the correct tools.
Check the latest information.
Remove foreseeable distractions.
Confirm the handover point.
Identify what could make the result unsafe or unusable.
Ask questions while correction remains cheap.
This is where good workmanship often separates itself from rushed workmanship.
A person eager to “get started” may begin before understanding the task.
Then halfway through, they discover:
The wrong version was used.
The wrong tool was selected.
The specification changed.
The customer expected something different.
A dependency was missed.
Now the work has to be repaired.
Preparation is not procrastination when it directly reduces avoidable error.
Care taken before the first movement often prevents repair after the final one.
Checklists Protect Attention
Competent people make mistakes.
Experienced people make mistakes.
Intelligent people make mistakes.
Fatigued people make more.
Repeated tasks create familiarity.
Familiarity creates assumptions.
Time pressure narrows attention.
Interruptions break sequence.
Stress reduces working memory.
Overconfidence encourages skipping steps.
That is why checklists matter.
A checklist does not replace judgement.
It protects essential steps from predictable human limitations.
A useful checklist should be:
Short enough to use.
Specific enough to verify.
Ordered where sequence matters.
Updated when the work changes.
Connected to action.
Treated as a minimum, not theatre.
The checklist is not there because the worker is incompetent.
It is there because the worker is human.
There is an important difference.
The best systems do not depend on perfect memory.
They support good judgement with structure.
Test Before Trust
Apollo hardware was not trusted merely because intelligent people designed it.
It had to be tested.
That principle applies almost everywhere.
Preview the page before publishing it.
Test the payment process before launch.
Perform the movement lightly before loading it.
Open the saved file before sending it.
Recalculate the figure.
Read the instructions from the customer’s point of view.
Confirm the repair survived ordinary use.
Testing asks a better question than:
Should this work?
It asks:
What happened when we tried it?
That shift is powerful.
Assumption becomes evidence.
Confidence becomes earned.
Problems become visible while correction is still possible.
Testing does not show distrust in the work.
It shows respect for the consequence.
Good Systems Expect Human Error
A strong system does not pretend nobody will make mistakes.
It is built knowing that mistakes will happen.
That may include:
Independent checking.
Clear tolerances.
Version control.
Standard naming.
Physical guards.
Warnings.
Redundancy.
Automatic validation.
Safe failure states.
A defined escalation path.
This does not remove personal responsibility.
It strengthens it.
Excellence is not a workplace where nobody ever makes mistakes.
That is fantasy.
Excellence is a workplace designed to detect mistakes before they become damage.
The same principle applies at home, in training, in business and in digital work.
We often ask people to “be more careful.”
Sometimes that is necessary.
But sometimes the better question is:
Why did this system allow one ordinary mistake to become a major problem?
Personal attention matters.
System design matters too.
Apollo 1 Revealed the Cost of Normalised Problems
The Apollo story includes triumph.
It also includes tragedy.
On 27 January 1967, Virgil “Gus” Grissom, Edward White and Roger Chaffee died in a cabin fire during a ground test for Apollo 1.
The failure cannot be reduced to one careless person or one overlooked detail.
Multiple risks aligned.
The spacecraft’s atmosphere.
Combustible materials.
Wiring concerns.
Hatch design.
The way the test itself was classified.
Technical issues.
Management decisions.
Assumptions.
Warnings that did not produce enough correction.
The deaths of three astronauts deserve more seriousness than a slogan about “attention to detail.”
The useful lesson is larger:
When warnings, assumptions and incomplete responsibilities accumulate, the failure belongs to the system—not only to the final person who touched the work.
After Apollo 1, hardware was redesigned.
Combustible materials were restricted.
Safety oversight improved.
Quality control became more rigorous.
That matters because excellence sometimes requires stopping and rebuilding the system itself.
Not merely telling the person at the end to try harder.
Report the Small Problem Early
People hide small problems for predictable reasons.
They do not want to look incompetent.
They do not want to delay the work.
They do not want to annoy the manager.
They do not want paperwork.
They do not want blame.
They hope the issue will disappear.
Sometimes it does.
Sometimes it grows quietly until somebody downstream inherits a much larger problem.
An early warning preserves options.
A useful report should answer:
What was expected?
What was observed?
What is the immediate risk?
What has been paused or protected?
Who needs to decide?
What evidence is available?
That is not weakness.
It is professionalism.
A person who reports a small problem early gives the system time to respond.
A person who hides it transfers uncertainty to everybody after them.
A small problem reported early is information. The same problem hidden until failure becomes an incident.
The Handover Is Part of Your Work
Some people declare a task complete when they stop touching it.
That is often too early.
A proper handover should explain:
What was completed.
What remains open.
What changed.
What was tested.
What could not be confirmed.
Where the supporting information is stored.
What the next person must do.
Compare:
It should be fine.
with:
The update is installed and the registration path has been tested on desktop. Mobile payment remains unverified and is recorded here.
The second statement respects the next person.
It tells them where certainty ends.
It prevents assumption.
It allows responsible continuation.
Your work is not complete when you walk away from it.
It is complete when the next person can use it responsibly.
That is part of workmanship.
Properly Is Not the Same as Perfectly
There is a danger in all of this.
Perfectionism.
Perfectionism sounds like high standards.
Often it creates waste.
Endless revision.
Unnecessary complexity.
Missed deadlines.
Attention spent on consequences that barely matter.
Fear of releasing useful work.
Avoidance disguised as excellence.
The answer is proportional workmanship.
High consequence: verify rigorously.
Moderate consequence: meet the defined standard and review.
Low consequence: complete the useful version and move.
A safety-critical component deserves more attention than the spacing in a casual internal note.
A payment system deserves more testing than a draft title.
A heavy lift deserves more technical control than an easy warm-up.
A legal agreement deserves more review than a routine message.
Excellence gives detail the attention its consequence deserves.
Perfectionism gives every detail unlimited attention.
Those are not the same thing.
Repetition Reveals the Real Standard
Almost anyone can do one visible task carefully.
The real standard appears later.
When the task becomes boring.
When it has been repeated fifty times.
When nobody is watching.
When the day is nearly finished.
When praise is unlikely.
When you already know how to do it.
When the same thing must be done again tomorrow.
Replace the equipment properly.
Enter the transaction accurately.
Name and store the file correctly.
Complete the final repetition with control.
Clean the work area.
Send the promised follow-up.
Record the change.
This is where workmanship becomes character.
Your true standard is not the care you produce for inspection.
It is the care that survives repetition.
That is why small things matter so much.
They are repeated often enough to expose who we become when attention is no longer exciting.
Inspect the Point Everyone Steps Over
Now apply this to your own life.
Choose one area:
Work.
Training.
Household.
Money.
Customer service.
Website management.
Food preparation.
Family commitments.
Ask:
What gets rushed because it looks minor?
What repeatedly needs correction?
Which problem has become “normal”?
Who receives the consequences?
What standard is currently assumed but unwritten?
What would proper completion look like?
How could it be verified quickly?
Do not search for the most impressive project.
Find the place where careless repetition is creating the greatest downstream cost.
That is usually where improvement is most valuable.
Build a Definition of Done
Choose one recurring task.
Write:
Outcome:
What must exist?
Quality:
What condition must it meet?
Safety:
What must be protected?
Check:
How will accuracy be verified?
Record:
What evidence must remain?
Handover:
Who needs what information?
Completion:
What makes the task genuinely finished?
Correction:
What happens if the check fails?
Keep it short.
If the definition of done is too complicated to use, it will not be used.
The objective is not paperwork.
The objective is consistency.
The Seven-Day Small-Thing Drill
For seven days:
Select one small recurring responsibility.
Write its definition of done.
Prepare the required tools before beginning.
Remove one predictable distraction.
Complete the task in the correct sequence.
Perform one verification.
Record or communicate the result.
Correct every miss without creating an excuse.
Improve one weak point in the process.
At the end of the week, ask:
Did the work become more reliable?
Did errors reduce?
Did the people downstream receive better work?
Did handovers become clearer?
Did the task become easier because the standard became more obvious?
What should remain in the process?
Then continue.
The instruction is simple:
Do one ordinary thing today in a way that nobody has to repair tomorrow.
The Moon Was Reached Before the Rocket Left
The Moon landing became visible in one extraordinary moment.
But the mission had been built long before that moment arrived.
In workshops.
Testing rooms.
Control centres.
Factories.
Offices.
Laboratories.
Training facilities.
Documentation systems.
Quality checks.
People inspecting something that looked small.
People recording a problem.
People correcting a component.
People following a checklist.
People handing information to the next person properly.
Direction identified the destination.
Standards defined acceptable work.
Preparation made quality possible.
Checklists protected essential steps.
Testing replaced assumption with evidence.
Reporting protected the wider system.
Handover respected the next person.
Repetition turned workmanship into character.
That is how large outcomes are built.
Not by treating every small task as unimportant because it lacks drama.
But by recognising that something larger may already depend upon it.
Define the standard.
Check the detail.
Report the problem.
Finish the handover.
Treat the small thing as though something larger depends upon it—because it usually does.