
You're in a weekly business review. Ten people around the table. You give out action items—maybe ten across the hour. Everyone nods. Some take notes. Some don't.
Next week, you walk in. You remember three of those items. You ask about them. Two are done. One person looks confused—they understood the ask differently. Seven items? You don't even remember giving them.
Nobody reminds you. Nobody follows up. Those seven actions dissolve into nothing.
This happens everywhere. I've seen it across a large number of companies—startups, mid-size, and large ones. I lived it myself—until I joined Amazon and was forced into a system that made this problem disappear.
I didn't appreciate it at first. It felt bureaucratic. Why do I have to enter this in a tracker right now? Why can't I just send an email later? But after a few months inside the system, I understood why it works. The discipline isn't overhead—it's the mechanism that makes coordination possible at scale.
I've deployed this system everywhere I've worked since. It's not my invention. It's a battle-tested approach I learned by being inside it.
The Real Cost.
Here's what actually breaks when action items slip:
You train people that follow-through is optional. Miss a few follow-ups, and your team learns the pattern. "Boss will forget anyway." Your words lose weight. The meeting becomes theater.
Coordination overhead explodes. Without a system, you're chasing people on Slack, sending reminder emails, trying to remember who said what. You become the bottleneck.
The same problems recur. That action item you forgot? It was supposed to fix something. It didn't get done. The problem resurfaces three months later, and everyone acts surprised.
The fix is embarrassingly simple. But most teams don't do it—because it requires discipline, not technology.
The Forcing Function.
The system has three components: a format, a set of rules, and a recurring meeting that makes dodging impossible.
The Format.
Every action item gets recorded with these fields:


