An MoU isn't a finish line. It's a starting gun.

There's a moment most ops leaders know well.

Leadership announces the new initiative. The contracts get signed. Someone sends an all-hands email with an exciting subject line. And then nothing changes. Or not nearly as much as the announcement implied. Or not nearly as fast.

The announcement was real. The agreement was real. The gap between "we agreed to this" and "it's actually working" is also very real, and it's where most of your process debt gets made.

This week on Process Debt, Chris and Toby used an unlikely case study to dig into that gap: the recent US-Iran memorandum of understanding. Strip away the geopolitics, and it's a remarkably clean illustration of how agreements in principle work — and how easily they get confused with outcomes.

An MOU Is Not a Done Deal

A memorandum of understanding is, by definition, an agreement to enter a process — not the completion of one. You've agreed on a direction. You've committed to negotiate. That's it.

Chris used a blunt analogy to make the point: an MOU is like agreeing to dissolve your marriage. You've both decided it's over. What you haven't done is figure out who moves out, who gets the joint accounts, what happens with the shared calendar, the shared lease, the shared history. If you've been married for any length of time, almost everything in your life is intertwined with that other person. The MOU just means you've agreed to start unraveling it.

Organizations do this constantly. A new platform gets purchased. A partnership gets announced. A restructure gets greenlit. Leadership calls it done. The people who have to actually implement it know better — they're the ones who suddenly have to figure out the Aunt Gladys dishes equivalent.

What History Actually Predicts

One of the most useful moves in this episode is a simple one: go look at what happened last time.

Chris pointed out that Obama's Iran nuclear agreement — structurally similar to the current MOU — took 18 months to go from first agreement to a signed 150-page document. That's not speculation. That's a data point. And if you apply basic Bayesian reasoning — updating your probability estimates based on what you already know — 18 months is probably your floor, not your ceiling.

This kind of historical baseline is almost always available in organizations too, and almost never gets consulted. How long did the last ERP rollout take? How long did it take for the platform before this one to hit actual adoption? If your track record says 14 months and your project plan says 6, you don't have a realistic project plan. You have an optimistic story you're telling to get the thing approved.

Ignoring track records leads to bad predictions. That sentence sounds obvious. It rarely affects the slide deck.

The PUMP Framework: A Pre-Mortem for Big Decisions

Chris and Toby walked through their PUMP framework as a way of pressure-testing the MOU before going in:

• Power — Who actually has it, and does this agreement change that?

• Unintended consequences — What gets worse as a direct result of this decision?

• Money — Where does it flow, and does that match the stated intent?

• Process — What has to actually happen for this to work?

The value of PUMP isn't that it gives you answers. It's that it forces you to slow down before you commit and actually think through each dimension. It's a pre-mortem disguised as a framework.

In the episode, Toby flagged the Hormuz Strait as an unintended consequence that was entirely predictable — it shouldn't have been unintended. In organizations, the equivalent is the classic "we implemented the new CRM and now no one knows where to find the old data" situation. It was foreseeable. No one ran the PUMP check.

"To What End?"

Toby mentioned a Substack piece from Angela Goodwin, a former finance leader, that stopped him cold: if you don't know what success looks like before you start, maybe you're not ready to start.

This is deceptively simple and almost universally ignored. Organizations kick off initiatives — tool rollouts, process redesigns, org restructures — without a clear answer to the "to what end?" question. What are we trying to be able to do that we can't do now? How will we know if it worked?

When you can't answer that question, you don't get a failed project. You get an endless one. The implementation drags, the scope creeps, the stakeholders lose interest, and eventually the thing just becomes the new status quo — whether it works or not.

The Pollyanna Problem

Here's where it gets honest in a way most process content doesn't: you often have to oversell timelines and outcomes to get anything approved.

Chris acknowledged this directly. If you stand up in a planning meeting and say "realistically, based on our track record, this will take 18 months and we're not sure what success looks like yet" — it doesn't get funded. The 6-month version gets funded. And then you spend 12 months explaining why it's taking longer than expected.

This isn't just a leadership failure. It's structural. Organizations don't reward honest forecasts. They reward confident ones. So process debt gets baked in at the proposal stage, long before anyone opens the software.

The move isn't to become a pessimist. It's to build the honest timeline alongside the sellable one, share it with the people who'll actually do the work, and stop being surprised when the sellable version turns out to be wrong.

Most of Us Are Receivers

One thread that ran quietly through the whole episode: most of the people who have to live inside a decision aren't the people who made it.

The MOU gets signed by heads of state. The ops leaders in both countries figure out what it actually means for their day-to-day. The acquisition gets announced by the C-suite. The project manager inherits the integration. The platform gets bought by the VP. The team lead gets handed the rollout.

Being a receiver of decisions isn't a failure of status. It's just the reality of how most organizations work. But it does change how you think about process design — because a process designed entirely by people who won't have to use it tends to fail in very predictable ways.

The Short Version

Signing the thing is not finishing the thing. History is your best baseline for how long the real work takes. Pre-mortems aren't pessimism — they're professionalism. And if you don't know what success looks like, the agreement is the easy part.

The hard part comes next.

Chris Terrell and Toby Lucich host Process Debt, a podcast about the hidden cost of deferred process decisions — and how to start fixing them.