"I don't always have time to do it right, but I do have time to do it twice."

I said that to Katie Anderson on the podcast half as a joke because sometimes putting in the effort to get things right the first time is a major challenge with 100 other priorities nipping at your heels. She didn't just laugh it off. She treated it as a diagnosis, and a fair one. We plan, we do, we do some more, and then we move straight into the next thing. Whether the work actually produced what we wanted is a question most of us never circle back to ask.

Katie spent a decade studying Toyota's culture alongside Isao Yoshino, a leader who spent 40 years inside the company. She kept asking him for the secret. He kept telling her there wasn't one, then eventually landed on this: the closest thing to a secret was an attitude toward learning so built into daily work that nobody inside the company even noticed it was there.

Here's the version of that idea I've actually been able to use.

Frame the work as a hypothesis

Katie's tried to break down the trick in simple terms. Before you take an action, frame it as a hypothesis. We're going to do X, and we expect Y to happen. When the work is done, hold a short reflection. Did what you expected happen? If not, why not? What needs to change?

Three moves:

• State the action

• State the result you expect it to produce

• Check afterward whether reality agreed with you

Katie ties this to the plan, do, study, adjust cycle Toyota runs on. Her read on most Western organizations is that we run a shortened version. Plan, then do, do, do, do, do. The study and adjust phases fall off the back of the truck, because we've quietly decided that doing and creating impact are the same thing. They're not. Impact comes from the loop, not the doing alone.

The part that stuck with me

Katie has taught this material for years and still catches herself equating action with impact. I found that oddly reassuring and slightly annoying at the same time, because it means this isn't a knowledge problem. It's an identity problem. Years of being the person who gets things done builds a version of yourself that treats a pause as a threat, and reading a book on personal and professional development doesn't undo that overnight.

We measure our worth by what we can point at. Reflection doesn't produce anything you can point at in the moment, so it feels like slacking, even when it's the most valuable ten minutes in the week.

What this actually looks like in a small business

I've already put this to work in my own company, which is a better answer than telling you I plan to. We brought on a new team member, and the person training her is a strong doer, the kind who knows that if she doesn't handle something herself, it might slip through the cracks. Left alone, that habit defaults to execution, because executing is faster than teaching.

So we started framing the handover as a small hypothesis. We walk her through the context on this task, and we expect she'll be able to make the judgment calls herself next week. Then we check. Did she? Where did it hold and where did it wobble?

Two things changed. The training conversations got sharper, because a stated expectation is easier to evaluate than a vague hope. And the reflection stopped feeling like an interruption, because the hypothesis had already booked it a slot on the calendar.

One condition has to be true for this to hold. You have to be honest about when a moment is actually urgent. If the deadline is tomorrow, bring your best expertise and get it done. The trap is treating every task like the deadline is tomorrow, because that's exactly how the learning slot never arrives and you stay stuck in the fires that the missing learning keeps lighting.

A short audit worth ten minutes

• When your team finishes a project, is there a scheduled moment where you compare what happened to what you expected?

• Can you name the last time a piece of work changed how you did the next piece of work?

• What did rework cost you last quarter? If you can't estimate it, that's an answer too.

• When something goes wrong, does your team ask why, or does everyone just grab a bucket?

• Do your people know what result you expected from the task, or only what the task was?

These made me uncomfortable the first time I ran them on my own business. That discomfort is the useful part. It's pointing at exactly where the study and adjust phases went missing.

Start smaller than feels worthwhile

A two-minute reflection at the end of a task. One stated expectation before a project kicks off. You don't need a continuous improvement department. You need a sentence that starts with "we expect."

Building the systems that let a learning loop like this run on its own, especially across a distributed team, is exactly the kind of work we help clients with at Unbottleneck. If your business is growing faster than your processes are maturing, book a call with me and we'll find where the loop is breaking.

The full conversation with Katie Anderson is at leadsmarterpod.com. Her book, Learning to Lead, Leading to Learn, is worth the read too.