A beta-tag standoff that turned out to be about institutional memory, not policy.
We had a feature going out that wasn’t ready to be judged as finished. Early feedback was rough. One round of it was blunt enough that there was no soft way to read it. The best move seemed obvious to me: ship it with a signal that it’s still in progress, a beta tag, so people would weigh it as a work in progress instead of a finished promise we were charging full freight for.
Engineering folks pushed back, and not unreasonably. We don’t have a beta framework. What are the exit criteria? How long does something stay a beta? Can we even charge for it? Those are real questions, and a team that asks them is doing its job. But underneath the questions was an assumption I recognized, because I’ve seen it in every company that’s grown fast: the assumption that we’d never done this before. That a beta release would be a brand new thing we’d have to invent from scratch, under deadline, with no precedent to lean on.
We had done it before. The company had shipped under different release labels at earlier points, with different rules for different situations. The reason it felt like uncharted territory is that most of the marketing team is newer. They inherited the product as it is today. They didn’t inherit the history of how it got here, and nobody had handed it to them. So “we don’t do that here” wasn’t a policy. It was an amnesia. The blocker wasn’t capability or even risk, it was lost institutional memory, and the fix for lost memory isn’t a new framework, it’s somebody in the room who remembers and can say “we’ve done versions of this, here’s the precedent, let’s get the exception approved.”
There was one genuine snag worth separating out, because it wasn’t amnesia, it was a real fit problem. The usual shape of a limited release assumes a short window, a few weeks, then you graduate or you pull it. This feature has a long usage cycle. People don’t form a verdict on it in a few weeks, they form it over a much longer arc. So the standard mold didn’t fit, and that’s a case where the best answer is that you have to make a new shape rather than force the work into an old one. Knowing the difference between “we forgot we could” and “this honestly doesn’t fit what we’ve done” is most of the decision.
The teachable part
When a team tells you “we don’t do that here,” figure out fast whether you’re hearing a rule or an amnesia. Newer teams inherit the present but not the past, and a surprising amount of “we can’t” turns out to be “no one here remembers that we did.” Part of the job, especially as the org grows and the people who carry the history thin out, is to be the institutional memory that lets the company say yes to something it’s actually done before. And when the precedent honestly doesn’t fit, say that too, and go make the new shape on purpose.