The Black Box Problem

Nobody outside your team can explain what product does. That's not their failure. It's yours.

Walk down the hall and ask finance what your product org is working on this quarter. Then ask sales. Then ask a senior engineer who isn't on your team. You'll get three different answers, and none of them will match the roadmap.

That gap has a name. Most leaders call it a communication problem and try to fix it with more updates. They're treating a missing story as a missing memo.

Early in my career I made that exact mistake, and a mentor called it out in front of a room.

I was presenting product work the way I thought you were supposed to. I listed what we'd shipped. The clever architecture. The hard technical call we got right. I was proud of the mechanism. The room glazed over — no questions, no decisions, no pull.

Afterward my mentor said the thing I still repeat: "Adam, nobody gives a damn about the cool thing you built. Your job is to make sure the people using it have an easier time and get a better outcome. That's it."

I'd been describing the engine. Nobody buys an engine. They buy where it takes them.

A black box isn't a secrecy problem.

Here's the trap. When the org can't see product, leaders assume product is hiding something or not communicating enough. So they add ceremony. More status decks. A weekly digest. A new Confluence space nobody reads.

None of it works, because the problem was never volume. You can flood the org with information and still be a black box.

A black box is an output problem. Information goes in — research, customer calls, tradeoffs, hard decisions — and what comes out the other side is a feature list. The reasoning stays trapped inside the team. The org sees what shipped. It never sees why this and not that.

When the why is invisible, people fill the vacuum with their own story. Sales decides product is slow. Engineering decides product is arbitrary. The CEO decides product needs adult supervision. You didn't tell your story, so everyone wrote one for you.

What's actually missing is narrative clarity.

Narrative clarity is the ability to explain your work upward, sideways, and downward in plain language — what matters, why now, and what you're not doing because of it.

It's not a deck. It's not a tagline. It's the through-line that connects a customer problem to a business outcome to the specific bet your team is making this quarter. When you have it, a stranger can repeat your strategy back to you after one conversation. When you don't, even your own team can't.

And narrative clarity isn't decoration on top of strategy. It is strategy made portable. A strategy that can't travel from your head into someone else's mouth isn't a strategy. It's a private opinion.

You can measure it on Monday.

My mentor Chris Butler gave me a test I've used ever since. He called it the Rule of Three.

Pick a decision your team is making right now. Then go ask three people it affects — outside product — to name the three most important things your team is doing and why. Don't coach them. Don't prep them. Just ask.

If the three answers rhyme, you have narrative clarity. If they scatter, you don't — and now you know exactly where the story breaks.

This gives you a signal most orgs never collect. Not a survey score. Not an engagement metric. The raw distance between what you think you've communicated and what actually landed. I've run this in SaaS teams, in fintech, in a government agency where the "customer" was a citizen who'd never log a complaint. Same result every time: leaders are stunned by the spread.

The spread is the black box, measured.

The fix isn't more reporting.

So don't go build a better dashboard. Don't hire a product marketer to "own the narrative." Don't add a standup.

A black box isn't a team that won't talk. It's a team whose reasoning never leaves the room.

Build the story instead. One paragraph: the problem that matters most right now, who it hurts, why this quarter, and what you're deliberately not doing to protect that focus. If you can't write it in plain language, you haven't decided — you've just been busy.

Then say it everywhere, like a broken record, until the Rule of Three comes back clean. That repetition feels excessive from the inside. From the outside, it's the first time the org has ever heard the actual logic.

Whether you're the VP who owns the strategy or the PM trying to defend a single roadmap item, the test is the same. Can someone who doesn't report to you repeat back why your work matters? If not, you don't have a visibility problem. You have a story you've never told.

This week's prompt

Run the Rule of Three before Friday. One decision, three people outside product, no prep.

Write down what they say. Compare it to what you believe your team is working on and why.

Where's the widest gap between your story and theirs? That gap is the most expensive thing on your roadmap, and nobody's tracking it. Reply and tell me what you found.