Get a Change Adopted, Not Just Announced
Practice for the stretch between the announcement and the day the new way is simply how work is done, and for the supervisors who have to carry a decision they did not make.
What happens between the announcement and the floor
A change is announced on a Friday. The new format is explained once, in a room, by someone who has known about it for weeks. On Monday the supervisor has to answer questions the announcement did not cover, and the person who was never consulted decides to wait and see. Within a month the old register is back out of the drawer and the figures are reconciled by hand. This session works that stretch.
What the sessions work on
The Announcement Nobody Prepared For
What people actually hear when a change arrives at short notice, why the first reaction is usually about lost competence rather than about the change itself, and what a supervisor can usefully say in the first hour.
Reading the Curve in Your Own Team
The stages people move through between the announcement and ordinary working, mapped onto a change your business has genuinely been through, so participants can name where each person on the floor currently sits.
Carrying a Decision You Did Not Make
How a team lead answers “why are we doing this” honestly, without either defending a plan they were never consulted on or quietly joining the complaint about it.
Running Two Systems at Once
The cutover period, when the old process and the new one both exist: what to hold people to, what to let slide, and how to stop the old format becoming the real one again by default.
Sorting What Is Actually Yours to Decide
Splitting a change into what is settled, what is still open to influence, and what is simply yours to work with. Done against a live change, so the list is real rather than an exercise.
Saying What Is Not Yet Settled
Communicating a change while parts of it are still undecided: what to state, what to hold, and why going quiet costs more on the floor than admitting a decision has not been taken.
When the Objection Is Correct
What to do when the resistance is reasonable. Participants work out which objections are information the business needs back, and how to route them so they reach someone who can act on them.
What it is meant to change at work
Reversion Gets Noticed Early
Supervisors know what quiet reversion looks like — the parallel sheet, the WhatsApp workaround, the batch corrected at month end — and raise it while it is still one person's habit.
Objections Reach a Decision-Maker
What the floor says about a change arrives upstairs as usable information rather than as grumbling, because the people hearing it have a route for passing it on.
Team Leads Stop Being Stuck in the Middle
Supervisors have wording for the conversation where they must hold a change they privately have doubts about, so they neither over-promise it nor undermine it.
The Cutover Has an Agreed End
The team knows the date the old way stops being acceptable, and what happens to the work still sitting on it.
How GullyHR runs this one
Built Around a Change You Are Actually In
The material is written from the reorganisation, system rollout or policy shift in front of you, de-identified where it needs to be. A generic change exercise teaches nothing on this subject.
Supervisors and Their Teams, Usually Apart
Team leads need to rehearse answers they cannot rehearse in front of their own people. We advise on the cohort split at the needs discussion rather than after nominations.
We Will Tell You When It Is the Plan
Training people to absorb a badly announced change is an expensive way to avoid announcing it properly. Where the sequencing or the communication is the fault, we say so instead of running the workshop.
Timed Against the Rollout
Sessions are placed where they are useful — before the announcement for managers, during the cutover for the floor — rather than wherever the calendar was free.
Work the change you are in the middle of
Tell us what is changing, when it was announced and who has to carry it. We will say what training can do about that, and what it cannot.
Frequently Asked Questions
Yes, and that is usually the better order. Managers rehearse the announcement and the questions that follow it before the news is out, instead of recovering afterwards. Tell us the timeline at the needs discussion so the sessions sit where they help.
Possibly not, and it is worth checking before you buy. Where the fatigue comes from changes arriving faster than any of them can be embedded, the fix is sequencing, not a session on mindset. We look at what has landed on that team this year first.
No, and nobody can honestly promise that. It equips supervisors to recognise what sits behind the resistance, answer it straight, and escalate the parts that are genuine design problems. What people then choose to do remains theirs.
Scoped with you, not fixed in advance. It depends on how many of the areas above the cohort needs, whether managers and the floor train separately, and whether sessions are placed around a live rollout. The proposal states the pattern before you commit.