The MI pack that aged out
Reporting on an operation that no longer exists
MI packs age out the same way schedules do. The metrics that mattered when the pack was built captured an operation that has since changed — new channels, different customer base, evolved routing, shifted operating model. The pack still reports against the old structure, the operation has moved on, and the gap quietly widens until the pack is reporting on a version of the operation that doesn’t exist any more.
The failure is recognisable. The chat channel went from 15% to 35% of contacts and the pack still leads with voice metrics. The contact reasons restructured eighteen months ago and the breakdown still uses the old categories. The operation absorbed a different brand and the pack still reports the legacy operation. The audience reads the pack out of habit; nothing in it changes their behaviour because nothing in it describes the operation they’re actually running.
The warning signs
Five patterns that say a pack has aged out.
Metrics that no longer move with operational reality. The SL metric trends flat for two quarters even though the operation has changed measurably. Either the operation hasn’t changed (rare) or the metric isn’t capturing the change (common). The latter is a sign the metric’s definition is no longer aligned with the operation.
Audiences have stopped reading the pack. The signs are subtle: shorter glance time, the same question asked weeks after the pack already answered it, the meeting agenda gradually dropping the pack from the standing items. By the time the audience explicitly says “I don’t find the pack useful any more,” the drift has been visible for months.
The same “why is X happening” questions recur. Questions the pack should answer but doesn’t are diagnostic. The audience is asking because the pack isn’t telling them the thing they actually want to know — usually because the pack is structured around metrics that aren’t the right ones any more.
The pack has grown without anyone deliberately growing it. Slow accretion of metrics added in response to ad-hoc requests, with nothing ever removed. The pack hits 35 pages and the producer can’t remember why three-quarters of them exist.
The breakdowns don’t match how the operation is run. The pack reports by queue when the operation routes by skill. By channel when the operation handles work as customer journeys. By legacy brand when the operation has merged. Each of these mismatches makes the pack slightly less useful and the cumulative effect is large.
The quarterly review discipline
Same shape as the schedule quarterly review. Once every three months, the planning team and a representative of the audience walk through the pack with a structured agenda.
What in the operation has changed since the last review? New channels, new queues, new routing rules, new customer mix, organisational change. Each is a candidate for affecting how the pack should report.
Which metrics aren’t earning their place? The “so what?” audit from the previous piece, applied lightly. Anything that didn’t support a decision in the quarter is a candidate for cutting.
What does the audience still want to know that the pack doesn’t tell them? Direct ask. The audience often has accumulated frustrations they’ve never raised because they assumed the producer had reasons. Surfacing them produces concrete fixes.
Are the breakdowns aligned with how the operation is run? Re-test against the current routing, the current customer segmentation, the current operating model. Adjust where they’ve drifted.
The review takes about ninety minutes. The output is a small set of changes for the next quarter rather than a wholesale rebuild. Over four quarters, the pack stays current.
The conversation that prevents a pack redesign becoming destabilising
Audiences resist pack changes even when the existing pack isn’t working for them. The reasons are familiar — the format is familiar, the trend lines are continuous, the “we’ve always done it this way” inertia. The fix is the briefing conversation before the change lands.
“Next quarter’s pack will look different in three ways. Here’s what we’re changing and why. Here’s what stays the same. Here’s what the new sections will tell you that the old ones didn’t. Trial it for one quarter; we’ll review at the end.” The audience knows what to expect, the change has a stated rationale, and the trial framing reduces resistance. Most pack redesigns that fail do so because the audience wasn’t briefed.
The honest reason pack aging is under-managed
The producer of the pack has the strongest incentive to keep it the same. Changing the pack means more work in the short term and risks the audience preferring the old version. The quarterly review forces the change even when the producer would rather not.
This is exactly the same dynamic as the schedule that ages out, the FAQ that needs refreshing, and the glossary that needs updating. Recurring editorial work always falls behind one-off project work without a forcing function. The quarterly review is the forcing function.
Conclusion (and series conclusion)
The MI pack that ages out is the closing piece of this series because it’s the failure mode that compounds all the others. A pack designed for an audience that has changed; tracking downstream metrics whose upstream drivers have shifted; relying on lagging indicators that no longer capture the relevant outcomes; bloated with metrics that no longer produce decisions; built against an operation that no longer exists. Each individual failure is correctable. The aged-out pack has all of them at once.
The quarterly review is the discipline that prevents the compound failure. Like the schedule review, it’s short, structured, and unglamorous. Operations that run it find their MI stays current and useful; operations that don’t find themselves quietly rebuilding the pack every two years at high cost because the existing one has stopped working.
That’s the six failure modes. Design for the audience. Track upstream as well as downstream. Add leading indicators. Cut what nobody acts on. Review the pack quarterly so it doesn’t age out. And don’t hide truth behind composite metrics. None requires a new platform. All require sustained editorial discipline. The operations that hold the discipline have MI functions that drive decisions; the operations that don’t have MI functions that produce decks.
Series end. Read from the start: Where MI most often goes wrong.
Pair this with designing meaningful MI, composite metrics hide truth, and the schedule that ages out.