October 18, 2026

A method that can't tell you when its output has expired is half a method. The positioning line you locked last year was right on the day you locked it. Nothing in it will tell you the day that stops.
I work with B2B founders at the 5 to 100 person stage who still run their own sales. Settling a position is hard at that size. You picked one buyer over another and gave up claims you liked. That took discipline, and the line was probably right.
Locking it was correct, because a position you reopen every Monday is no position at all.
Then the market moves. A competitor changes what they sell, or your product gains something it couldn't do last year. Buyers begin comparing you with a company you hadn't heard of.
The line on the page still reads well. Reading well and being true are different tests, and only the first is visible from inside the business.
If your line stopped being true three months ago, what in your business would have told you?
April Dunford made this argument in her newsletter on 2026-09-03. At a roundtable, a founder told her any positioning would be stale within a fortnight. Her answer was to re-run the steps you used the first time. Check who buyers now compare you with and what you can do that they can't. Then ask whether the value you claim has moved.
Often it hasn't. She finds new capability tends to reinforce a claim you already make. The line holds and the explanation beneath it grows. Without a process, she writes, "your positioning is left flapping in the wind" each time something ships.
She was writing about AI products, where the ground moves fastest. The logic holds for any shock, whether a competitor's new offer or a buyer asking a different question.
I'd take it further than positioning. The value of any method is knowing when its output has stopped being true. The document is a by-product. The same holds for a sales playbook or a set of pipeline stages. Something installed without a trigger for revisiting it is right once, then wrong with nobody told.
A scheduled review helps, and it beats having none. Its weakness is the calendar. Say the market moves in week two. A quarterly review leaves you wrong for most of the quarter. A trigger tied to an event catches the change when it happens.
Take the positioning line you settled on and write the date beside it. Then write down what would have to change in the market for you to rewrite it. Two events is enough: a named competitor moving into your segment, or a lost deal where the buyer compared you with something new.
If you can't say what would have to change, the line is a slogan.
Coming up blank is normal. Nobody asked you for the trigger when you did the work, because the exercise ended at the document.
Picture it with the trigger in place. A competitor announces a cheaper tier on a Tuesday. By Thursday you have run the same checks and found the value you claim hasn't moved. The line stays and one sentence beneath it changes. Nobody spends a month debating a rebrand.
That is what I mean by a revenue operating system. The decisions are written down, and so are the conditions for reopening them.
This article gets the same treatment. Review-By: 2027-01-18. I'd rewrite it sooner if a founder showed me a locked position that held for years with no trigger and no cost. Or if Dunford revised the argument I've leaned on.
This week's posts take two pieces further: the date on the line, and what would make you rewrite it.
Source: Originally published on LinkedIn, 18 October 2026.