> ## Content Index > Fetch the complete content index at: https://www.theadamthomas.com/llms.txt > Use this file to discover other available public pages before exploring further. # The Re-Forecast Meeting - URL: https://www.theadamthomas.com/the-re-forecast-meeting/ - Published: 2026-11-10T18:00:11.000Z - Updated: 2026-11-10T18:00:11.000Z - Author: Adam Thomas - Tags: Newsletter A product leader told me recently that his organization had a quality process, and I asked him the only question worth asking about a process like that: has it ever changed a decision? He thought about it for a while, which was the answer. If your mechanism has never once produced a different outcome than you'd have reached without it, you don't have a mechanism. You have a meeting with a good name, and the fact that it appears on a calendar every fortnight is doing a remarkable amount of work in disguising that. I know this one from the wrong end. Early in my career a mentor stopped me in front of a full room and told me that nobody gives a damn about the cool thing I'd learned from wherever I'd learned it from. I was mortified, and he was completely right. I'd brought a framework to a problem that needed a decision, and the framework had never once changed what we did — it just made me feel like a serious person while I presented it. That is what most processes are, and I built a few of them myself before I stopped. The last three issues were about naming a shifted reality: say the delta, name the owner, announce the drop, hand over the right to re-plan, and sort every promise into what stands, what moves and what dies. All of that is a speech, though — a good one, delivered once, in a hard week. The question this week is what makes it an operating system instead. ## Why the speech doesn't hold Here's what happens to the leader who does everything in the last three issues correctly. The all-hands lands well, and people are visibly relieved that somebody has finally said the number out loud. Two engineers tell you privately it was the most honest thing they've heard from leadership in a year, and you go home feeling like you've done the job. Then eleven weeks pass and reality shifts again, because reality does that. Another req gets frozen, or an AI tool absorbs a workflow, or your best release engineer takes a job at a company that pays in stock you can actually sell. And this time there's no all-hands, because the last one was a crisis response and this doesn't feel like a crisis yet. So it gets absorbed all over again, and the plan on the wall drifts away from the company for the second time, only now your team has learned something worse than before: that honesty about constraints is available in emergencies and unavailable the rest of the time. A speech is what you do when reality has already broken. A cadence is what stops it breaking unnoticed. Strategy has the same disease, and I say this as somebody who gets most of his strategy thinking from Richard Rumelt. A strategy document that gets carved in November, placed carefully in Google Drive, and walked past for eleven months isn't a strategy. It's a statue — dead, and nobody cares. The living version is a plant you water every sprint, and the watering is the part everyone skips because it's unglamorous and never finished. ## What a re-forecast actually needs There are three components to it, and I'd argue fairly hard that you can't run this thing on two of them. A trigger that isn't a feeling. Something has to fire the meeting other than somebody's anxiety, because anxiety is unevenly distributed and tends to peak too late. At one company we had a rule I still recommend: if the AWS bill was projected to jump more than 10% off a release, everything stopped and we had a conversation before shipping. Not a review, not a note in the retro — a hard stop. The number did the deciding, so nobody had to be brave enough to call it. What's your equivalent? If you can't name one, your trigger is currently vibes, and vibes fire late. A table, not a discussion. The re-forecast produces three columns, filled in: what capability changed, who owns the gap, what comes off the plan. If it produces prose instead, it produced nothing, because prose can't be compared to last quarter's prose and nobody will try. A table can be laid next to last quarter's table. A conversation can only be remembered, badly, by whoever talked the most. A record a stranger could read. Not minutes. The decision, the number behind it, and who owned it, written where somebody who wasn't in the room can find it next year and see exactly what you were looking at. This is the component that turns a re-forecast from a coping ritual into an asset, because the second time you run it you can see what the first one got wrong. ## The thing this fixes that you can count Here's the number that makes this worth an hour a month, and you can pull it this afternoon. Count the roadmap items that changed last quarter. Now count how many of those changes someone actually decided. The rest just happened to you. A re-forecast meeting is where the things that happen to you turn back into things you decide. ## Make it visible while it happens One design note, and it's the difference between a re-forecast that works and one that becomes theater within two quarters. Run it in the open. I think of this as Waffle House visibility — the kitchen is right there, you can watch your food being made, and there's nothing to backchannel about because there's no back. When the tradeoffs get made in a closed room and announced afterward, the announcement is the only artifact, and announcements are exactly what your team has learned to discount. When they're made in front of the people affected, the reasoning becomes the artifact, and reasoning is portable. Does that make the meeting slower and more uncomfortable? Yes. That's the cost, and it's cheap against the alternative, which is a team that quietly stops telling you what's breaking. This is most of what we build in my workshops, incidentally — not the slides, the actual cadence, in the room, with the leaders who'll have to run it on the Monday after. ## Your version, this week Write down the trigger. One number, with a threshold, that fires a re-forecast without anyone needing courage. Then look at the last process you introduced and ask the question I opened with. Has it ever changed a decision? If it hasn't, you've got a choice between fixing it and killing it, and killing it is a perfectly respectable answer — it's the one thing that reliably gives capacity back.