Why Planning Season Exposes How Much Context Your Team Already Lost
Quarterly and annual planning does not ask a team to learn anything new. It asks them to remember what was already said in customer calls, postmortems, and strategy meetings months earlier, and by then most of that reasoning has quietly decayed. A look at why planning season keeps feeling harder than it should, and what to pull into the room instead of starting from memory.
Planning season is not a research phase
Every planning cycle opens with some version of the same question: what did we learn since the last one. Most of the time the company already knows the answer, because it was said out loud already, in a customer call, a postmortem, a pricing debate, or a hallway conversation sometime in the last three months. The information exists. The problem is finding it again.
Teams treat planning season like a research phase anyway. Someone spends the week before the offsite pinging people in Slack asking what we decided about the enterprise tier, or why the last campaign underperformed, or what the customer actually said on that call in May. That is not research. It is retrieval, done badly, under a deadline, from whoever happens to still remember.
Why the memory is already gone by the time planning starts
Hermann Ebbinghaus ran the original experiments on this in the 1880s and the pattern he found still holds: people tend to lose half of what they learned within days or weeks unless they consciously review it. The rate is not about effort or intelligence. Ebbinghaus found the basic forgetting rate differs little between individuals, and that what actually slows the decline is active review, spaced out over time, not raw memory skill.
A quarter is roughly ninety days. Whatever specific reasoning sat behind a March pricing decision has had ninety days of unreviewed time to decay before a June planning session asks someone to reconstruct it from memory. Nobody forgot because they were careless. They forgot because that is what happens to information nobody deliberately revisited.
A premortem is only as sharp as what the team can actually recall
Gary Klein's premortem technique, described in Harvard Business Review in 2007, asks a team to imagine a plan has already failed and work backward from there to explain why. Klein's research found that this kind of prospective hindsight raises a team's ability to correctly identify reasons for future failure by roughly thirty percent compared to a standard forward-looking risk discussion, because imagining a failure that already happened feels like explaining, not criticizing, and people say things out loud they would otherwise hold back.
Most premortems still run on imagination alone, because imagination is what is left when the actual record of what happened last cycle is scattered across people's memory instead of somewhere searchable. The strongest failure modes to raise in a premortem are rarely hypothetical. They are the ones that already happened once in a smaller form: the customer commitment that slipped, the launch that got pulled a week before ship, the decision that got quietly reversed and never explained. A team can only put those on the table if the record of them survived past the meeting where they came up.
What to pull into the room instead of starting from memory
Before a planning cycle starts, the useful question is not what does everyone remember, it is what did the last ninety days of meetings actually contain. Pulling the specific commitments, reversed decisions, and near misses from that period gives a planning session something to argue with instead of a blank page and whoever speaks first.
Driffle keeps a searchable record of meetings as they happen, without a bot joining the call or a recording notice going out, so the context is still there when planning season starts. Asking what did we actually decide about the enterprise tier in March returns the March conversation instead of whoever's memory of it is loudest in the room, and that same record is what turns a premortem from a guessing exercise into one grounded in what already went wrong once before.
Sources
- Ebbinghaus forgetting curve - Wikipedia
- Performing a Project Premortem - Harvard Business Review (Gary Klein, September 2007)
FAQ
Does this apply to quarterly planning, annual planning, or both?
Both. The forgetting curve does not care what the planning cycle is called. It cares how much unreviewed time has passed since the original meeting, and a year gives the decay far longer to work than a quarter does.
How is this different from a retrospective?
A retrospective usually looks at how the immediate last cycle executed against its plan. This is about the raw material a retrospective or a planning session needs before that conversation can happen at all: the specific reasoning behind decisions, not just the outcomes a task tracker already recorded.
Doesn't a project management tool already capture this?
A task tracker records what got assigned and whether it shipped. It rarely records why a decision was made, what was said on the call where it was debated, or the near miss that never became a ticket, and that reasoning is exactly what decays first.