Make your bed: the case for starting automation small
One workflow, automated end to end, working properly on a wet Tuesday, beats an eighteen-month transformation programme every time. Not because ambition is wrong, but because teams do not trust programmes. They trust the thing that already works down the corridor. Admiral William McRaven's Make Your Bed makes the same argument about people: the small thing finished properly is what earns the right to attempt the large one.
Admiral William H. McRaven's Make Your Bed grew out of a commencement speech and one deceptively simple instruction: if you want to change the world, start by making your bed. The argument is not about bedding. It is that completing one small task properly sets a standard that cascades, and that people who cannot be trusted with small disciplines will not hold up in large ones.
What is wrong with the grand programme?
Nothing, except that it does not produce a changed workflow.
| The grand programme | One made bed | |
|---|---|---|
| Starts with | A steering committee and a platform evaluation | One workflow people already resent |
| Needs permission from | Several people | Nobody |
| First visible result | Eighteen months, a deck | Weeks, a working process |
| What it proves | That the business can plan | That the business can change |
| If it fails | Expensively, and quietly | Cheaply, and you learned something |
| Teams' reaction | Wait and see | Ask for theirs next |
The right approach is McRaven's: pick one small task and do it completely, to a standard. The minutes of one recurring meeting. The diary of one site. The naming of one project's documents. Small enough that nobody needs a committee. Complete enough that it works under pressure.
The cascade is the point. One working automation becomes the proof, the playbook and the appetite for the next one, which is exactly what a well-designed pilot is for.
Do the small things really matter?
In construction records they are the whole game.
McRaven's inspections as a trainee turned on details that looked trivial, because the details were the evidence of the standard. Nobody thinks a file name matters until the adjudication, when the party whose records are consistently named, dated and filed reads as the party whose story is true.
Small disciplines are what credibility is made of. They are also exactly what automation performs without ever having a bad week: a machine does not decide the naming convention can slide this once.
Why can this not stay one person's win?
Because a private success is an anecdote, and anecdotes do not change an organisation.
Another of the book's lessons is that nobody gets through anything that matters alone. The small-start approach fails if it remains one enthusiast's project. The discipline is to share it: circulate the hours saved, hand the playbook to the next team, let the site manager who now gets his evenings back say so in his own words.
That is how one bed made becomes a culture rather than a story someone tells.
What happens when the novelty wears off?
This is where automated discipline quietly outperforms every motivational framework.
McRaven is clearest on the bad days: the standard is the standard, especially when you do not feel like it. Businesses meet their version about a month in, when novelty fades and the old shortcut whispers.
But the automated discipline does not need morale. The diary still writes itself during the tender rush. The records still file correctly through the December push. The system keeps the promise on the weeks when nobody has the energy to, and it never once decides it has earned a lie-in.
Start small. Finish it properly. Let it cascade. If you want to change the business, automate one bed's worth of work this month, and make it perfect.