Insights

Essays on execution architecture.

Field notes on what makes execution hold in a leadership team - and where it quietly breaks. Drawn from 15+ years leading inside Fortune 100 operations.

Accountability
The Andon Cord Nobody Pulled

Organizations see defects coming and stay silent - not because no one notices, but because pulling the cord costs more than letting the flaw through. How leaders invert that math.

Information Flow
What the Leader Couldn't See

Every update you receive has been filtered through dozens of small decisions about what's safe to surface. The compression is rational, predictable, and strips out exactly what you most need to know.

Decision Rights
The Reorg That Solved the Wrong Problem

Boxes move. Authority doesn't. Why most reorganizations redraw the visible artifact and leave the real problem - who actually decides what - exactly where it was.

Decision Rights
The Decision That Belonged to Three People

Shared ownership is structural ambiguity disguised as collaboration. The case for assigning every decision to exactly one owner - and what it costs when you don't.

Accountability
The Five Places Commitments Fail

Commitments rarely fail at the moment they're made. They fail later, at five specific structural points. The COMET standard names each one.

Diagnosis & Calibration
Why the Same Architecture Fails Two Different Teams

The same execution system thrives in one team and collapses in another. The difference isn't the system. It's whether anyone read the team before installing it.

Leadership Transitions
The 90-Day Window

The most consequential window when a new leader arrives isn't theirs to learn the organization. It's the organization's window to absorb them - and it closes faster than anyone designs for.

Methodology
The Structural Reason for 90 Days

90 days isn't enough to produce business outcomes. It's exactly enough to install the architecture those outcomes depend on - and measuring the wrong window is what kills good work.

Methodology
The Playbook in Their Own Language

The playbooks that get used are written in the team's own language, not the consultancy's. Why that's the difference between a system that gets carried and one that gets shelved.