Every morning during Army training, we stripped perfectly good beds. Then, a few minutes later, we raced to remake them… Except we weren’t allowed to race.
No running.
We’d start the morning by completely stripping our beds. Bedding over our right shoulders, we’d line up in the hallway, count off, and receive our morning orders, which would include instructions along the lines of:
Make your bed. Get dressed. Brush your hair. Brush your teeth. Be ready.
And we’d be given a very short amount of time to do it. Short enough that it was impossible to do everything yourself. Which was the point.
We shared rooms, and we quickly learned that the only way to meet the deadline was to work together.
While two people made a bed, someone else might be getting dressed. Someone would help straighten a uniform. Someone else might be checking that everyone had what they needed.
And, no running.
There were no excuses. Just a group of people trying to get the entire room (and ourselves) ready before the clock ran out.
When time was called, we’d line up again in the hallway, count off, and wait for inspection.
And then came the part that made the whole exercise memorable, even 7+ years later…
If someone’s uniform wasn’t right, or someone’s bed hadn’t been made correctly, everyone reset.
Every bed would be stripped, and we’d start all over again.
Hospital corners still haunt me.
At the time, it was easy to question what the point was.
Why were highly capable adults spending so much time making beds? Why did the exact way a sheet was folded matter? Why should everyone have to start again because one person’s bed wasn’t right?
Years later, I finally understand; it wasn’t really about the beds.
The bed isn’t the point
Admiral William H. McRaven famously talks about the importance of making your bed in Make Your Bed. His point is simple; start the day by accomplishing a small task. It creates a sense of pride, reinforces discipline, and gives you momentum for the things that follow.
However, my experience of making beds in the Army taught me something slightly different.
Making your bed wasn’t an individual act of discipline. It was a team sport.
You could make your own bed perfectly, but if the person next to you wasn’t ready, you weren’t ready.
You could be completely dressed, teeth brushed, hair done to army standard and standing to attention along the wall of the hallway (lines).
It didn’t matter if the team wasn’t finished.
That distinction has stayed with me.
Because in work, and particularly in teams, we often think about completion at an individual level.
I’ve finished my task. I’ve sent the email. I’ve done my part. It’s with the next person now.
But that’s not the same thing as getting the job done.
A team doesn’t succeed because every individual completes their own checklist. It succeeds when the collective outcome is achieved.
You can do it alone, you just can’t do it as quickly.
The timeframe we were given was deliberately uncomfortable (I remember 7 minutes being the magic number a lot of the time).
It was enough time to get everything done if we worked together. But, it wasn’t enough time if everyone tried to do everything themselves.
That was one of the earliest lessons I learned about teamwork.
You can work alone to achieve the result you want. But you’ll often get there faster with a team.
The trick is that teamwork isn’t simply about dividing the work. It’s about trusting other people with the work. Which sounds obvious, but isn’t.
If I’m working on something important, my instinct can be to do it myself; I know how I want it done, I know what “good” looks like, and often, it can feel faster to just take care of it.
But that’s a trap.
The more responsibility you take on, the more you become the bottleneck. And if you’re building a business, leading a team, or trying to accomplish anything larger than yourself, eventually you have to move from:
“How do I get this done?”
to:
“How do we get this done?”
It’s a one-word difference that makes for a completely different question.
Trust is built in the small things
There was also another lesson hiding in those mornings…
You had to trust the people around you.
If someone else was making your bed while you were getting dressed, you had to trust that they’d do it properly. Not approximately, not “good enough.” Properly.
Because their work could affect you, and yours could affect them.
That creates a different kind of relationship between people. You aren’t just responsible for your own output. You’re responsible for being someone other people can rely on.
That’s what trust actually looks like in a team. Not a motivational poster, or a quarterly off-site. Not someone saying, “We’ve got to trust each other.” Trust is built when I know that if I hand something to you, you’ll take ownership of it. And you know the same is true when you hand something to me.
The goal isn’t for everyone to do things exactly the same way. The goal is for everyone to care about the standard.
When one person slips, everyone feels it
At the beginning, the collective punishment felt harsh. One person’s mistake meant that everyone started again. But there’s an uncomfortable truth in that which applies directly to teams (that’s also much easier to accept in hindsight, ha):
Our work is interconnected.
A missed detail in one part of a business can create problems somewhere else. A salesperson can close a fantastic deal, but if the delivery team can’t fulfil it, the company hasn’t succeeded. A designer can produce brilliant work, but if the product isn’t launched, the work hasn’t achieved its purpose. A founder can have a brilliant strategy, but if the team doesn’t understand it, the strategy doesn’t matter.
We like to separate responsibility into neat little boxes. That’s their job. That’s my job. I’ve done what I was supposed to do.
But customers don’t experience your organisational chart. They experience the outcome. And sometimes the thing that matters most isn’t whether you did your job. It’s whether we did ours.
Standards matter most when you’re under pressure
It’s easy to have high standards when you have plenty of time. However, the real test comes when the clock is running down. When you’re tired and busy, when you’ve got ten other things to do. That’s when the little details start to feel optional.
The Army had a simple answer to that. They’re not optional.
The hospital corners still need to be right, uniforms still need to be correct, boots still need to be polished.
Not because anyone particularly cares about a bed, but because you’re practising what happens when the stakes are higher.
If you learn to maintain standards when something feels trivial, you’re more likely to maintain them when something actually matters.
It’s the same reason businesses have processes, checklists and quality controls. The details are rarely important because of the details themselves. They’re important because they reveal something about the standard you’ve chosen to operate at.
How you do one thing is how you do everything.
I’ve heard variations of that phrase throughout my life.
In the Army, this couldn’t be more true. The bed was a very low-stakes environment in which to practise discipline. Nobody’s life depended on whether I got a hospital corner right, but the behaviour was being rehearsed. Attention to detail, following instructions, working under pressure, trusting the person beside you.
Taking responsibility for your part; helping someone else when they needed it, and understanding that your actions had consequences beyond yourself.
Those behaviours matter a lot more when the stakes aren’t a perfectly made bed. But, they matter when you’re responsible for people, when you’re responsible for customers, when you’re making decisions with incomplete information, when the business is under pressure, when things don’t go according to plan.
The Army wasn’t really teaching us how to make beds. It was teaching us how to behave when the clock was running, the standard was high, and other people were relying on us.
Are we done?
And perhaps the biggest lesson I took from those mornings is a subtle change in language.
Not:
“Am I done?”
But:
“Are we done?”
That one word changes the way you think.
“Am I done?” is individual. “Are we done?” is collective.
The first asks whether I’ve completed my responsibility, the second asks whether the outcome has been achieved.
Good teams understand the difference. They don’t just protect their own piece of the work. They look around, they notice who’s struggling, they help, they communicate and they pick up the things that fall between the cracks.
Because sometimes the person beside you needs five minutes of help to get the whole team over the line.
And sometimes you’ll be the person who needs the help.
That’s not weakness, that’s teamwork.
Every morning, we stripped our beds and put them back together again. At the time, it seemed like an exercise in pointless perfection. But, looking back, it was one of the simplest lessons in teamwork I’ve ever received.
Your job isn’t finished when your part is finished.
Your job is finished when the team is ready.
And sometimes, getting everyone there requires a few hospital corners.
