|
Good Monday morning. This week I want to tell you about a night in Kyiv that took me years to fully understand. The story resolves in four minutes. The lesson took considerably longer.
|
ON AUTHORITY ARCHITECTURE
Four Minutes Resolution
I was at dinner at the Brazilian ambassador's residence in Kyiv with the Secretary of Agriculture. My COO called. One hundred containers were sitting outside processing plants in Brazil, ready to move, commercial clock running. Five days of discussions, and no resolution. An inspection interpretation question that nobody in the organisation had been able to settle.
I raised it across the dinner table. The Secretary called the head inspector in Brazil. Minutes later, the containers started moving.
Four minutes. After five days.
|
Every piece of information needed to release that cargo already existed inside the organisation. What was missing was not knowledge. It was authority.
— Rod Martin
|
The plant understood the documentation. The logistics team knew the shipments. The commercial team knew what was at stake. The authorization to finalize a straightforward interpretation had no structural path to the people who needed it. So it waited until someone at a dinner in Kyiv happened to be sitting next to the right person.
I felt like I had done something good that night. And I had. But the feeling concealed the real problem.
When a decision takes four minutes at your level, it usually waited three days to reach you. That gap — between where authority lives and where the work needed it — is invisible in any performance report. But it is accumulating cost in your organisation right now, quietly, every single week.
|
The question worth asking is not how to intervene faster. It is what would have to change for authority to reach the work without needing you to carry it there.
|
|
STRATEGIC MANAGEMENT OPERATING SYSTEM
Authority Architecture: The First Design Question
The Kyiv story is not an anecdote. It is a diagnostic. In every organisation where execution is underperforming, the same structural condition is present: authority is concentrated at a level too distant from the work it governs.
SMOS™ addresses this through Expectation Architecture — the structural design of where decisions are authorised, not just who makes them. What you build into the system, you no longer need to manage around.
|
|
THIS WEEK'S FOCUS
The Art of Managing Business Expectations
Rod Martin
The governing thesis of this newsletter in book form. Execution reliability is not a performance property — it is a structural one. Its governing condition is whether expectations have been encoded to survive distance, time, and load without reinforcement.
|
| 02 |
High Output Management
Andrew Grove
Still the most honest account of what management actually produces. Grove's argument that managerial output is the output of the organisation under a manager's influence lands differently once you have unblocked a hundred containers with a single phone call. Read it asking: where is output waiting on a call that should not need to happen?
|
| 03 |
The Hard Thing About Hard Things
Ben Horowitz
Not a framework book. A scar tissue book. Read it for the weight of what execution leadership actually costs — and what it produces when the architecture holds and the leader no longer has to carry every decision personally.
|
|
The containers moved. The client was satisfied. I received no formal recognition for it because, to the outside, nothing had broken. That is the paradox of invisible costs — they disappear when you fix them, so the organisation never accounts for how long they were running.
This week, ask yourself once: what is sitting in my organisation right now that only moves when someone like me is in the right room? Whatever the answer is, that is the design problem worth solving.
Rod Martin
Founder · T'ehnah Management Consulting
|
|
