Team, 

As leaders, our default instinct when something gets missed is often to look at the person closest to the miss. That’s normal. But at scale, that instinct becomes expensive and often incorrect.

More often than not, what looks like a people issue is actually a systems issue.

Strong organizations are not built on heroic effort or perfect memory.

They are built on systems that make the right behavior obvious, repeatable, and hard to miss. When something drops, slips, or stalls, our first responsibility as leaders is not correction - it’s diagnosis. As we head into next quarter, this is not a call to build more systems for the sake of feeling protected.

Overbuilt systems create drag, slow decision-making, and give the illusion of control and importance without delivering leverage.

A system built out of fear becomes a giant ugly cast … heavy, rigid, and unnecessary… instead of a precise band-aid that supports the work and then gets out of the way.

The standard we are aiming for when building systems is PRECISION.

We don’t ask, “What systems should exist in theory?”

We ask, “What actually broke?”

Every real miss is feedback. It tells us where clarity, ownership, feedback, sequencing, or visibility broke down.

The right response is not layering on process, but designing one clear mechanism that would have either prevented the miss or increased the likelihood of the correct outcome.

This is how we shift from spending time repairing to spending time preparing — without bloating the organization.

Non Obvious Questions to Ask When Something Gets Missed

What part of this relied on someone remembering instead of the system prompting?

Most failures don’t come from incompetence, they come from memory dependency. If success required someone to “just remember,” the system was already broken.

Where in the sequence did this fail — before execution, during execution, or after?

Leaders often jump to fixing the wrong moment. Misses almost always happen upstream (unclear trigger, ownership, or timing), not at the point of action itself.

What is the smallest system that would have made the right outcome the default?

Not the safest system. Not the most comprehensive. The minimum effective mechanism that would have prevented this exact failure - without adding unnecessary weight.

The goal is not zero mistakes. The goal is never paying for the same mistake twice.

Our job as leaders is to use real failures as design inputs and to build only what is minimally effective - not what looks cool or sounds impressive.

Carry on!

— Leila

Ps. Want to receive these memos in your inbox (completely free)?