Operational Truth Rarely Lives in One Department

Most organizations don’t have a communication problem. They have a cartography problem. Every department has drawn the business from where they sit. Nobody has ever put the maps in the same room.

One Step Said “Prepare the Customer for Onboarding”

That sounded perfectly reasonable. It was right there in the documentation, sitting between two other steps that were equally tidy and equally vague. Prepare the customer for onboarding. Five words. A complete sentence. A checkbox nobody questioned.

So we started asking people what they actually did at that step.

The first person walked the customer through a checklist over a thirty-minute call. The second sent a PDF and followed up to see if there were any questions. The third had an informal conversation that covered roughly the same ground but in a different order depending on the client. The fourth assumed someone else had already done it. The fifth had developed their own version over two years and considered it an improvement on the original — which, to be fair, they had never actually seen.

One person had a jar of Jif. One had Skippy. One had chunky store brand. One was using a butter knife, one a spatula, and one was effectively using a sword.

Everyone believed they were following the documented process.

Technically, they were.

“We had documented that peanut butter should go on the bread. Nobody had documented what peanut butter was.”

The process wasn’t wrong. It was too vague to produce consistent outcomes. There’s a difference. Most organizations never find it — because nobody ever asks five people to explain the same step out loud, in the same room, at the same time.

This Is What Process Debt Actually Looks Like

A flowchart is not a system. A box with a label is not an instruction. It is a placeholder where an instruction should be — and placeholders compound quietly. One vague step becomes five. Five become a department. A department becomes a company that cannot explain, with any consistency, what it actually does.

The documentation existed. The process did not. Those are two different things, and confusing them is one of the most expensive mistakes a scaling organization can make.

The Follow-Up Problem That Was Actually Four Problems

A different organization. A cross-functional review. Everyone in the room agreed there was a follow-up problem — which was progress, because at least the problem had a name.

Leadership believed there was a single process for following up with prospects. Sales thought they were following it. Operations thought they owned part of it. Customer service had their own understanding of when they were supposed to get involved and when they weren’t.

As we started mapping the workflow, we discovered there wasn’t one process.

There were four spreadsheets.

Each one maintained by a different team. Each one cloned fresh every week to create that week’s version of the follow-up list. Anyone in the organization could edit them. No version control. No clear owner. No guarantee that two people looking at the data were looking at the same data.

The surprising part wasn’t that the spreadsheets existed. It was that everyone had adapted to them so completely that they no longer experienced this as unusual. They simply believed this was how the business worked. The parallel systems weren’t a workaround anymore. They were the operating model.

What a PBJ Session™ Actually Is

Only now does the definition matter — because you’ve already seen two examples of what happens without one.

A PBJ Session™ is a structured cross-functional conversation designed to do one thing: compare maps. Get the people responsible for different parts of the revenue journey in the same room. Ask each of them to describe the same process independently. Put the descriptions side by side. The gaps between them are the real diagnostic.

Why PBJ?

Every department is a jar on a shelf. Marketing. Sales. Operations. Customer Success. Leadership. Each one contains something real and useful. None of them, alone, make the sandwich. The session is what happens when you actually combine them — and discover that two of the jars thought they were the same thing, and weren’t.

The name is the point. Peanut butter and jelly are both perfectly functional on their own. Together, combined in the right way with some clarity about what goes on which slice, they produce something that works. Separately, sitting on a shelf, they produce a lot of confident people making very different sandwiches and wondering why nobody agrees on what lunch is supposed to taste like.

What Gets Revealed When You Compare the Maps

The session doesn’t create the gaps. It just makes them visible for the first time. And what becomes visible is almost always some version of the same thing: leadership is operating from assumptions that the organization stopped reflecting a long time ago.

Each of these is a system failure wearing a people-problem costume. Leadership diagnoses the symptom, addresses the symptom, and watches it return — because the underlying process was never examined. The session doesn’t assign blame. It just surfaces the gap between the map and the territory, which turns out to be the only starting point that actually produces change.

“Revenue doesn’t move through departments. It moves through handoffs. And nobody owns the handoff.”

What the Session Actually Produces

The output is not a meeting summary. It’s not a slide deck with a RAG status. It’s not a list of action items that will be reviewed once and never again.

The output is a more accurate map of how revenue actually moves through the business. Which sounds simple. Which is, in practice, one of the most valuable things a leadership team can possess — and something almost no leadership team actually has.

• Most companies don’t fail from bad strategy. They fail from accurate strategy applied to an inaccurate map.
• The map everyone agrees on is rarely the one that reflects reality.
• You cannot fix what you cannot see. You cannot see what you have never compared.

PBJ Sessions™ are how you find the Shadow Systems™. They’re how you start reducing Visibility Debt™. They’re the front end of a Revenue Health Diagnostic™ — because before you can score how a system is performing, you need to know what the system actually is. Not what the flowchart says. What it is.

The Moment the Spreadsheet Looks Back

Go back to the cross-functional review. Everyone is in the room. Leadership has explained the process. Sales is nodding. Operations is nodding. There’s a general sense that alignment is happening, that the meeting is going well, that perhaps the follow-up problem will finally be resolved.

And then someone from Customer Success quietly opens their laptop.

They’ve been maintaining a spreadsheet for eight months. They built it because they didn’t trust the official system — and they were right not to. It contains every prospect that fell through the cracks, every follow-up that didn’t happen, every customer who almost didn’t become one. Eight months of operational truth, living in a tab nobody knew existed.

The room goes quiet.

Not because anyone did something wrong. Because everyone, in that moment, realized they had been solving the problem individually instead of together — and that the spreadsheet had been telling the truth the whole time.

Marketing says sales never follows up.
Sales says marketing sends garbage leads.
Operations says nobody told them the customer existed.
Customer Success quietly opens a spreadsheet they’ve been maintaining for eight months.

Then everyone looks at the founder.
The founder looks at the spreadsheet.
The spreadsheet looks back.

That moment — the quiet, the recognition, the collective understanding that the real operating system had been running in the background the whole time — is what a PBJ Session™ is designed to produce. Not conflict. Not blame. Clarity. The kind that only comes from putting every version of the map in the same room and asking, honestly, which one reflects the territory.

Most organizations never do this. Not because it’s difficult. Because it requires sitting with the gap between what leadership believes and what the business actually does — and most leadership teams find that gap uncomfortable enough to avoid indefinitely.

The ones who don’t avoid it are the ones who scale.