Transformation and change
How much change can our teams take on?
You spot overload before it reaches the people involved. Every initiative states whom it affects, how hard and for how long, and the sum per group and month shows the load.
Today
Every initiative plans its rollout, the sum stays unplanned
The same people get everything at once
Three projects reach the same department in the same quarter. Each one is well planned, and together they cannot be done.
Whether it lands is known at the end
The rollout counts as done once the training has happened. Whether the new way of working lands shows in the figures only months later.
The resolution and the effect are not connected
What was resolved is in the minutes. What became of it among the staff is usually first asked in the committee, and then the answer is missing.
What changes
Change gets receivers, a measure and a pulse
Change arrives at a pace people can carry. The heatmap shows collisions per audience and month, and an anonymous pulse shows whether it lands.
People and change
What you have afterwards
What transformation holds afterwards
- Collisions before they happen, in the change-load heatmap per audience and month.
- A signal of whether the change lands, from an anonymous pulse per group.
- Rollouts that start only when the prerequisites are in place, with a readiness check per initiative.
- Evidenced impact from decision to outcome, with the history of every approved change.
Common objections
- Our works council will ask whether staff are being measured here.
- No. The load is declared per audience, not measured per person. The pulse is anonymous, and groups below the anonymity threshold are not evaluated. Evaluations run at group and initiative level.
- Who is supposed to estimate the intensity per audience?
- The initiative that causes the change, on a four-level scale. That is an estimate, and it is visible as one. The pulse lets you check it as the rollout proceeds.
- What if two initiatives need the same group?
- Then the heatmap shows the month over capacity, and the decision is to defer, merge or end. Each of those decisions is recorded in the decision log.
See it first
Recording decisions on change load
The guide shows how to record deferring, merging or ending so that the reasons still hold a year later.