The win-theme retirement ceremony
A quarterly ritual: which win themes we stop using, and why. This quarter, three retired. One we kept against better judgment.
Every quarter I sit down with the proposal team and we retire win themes. We don’t just reassess them. We retire them — with a written statement about why, what replaced them if anything, and which pursuits they were used on one last time.
This is the ritual. And this quarter’s retirees.
Why retirement is a ritual, not a review
Reviews keep win themes around. “Is this still useful?” almost always gets a yes, because the theme worked somewhere, for someone, last year. A review is biased toward preservation.
Retirement is biased the other way. The default is retire; the theme has to earn staying. You articulate what’s wrong with it. You name the pursuits it won and the pursuits it lost. You look at the freshness of its evidence blocks. You ask: if we were writing it for the first time today, would we?
PropLibrary’s piece on win themes makes the case that themes go generic through reuse — the more a theme is used, the more it mutates into a reusable paragraph, and the less it functions as a theme. Retirement is the counter-force.
This quarter’s retirees
“Purpose-built for regulated industries.” Retired after 18 months of service. Won us work in three pursuits early on; has been drifting into every proposal for the last six months as a default. When a theme appears on 90% of pursuits, it isn’t a theme anymore — it’s a tagline. And when we applied the swap test, any of our competitors could have used the same sentence. Retired with a replacement pair: “compliance-mapped by sector” (for proposals responding to industry-specific regulatory RFPs) and “audit-ready by default” (for DDQ-heavy pursuits). The replacements are narrower; that’s the point.
“Grounded AI that cites its sources.” This one hurt to retire, because it’s both true and central to our product. What made it fail as a win theme: prospects had started nodding at it without asking follow-up questions. A theme that doesn’t provoke a follow-up question isn’t landing — it’s sliding past. We’re not abandoning the positioning; we moved it out of the win-theme roster and into product marketing. Win themes for the product will now focus on specific mechanisms (“per-claim verification”) rather than the category claim.
“The proposal platform your reviewers can trust.” Retired because the word “reviewers” pointed at the wrong evaluation level. Our actual champion is the proposal manager, not the evaluator on the buyer side — and the theme was being read by champions who correctly identified that the evaluator wasn’t the person making a purchasing decision. We got the persona wrong in the theme. No replacement yet; the team is drafting one that addresses proposal managers directly.
One we kept against better judgment
“Every RFP you win makes the next one easier.” This is our product thesis. It has also been a win theme in our customer-facing proposals since month one. The case for retirement: it’s been on every deck, every pitch, every piece of marketing. It’s become the thing we say, which means it’s stopped being the thing that distinguishes us.
The case for keeping: when I apply the swap test to it, it doesn’t swap. No competitor makes this claim because no competitor ships the post-mortem-to-KB writeback that makes it defensible. The theme is still differentiating even if it’s familiar.
We kept it. I noted in the retirement review that we should revisit at end of Q3 — if by then the phrase has become generic industry language, the theme goes.
What retirement does that review doesn’t
Three things.
It creates space for new themes. A theme roster that accumulates indefinitely is a theme roster that writers stop using. New themes get swapped in because old ones went out, not because the team decided to layer in more.
It produces a documented reason. Every retired theme has a paragraph in the archive about why it was retired. Next year’s team can read why their predecessors made the call. Proposal-craft institutional memory erodes fast; this is one mechanism that resists it.
It forces revisiting the evidence. Every theme is backed by specific evidence blocks, customer stories, past-performance references. When a theme retires, those evidence blocks either get reattached to a replacement theme or get archived themselves. The KB stays honest.
When to do it
Quarterly works for us. Any more frequent and there aren’t enough data points since the last review. Any less frequent and the theme roster gets stale. The win themes field guide has the full framework; the retirement ceremony is one beat in it.
The ritual takes about 90 minutes, with 4–6 people. It’s uncomfortable. That’s the feature, not the bug.