Clarity debt compounds faster than any other kind

In the 1960s, Brasilia was built from nothing in forty-one months. The city plan was elegant: a central axis for government, residential superblocks radiating outward, each neighbourhood self-contained with its own schools and shops. The architects had a clear thesis. A modern capital for a modern nation. But the city grew faster than the plan anticipated. Satellite cities sprang up around the original design, each with its own logic, its own infrastructure, its own relationship to the centre. By the 1980s, the greater Brasilia metropolitan area housed millions of people who had no connection to the original urban thesis. Visitors would ask, "What is the idea behind this city?" and the honest answer had become: it depends which part you are standing in.

The plan was still there, buried under decades of pragmatic expansion. Nobody could see it any more.

And: the world where products grow

Product organisations follow this pattern with a reliability that would be funny if it were not so expensive. A startup begins with a thesis so clean you could write it on a napkin. We solve this problem, for these people, in this way. Everyone on the team can recite it. Customers repeat it back to you in their own words. Sales closes deals by saying the thing, because the thing is obvious and true.

And then the company succeeds.

Features arrive. A pivot adds a second use case without retiring the first. An enterprise deal produces a custom module. A partnership introduces capabilities that serve a different audience. Each decision is rational. Each expansion is justified. But the explanation of what the product is, the sentence that used to fit on a napkin, gets longer and less convincing with every quarter. Nobody notices because nobody is tracking it.

I have started calling this clarity debt. Like technical debt, it accumulates through reasonable decisions made under time pressure. But unlike technical debt, nobody files a ticket for it. There is no dashboard that turns red when your positioning statement stops making sense.

Clarity debt compounds faster than technical debt. And unlike technical debt, nobody is tracking it.

But: the narrative falls behind

At Freshworks, I lived inside this problem. The product began as a customer support tool. You could explain it in one breath: a modern helpdesk for growing businesses. But the company expanded into CRM, then IT service management, then marketing automation. Each product made sense on its own terms. But when you stepped back and asked "What is Freshworks?", the answer depended entirely on which team you were talking to. Support would give you one answer. Sales another. Marketing a third. Product management a fourth. The CEO a fifth.

None of them were wrong. That was the painful part.

I call this the five-answers test. Ask five people across functions to explain what your product does in two sentences. If the answers do not sound like they describe the same company, you do not have a messaging problem. You have a clarity debt problem. The product has grown faster than the narrative that explains it, and nobody has done the integration work of weaving the new pieces into a story that coheres.

The mechanism of accumulation

The reason clarity debt compounds is that shipping is continuous and narrative integration is not. A team can ship a feature in two weeks. Rewriting the positioning to account for that feature and the three before it requires someone to sit down, look at everything the product has become, and write a new version of the story. That work is slow, politically difficult, and produces nothing that shows up in a sprint review.

So it gets deferred. One quarter, then another.

At Adobe, I saw what happens when the deferral runs long enough. The product I was working on had accumulated two years of features, partnerships, and audience shifts since the last time anyone had formally updated the positioning. The marketing site described a product from 2019. The sales team had developed its own pitch, which bore limited resemblance to what marketing was saying. The product team used internal shorthand that customers would not have recognised. Three versions of the truth, each maintained by a different function, none of them quite right.

When someone finally convened a working group to write a unified positioning document, it took eleven weeks. Not because the writing was difficult. Because the conversations were. People had genuinely different beliefs about what the product was, and those beliefs had diverged for so long that reconciling them felt less like alignment and more like negotiation.

Eleven weeks to agree on three paragraphs. That is the interest payment on two years of clarity debt.

Therefore: someone has to own this

The pattern is consistent across every company I have worked with or advised. The zero-to-one stage produces effortless clarity. The product is small enough to hold in one person's head. But somewhere between product-market fit and the fourth major expansion, the narrative breaks. New hires take longer to explain the product than to learn the codebase. Customers describe you by naming the specific feature they use rather than the problem you solve. Your own team starts hedging when someone at a dinner party asks what their company does.

Those are symptoms. But the root cause is structural: nobody owns the narrative the way someone owns the architecture.

At my first startup, we built a product that did three things well. But when a prospective investor asked my co-founder to explain it, the explanation ran past ten minutes and still had not landed. I sat in that room thinking: if the two people who built this cannot explain it in ninety seconds, the problem is not the investor's patience. We had shipped faster than we had thought. We had a product. We did not have a story.

That experience taught me something I still carry. Speed without narrative is just accumulation.

The companies that manage clarity debt well share one discipline. They treat the product narrative as a living artefact, not a marketing deliverable that gets written once and filed. They ask one question regularly: can someone who joined last month explain what we do and why it matters, in language a customer would recognise, within their first fortnight? If the answer is no, the debt is growing.

What it really costs

Most teams file clarity under "communications" and move on. But the real cost is not confused messaging. It is confused building. When the narrative is unclear, everything is potentially in scope. Features get approved because nobody has a shared framework for saying no. Roadmaps expand because the boundary between what the product is and what it is not has gone soft. The product becomes Brasilia's satellite cities: each part makes sense locally, yet the whole no longer tells a story.

The most expensive features I have ever seen built were features that should never have been considered, in a product that had lost the ability to say what it was.

I do not think most organisations will resolve their clarity debt until they stop treating it as a branding exercise and start treating it as a product decision. What are we, now, in language a stranger could repeat back? Not what we were. Not what we aspire to be. What are we, after all the growth and the pivots and the reasonable compromises?

The answer is always shorter than people expect. But arriving at it requires the kind of honest, slightly uncomfortable conversation that growing companies keep deferring, one more quarter, one more feature, one more pivot, until the debt is so large it feels like starting over.

It does not have to be that expensive. But it usually is.