The core diagnosis is right: a capability that lives in only one person is a liability wearing a compliment. The 417-email audit is a sharp opener.
Where I'd push back is that the framework treats "stop answering that question" as mostly a design choice. In my experience, it's also a matter of trust. Leaders don't hoard decisions because the system lacks a heuristic; they hoard them because the first time they let go, something went wrong, and they never forgave the system for it. Architecture without that reckoning just produces a nicer-looking bottleneck.
The other gap: nothing here on what the leader does with the capacity they free up. Relocating capability into the org is necessary but not sufficient if the leader just fills the space with more meetings; you've built a better system carrying the same exhausted person.
Good structural thinking. Missing the emotional mechanics of why leaders actually cling.
I think you're right that trust is part of the equation. I'd argue that architecture and trust reinforce each other. Teams trust systems that repeatedly let them succeed, and good architecture provides the environment where trust gets built over time.
I also agree on the second point. The question of what a leader does with the capacity they free up is an important one. That's exactly where the next ARCHITECT framework is heading.
Really enjoyed this perspective. Great leadership is about building systems, not becoming the system
The core diagnosis is right: a capability that lives in only one person is a liability wearing a compliment. The 417-email audit is a sharp opener.
Where I'd push back is that the framework treats "stop answering that question" as mostly a design choice. In my experience, it's also a matter of trust. Leaders don't hoard decisions because the system lacks a heuristic; they hoard them because the first time they let go, something went wrong, and they never forgave the system for it. Architecture without that reckoning just produces a nicer-looking bottleneck.
The other gap: nothing here on what the leader does with the capacity they free up. Relocating capability into the org is necessary but not sufficient if the leader just fills the space with more meetings; you've built a better system carrying the same exhausted person.
Good structural thinking. Missing the emotional mechanics of why leaders actually cling.
Appreciate the thoughtful pushback.
I think you're right that trust is part of the equation. I'd argue that architecture and trust reinforce each other. Teams trust systems that repeatedly let them succeed, and good architecture provides the environment where trust gets built over time.
I also agree on the second point. The question of what a leader does with the capacity they free up is an important one. That's exactly where the next ARCHITECT framework is heading.