Automattic's lesson is not which tool to use. It is which coordination surface to make primary: written, durable, time-zone-neutral.
When you build operating habits on top of that surface, distance becomes a non-issue and synchronous time becomes a scarce, intentional resource.
The location question is not the strategy question.
The strategy question is whether your team can make decisions without you in the room. Most cannot. That is not a remote work issue. That is a design issue.
If your operating handbook was deleted tomorrow, would your organization still function? GitLab can answer that question. Most companies cannot.
Flexibility is not the input. Flexibility is what becomes possible after the structure is built.
Flexibility was never a strategy. It was the moment of choice. The strategy is what got designed afterward.
The teams winning at hybrid did the work most teams skipped: explicit decision rights, written-first defaults, designed cadence, learning treated as infrastructure.
Notice the meetings that exist to recover context that should have been written down.
Notice the decisions that reversed because no one knew who owned them.
Each is a structural gap your team is paying for in coordination time. Flexibility is not the absence of structure.
Toyota's most copied tool is the andon cord. Toyota's least copied design is what makes the andon cord work: standardized work, jidoka, leader-as-teacher.
Most organizations want the cord without the system around it. That is why most lean transformations fail.
Style is what your team imitates when you are in the room.
System is what your team executes when you are not.
If those two things produce different results, you have not built leadership. You have built a habit.
The performance proof is simple: durability under absence.
At Mayo Clinic, CEO transitions read as scheduling events, not crises. That is what designed leadership looks like.
Most institutions confuse copying a Mayo program with copying Mayo's system. The program is visible. The governance, committee architecture is what actually scales
Most organizations don't have a leadership problem. They have a dependency problem misdiagnosed as one.
Style is visible. Systems are durable. Charisma can win a quarter. Architecture wins a decade.
Walk your org this week and find the meetings that lose direction when one person isn't there.
Find the decisions that wait for that person.
Find the team whose quality drops when their manager is out.
You haven't found a people problem. You've found a design gap.
Which leaders are carrying more than they should?
That’s usually where the system is lightest.
If execution quality changes dramatically by manager,
you are looking at architecture, not just ability.
Ritz-Carlton is not just a service story.
It’s a reinforcement story.
Daily repetition is how standards survive turnover.
Leadership systems are built through rhythm.
Not inspiration.
What teams review consistently, they deliver more consistently.
Amazon’s real scaling asset isn’t just size.
It’s shared leadership language.
When judgment is codified, consistency becomes easier to reproduce.
If leadership expectations only exist in senior leaders’ heads, they won’t scale.
The moment they enter hiring and evaluation.
Organizations become leader-dependent because it feels efficient.
One strong leader can resolve what the system hasn’t designed.
That works, until it doesn’t.
The real danger isn’t strong leaders.
It’s systems that never learned to work without them.
Where is your organization still relying on personality to stay coherent?
That’s where scale will eventually create strain.
The hidden cost of style-based leadership is volatility.
Performance rises and falls with the person, not the system
Toyota is a useful correction to style-based leadership thinking.
Performance scaled because leadership was built into the work.
That is what systems do.
Strong leadership systems don’t just direct work.
They teach people how to see waste, solve problems.
McDonald’s is not a charisma story.
It’s a systems story.
Scaled leadership comes from teachable standards, not exceptional personalities.
The question isn’t whether a leader is talented.
The question is whether the leadership model can be taught.
Most leadership advice is personality advice.
That’s useful until the organization grows.
Style may energize people.
Systems are what keep performance stable.
The test of leadership is not how a leader performs in the room.
It’s whether the organization still works