The Notebook Proves the Point
I keep a notebook. Not a leather-bound journal I bought at an airport. A real one. Sprawling and unruly, full of meeting notes and email threads and half-finished strategies and slide screenshots from sessions I half-attended. I titled it “Mechanisms.” I added to it for years without thinking much about what it said about me.
Then one day, I read it back and realized the notebook is the argument.
Mechanisms are how intentions become outcomes. They are the distance between wanting something to happen and making something happen. Every leader has goals. Not every leader builds the thing that produces them.
The word itself comes from the Greek for machine. A machine does not forget. It does not have a bad week. It does not let the urgent crowd out the important. That is precisely the point.
What a Mechanism Actually Is
I sat in 2x2s for years and heard the word thrown around. Mechanisms. I nodded. I thought I understood it. I didn’t. Not yet.
Understanding it took watching the difference between teams that intend things and teams that produce them.
A Monday morning email to my team could be improvised each week and written whenever I got to it—skipped when the quarter got heavy. Or it could be a template, a cadence, a rhythm the team learns to expect. The first version has a good intention. The second is a mechanism.
An industry cohort strategy could remain a topic of conversation with my manager. It could live in my head, get discussed in a team meeting, and gradually lose its shape. Or it could become a written proposal. Shared for review. Brought to a VP. Operationalized. The first version is an idea. The second is a mechanism.
A new way of selling could be announced in a Slack message and forgotten by Thursday. Or it could be a two-day in-person immersion with prerequisites named, attendees mapped by city, facilitators confirmed, and a follow-up email sent the same afternoon. The first version is compliance. The second is adoption. One of those actually changes behavior.
The difference is never the idea. The difference is whether someone built the thing that runs the idea.
Amazon Understood This Early
I spent my first years at AWS wondering why everything has a name. The MBR. The 2x2. Narrative Documents (Six-Pagers). Bar Raiser. Working Backward. One-Way and Two-Way Doors. It felt like bureaucracy dressed up in frameworks. It isn’t.
These are mechanisms. They are not processes for their own sake. They are the engineering of discipline at scale.
Narrative Documents (Six-Pagers) force clarity before the meeting, not during it. There are no slides. No bullets to hide behind. No presenter controls the pace at which what gets absorbed is absorbed. The argument gets written in full sentences, in narrative form, and circulated before anyone sits down. The first fifteen minutes of the meeting are silent. Everyone reads. Then the discussion begins from a shared foundation of understanding, not a shared experience of watching someone present. It removes performance from the room and replaces it with thinking. That is not a small thing.
Bar Raiser brings an objective voice into every hiring decision. Not to block. To ensure. Someone trained to evaluate against Leadership Principles, to facilitate the debrief, to hold the standard steady when enthusiasm or urgency might soften it. The goal is not to hire someone who works for the manager. The goal is the right decision for the candidate and the company.
Working Backward starts where most processes end. Most teams build something, then ask whether customers want it. Working Backward asks the customer questions first. I write the press release before we build the solution. I draft the FAQ before we initiate the solution. I describe the customer's experience before deciding how to create it. It sounds counterintuitive. It is. That is exactly why it works. It forces the hard questions to the front of the process when changing direction is still cheap, rather than to the back when it isn’t.
One-Way versus Two-Way Doors is a decision-making framework so simple it almost sounds like common sense. It isn’t. Most organizations treat every decision with the same weight, the same process, the same committee, and the same delay. Amazon separates them. A two-way door decision is reversible. I can walk through it, look around, and walk back if I got it wrong. Move fast. Decide at the lowest level. Correct course if needed. A one-way door is different. Once I walk through, the door closes behind me. Those decisions deserve more time, more rigor, more elevation. The mechanism is not about moving fast. It is about knowing which kind of door I am standing in front of before I push it open.
None of these is intuitive. All of them are intentional.
What Amazon understood is that culture without mechanisms is just aspiration. I can say I am customer-obsessed. The Narrative Document makes me prove it before I walk into the room.
The rhythm of business is not accidental. It is engineered.
The Flywheel Runs Without You
Here is the test of a real mechanism. Remove yourself from it. Does it still run?
If the answer is no, I have not built a mechanism. I have built a dependency.
A great sales quarter is a win. A mechanism that produces great sales quarters every year is a business. A great coaching conversation is a gift. A weekly cadence that makes coaching conversations inevitable is a culture. A brilliant strategy memo is impressive. A planning cycle that generates brilliant strategy memos from my whole team is a leverage.
The goal is not to be the engine. The goal is to build the engine.
I learned this the hard way. I was the engine for a while. I carried the weight of keeping things moving through sheer personal effort, availability, and willingness to be the one who remembers. And it worked, until it didn’t. Until I traveled. Until a quarter got hard. Until three things broke at once, and no version of me could be in all three places.
Then I understood what a mechanism is for.
Build It Before You Need It
The best time to build a mechanism is before the problem it solves has fully arrived.
I have been tempted to wait. The quarter is moving. The deal is live. Twelve things matter more right now than building the infrastructure for how the team reviews deals, or how I surface blockers, or how I run territory planning. I tell myself I’ll get to it when things settle down.
Things do not settle down.
The leaders I admire most are the ones who built the mechanism in the slow moment before the fast one arrived. They set up the Monthly Business Review (MBR) intake before the quarter-end scramble. They designed the onboarding process before the new hire showed up. They defined the escalation path before the deal went sideways. They built the thing when they had time to build it well, so it could run when they had no time at all.
That is not preparation. That is architecture.
The Notebook
I flip back through it sometimes. The T&E report from July 2023. The FY2024 update. The Cross-Industry Cohort Strategy. The way-of-selling playbook. The Amazon facility tour checklist. The territory planning framework. My mindset shifts—forty months of mechanisms collected, tested, and refined.
None of it runs itself. I had to build each one.
That is the job. Not the calls. Not the slides. Not the Quarterly Business Reviews (QBRs). The job is building the things that make the calls, slides, and QBRs produce compounding outcomes. The job is turning good intentions into repeatable systems. The job is making the flywheel spin without me pushing it.
The notebook is full of evidence that I understood this, even when I was still figuring out how to say it.
Now I say it clearly.
Mechanisms are the work behind the work. Build them on purpose. Build them before you need them. Build them to run without you.
That is how the best leaders leave things better than they found them.