Programme 10 · Traction

Track rightsizing progress

A rightsizing plan is a set of predictions. This programme tracks them against reality: capacity actually freed, work actually redistributed, and the early signals that a team is quietly drowning.

A team meeting reviewing progress around a table10Traction

Continuous · live from your systems

The point of view

A rightsizing plan is a set of predictions. Most are never checked.

Every rightsizing plan makes claims about the future: this capacity will free up, that work will redistribute cleanly, coverage will hold, these people will transition by this date. Then the plan is approved, the organisation exhales, and the predictions go unexamined until the quarterly review, by which point every variance is three months old and expensive to correct. The plan was a forecast; nobody stayed to watch the weather.

The most dangerous assumption in any such plan is that work disappears with the role. It usually does not. It redistributes, silently, onto the nearest capable team, and for a quarter or two that team absorbs it invisibly through overtime and goodwill. The plan looks on track precisely because people are quietly paying its costs. By the time the strain surfaces in resignations, you are losing exactly the people the plan meant to keep.

Teams do not announce they are drowning. The data does, if you are watching it.

The humane and the commercial answer turn out to be the same one: watch the leading indicators. Overtime creep, ticket backlogs, cycle-time slips on affected processes, all of it visible in systems you already run, all of it surfacing weeks before it shows up in exit interviews. A steering meeting armed with that data makes corrections while they are still cheap nudges: resequence a milestone, backfill a transition, slow one workstream. A steering meeting armed with anecdotes argues about whose impression is right.

This programme keeps the plan honest: every milestone tracked in the graph as it lands, every freed hour traced to where it went, and the strain signals watched so the plan gets corrected by evidence rather than by attrition.

An overhead view of a working meeting in progress
The work

What this programme does.

Each milestone in the plan is tracked in the graph as it lands: roles transitioned, hours redeployed, coverage held. Variance is visible immediately rather than at the quarterly review.

Leading indicators watch the human side: overtime creep, ticket backlogs, cycle-time slips on affected processes, so a team under strain surfaces in the data before it surfaces in resignations.

How it runs

From kickoff to landed.

Continuous · live from your systems

Week 0 · Connect

The plan meets the signals

The rightsizing plan goes in, ideally built on this platform, and connects to the operational signals: ticketing, time and workflow data, with a monthly steering rhythm agreed.

Weekly · Track

Milestones against reality

Roles transitioned, hours redeployed, coverage held: plan versus actual per team, visible immediately rather than at the quarterly review.

Continuous · Watch

Strain surfaces early

Leading indicators watch the human side: overtime creep, backlog growth, cycle-time slips on affected processes, so a team under strain surfaces in data before it surfaces in resignations.

Monthly · Steer

Corrections while they are cheap

The steering meeting works from the capacity ledger and variance, not anecdotes: resequence, backfill, or slow a workstream, with the evidence for each call on the table.

Deliverables

What you get.

Living documents, not slideware: every deliverable stays connected to the graph and updates as the analysis moves.

Milestone tracker

Plan versus actual per team, per quarter.

Capacity ledger

Hours freed, redeployed and banked, traceable to tasks.

Strain signals

Early warning where the plan is hurting delivery or people.

What you need.

  • The rightsizing plan, ideally built on this platform
  • Access to the operational signals: ticketing, time or workflow data
  • A monthly steering rhythm to act on the variance
FAQ

The questions teams ask about this programme.

What signals do you actually watch?+

Two layers. Plan signals: milestones landing, roles transitioned, hours redeployed and banked. And strain signals from systems you already run: overtime patterns, ticket backlogs and cycle times on affected processes. Together they show whether the plan is working and what it is costing the teams carrying it.

Our plan was not built on your platform. Can you still track it?+

Yes. The plan's milestones and capacity assumptions are loaded into the graph and tracked from there. Plans built with the Rightsizing Plan programme start faster because the model already exists, but any structured plan can be tracked.

How do you spot a team that is struggling before it becomes attrition?+

Struggling teams show a consistent signature weeks before anyone resigns: overtime creeps up, backlogs grow, cycle times slip on the processes they own. Because the tracking watches those indicators per affected team, strain surfaces as a flagged variance, not as a surprise exit interview.

Who sees this data?+

The steering group you define. The tracking is about team-level capacity and process health, not individual performance, and the signal scope is agreed before anything connects. Its purpose is to protect the plan and the people carrying it.

What if the tracking shows the plan itself was wrong?+

Then it has done its job while the correction is still affordable. Variance is evidence, and the monthly steering rhythm exists precisely to resequence, rescope or reverse parts of the plan based on what reality reports back.

Programme 10

Start with this programme, on one department.

Course-correct the plan while corrections are still cheap, with evidence instead of anecdotes.

We use cookies to improve your experience and analyze traffic.