submove / behavioral simulation / predict reaction to a reorg
How to predict employee reaction to a reorg or manager change
Last updated: June 2026
To predict how employees will react to a reorganization or a new manager, you model the change before you make it: resolve the team into anonymous individual profiles inside their real reporting network, then play the specific change forward to estimate the likely shifts in stress, morale, trust, and performance, and where in the team they concentrate.
Most organizations learn the human cost of a reorg afterward, from attrition, missed delivery, and the quiet things people stop saying. A behavioral simulation moves that read forward in time, to while the decision is still on the table. This is the people-change version of the broader category explained in what is a behavioral simulation engine.
Why reorgs and manager changes are hard to predict
A reorg does not land on a list of names. It lands on a network. When reporting lines move, the strain shows up not only on the people who moved but on everyone who depended on them, and a new manager resets trust that took years to build, so delivery can dip even when the change is objectively reasonable.
That is why intuition and headcount math under-predict reaction. They count who is affected; they do not trace how the effect spreads. The people who carry the most strain are often one step removed from the change itself, and they are exactly the ones a flat plan misses.
How to predict reaction before you commit
The method is to rehearse the specific change against a model of your actual team, the same way a pilot rehearses a storm in a simulator before flying through it. With submove that runs as a focused engagement in four steps.
- Frame the change precisely. Name exactly what moves, which teams merge, who the new manager is over, what the new reporting lines are, so the simulation aims at a real decision.
- Build the model. Resolve the affected people into anonymous, governed profiles inside your real reporting and collaboration network. No PII enters the model; identifiers are masked and role-coded.
- Run the change forward. Play the reorg or manager change through the network many times, producing a distribution of likely trajectories for stress, morale, trust, and performance.
- Read the cockpit together. Interpret where strain concentrates and how it ripples, then translate that into how you might sequence, soften, or rethink the change.
A worked example: a new manager over an existing team
Suppose you are moving a high-performing team under a new manager as part of a restructure. On paper it is clean: same people, same work, one new leader. The question that decides whether it works is not on paper.
Played forward, a manager change typically shows a trust reset in the first weeks, not a collapse, but a dip that has to be rebuilt deliberately. The simulation tends to surface that the strain lands hardest not on the most vocal people but on the ones who quietly held the most dependencies under the old manager, because their informal authority does not transfer automatically. It also shows where a second, simultaneous change, say a tooling or process shift, would compound the dip rather than add to it linearly.
None of that names an individual or predicts a single person's future. It is a structured read of where the team as a whole is likely to strain, early enough to do something about it, stagger the changes, brief the new manager on where dependencies actually sit, and protect the people most likely to be quietly overloaded.
Seeing the likely trajectory while a decision is still reversible changes what you can do about it.
What you can do with the read
- Sequence the rollout. Order the moves so strain does not all land in the same week or on the same people.
- Soften the hard parts. Add support exactly where the model shows the first cracks tend to appear, instead of spreading effort evenly.
- Brief the new manager. Show where the real dependencies sit, so trust is rebuilt where it actually matters.
- Rethink the change. Sometimes the most valuable outcome is deciding to do it differently, or not yet.
Simulation or a survey?
A survey measures how the team feels now and cannot tell you how they will respond to a change you have not made, and asking can itself signal the change too early. A simulation rehearses the response privately, before anything is announced. They answer different questions and are strongest together.
For the full comparison, see behavioral simulation vs surveys vs change-management tools.
Frequently asked questions
Can you really predict how employees will react to a reorg?
You can estimate the likely reaction, not guarantee it. A behavioral simulation plays the specific reorg forward across a model of your real team and reports likely shifts in stress, morale, trust, and performance, and where they concentrate. It is calibrated, not validated, so it describes likelihoods rather than certainties.
How do you predict reaction to a new manager?
Model the team as anonymous individual profiles inside their real reporting network, then introduce the manager change and play it forward. Trust with a new manager typically resets and rebuilds gradually, and the simulation shows where that reset is likely to strain delivery and who absorbs it.
Should you run it before or after the announcement?
Before. The value is that the change is still reversible. Running it before the announcement lets you sequence the rollout, soften the parts likely to land hardest, or rethink the change, rather than reading the damage afterward.
Does this identify which individuals will resist?
No. submove never names or scores a real individual. It uses anonymous, governed profiles to show where strain is likely to concentrate across the team, not to single out a person.
How is this different from just asking the team in a survey?
A survey tells you how the team feels now. It cannot tell you how they will respond to a change you have not made yet, and asking can itself signal the change prematurely. A behavioral simulation rehearses the response in private, before anything is announced.
Rehearse your reorg before you commit
If you are weighing a reorganization or a manager change and want to see how it is likely to land first, you can request a simulation and tell us the situation. Engagements are invitation-only, so we will talk first about whether submove is the right fit.