Clean, Prune, Sunset: The Annual Review That Keeps Journey Work Alive

Journey management programs accumulate weight over time. Solutions that were relevant when the cycle began become obsolete as the market changes. Customer pains that were priorities eighteen months ago have either been addressed or are no longer the most urgent concerns. Big Solutions that are working well have become part of normal operations. Others have quietly stalled.

Without a deliberate annual review, the journey map and the program it anchors become cluttered with material that no longer reflects current priorities — and eventually, with the overhead of maintaining this accumulated weight, the program slows to the point where it stops driving the improvement that justified its existence.

Three Things the Annual Review Does

It cleans the journey map. After a full cycle of discovery, alignment, creation, implementation, and measurement, the map carries significant accumulated content. Not all of it remains relevant. Insights that have been addressed can be archived. Opportunities that were deprioritized can be reviewed for continued relevance. Confidence tags can be updated to reflect new evidence. The map should end the review lighter and more current than it entered it.

It prunes the solution portfolio. Some Big Solutions have delivered on their OKRs and are ready to transition from active development to steady-state operation. Others have been modified significantly in response to test results. Some have stalled without clear prospects of resuming. Each requires a different response — and the annual review is the moment to make those distinctions explicit.

"Review each Big Solution annually. Evaluate technical debt vs. continued value. Recommend redesign, merge, or sunset where needed. Remove outdated or redundant journey content."

It sunsets what is no longer serving the journey. This is the hardest part of the annual review and the most important. Sunsetting a Big Solution — deciding to stop investing in it, to archive the work done, to redirect the team's energy — is an organizational act that goes against most organizations' instinct to "protect" investments already made.

The sunk cost is real. But a solution that is not improving the experience and is not expected to improve with additional investment is a resource drag. The annual review creates the structural permission to make the sunset decision based on evidence rather than attachment.

The Cultural Dimension

Beyond its practical function, the annual review serves a cultural purpose: it signals that journey management is a living practice, not a program that runs indefinitely on inertia.

Organizations that conduct annual reviews with honesty — naming what worked, what did not, what has changed in the customer context that should reshape priorities — build a different relationship to continuous improvement than organizations that maintain programs because of the investment they represent.

The annual review is where journey management proves it can learn from itself. A program that adjusts based on evidence, that is willing to sunset solutions that are not working, and that incorporates new customer insights into its next cycle is a program that earns continued investment. A program that maintains its initial structure regardless of what the evidence shows will eventually lose relevance, even if it was well-designed originally.

What the Review Produces

The annual review should produce three outputs.

An updated journey map: cleaned of resolved or outdated content, updated with new insights from the current cycle's research, and re-scored based on the delta from the year's work.

A refreshed solution portfolio: Big Solutions reclassified as active, steady-state, on hold, or sunset, with rationale documented.

A program brief for the next cycle: the two or three priority areas that the current evidence suggests are most worth addressing in the upcoming twelve months, along with the resources and organizational changes needed to address them effectively.

This brief is the starting point for the next language kick-off meeting — and the cycle begins again, building on the accumulated knowledge rather than starting from scratch.