What it feels like when it is working

You know it has worked when somebody objects to cancelling the weekly meeting.

Not when it runs. Not when attendance is good. When taking it away would cause an argument, because at that point people are getting something from it rather than doing it for you.

The other signs, in the order they usually arrive

Somebody outside the leadership team adds something to the ideas list, unprompted. It means the list is understood as a real route rather than a suggestion box, and it is the first evidence that this belongs to the company rather than to you.

A team stops something, and nobody flinches. No defensiveness, no long explanation, no career cost. The reasoning gets written down, and the next goal gets pulled.

And three of your senior people describe what the company is betting on, separately, in roughly the same words. Not because they memorised a page. Because they use it.

What I actually think will surprise you

Everything above is a process outcome, and process outcomes are not why anybody does this.

Here is the one that matters.

You will find out your team was better than your system let them be.

The people you thought were cautious were reading the room correctly, and the room changed. The people you thought did not take ownership were never given anything they could own, only things they could be blamed for. The person who never brought you bad news had watched what happened to somebody who did.

None of that was about their character. It was about what they had seen, and you changed what there was to see.

That is the part I still find genuinely good after a decade of doing this. Not the reporting or the pace, although both come. It is watching a leadership team discover that they had better people than they thought, and that the difference was never the people.

And a caution, because this is a book about design

None of this makes anybody happy on its own. A well-designed operating model reduces friction, wasted effort and the low background frustration of working hard on things that do not add up. It does not substitute for decent pay, decent management, or a business with a future.

Design what you can design. Do not ask it to carry what it cannot.

Where this goes, if you want it to

There is more, and it is deliberately not in this book.

Goals that take as long as the outcome takes rather than as long as the calendar allows.

Strategy that updates monthly on what was learned from the work.

Teams that stand up and down around a question rather than a function.

An operating model shaped around what your people actually need to do good work.

All of it is year two, and all of it is easier if you have done the six first, because the six contain their seeds.

Choices with the hardest thing named become an adaptive strategy.

Endings with reasoning break the goal free from the quarter.

Tests become continuous discovery.

A company that has run the six well for a year has been practising the next layer without being taught it.

But that is later, and the six on their own are worth a year.