Leading through change.

To lead a team through change, answer four questions in the first conversation and keep answering them until the change is old news: what is changing, why it is changing, what it means for me personally, and what happens next. Say it early, say it in person, say the parts you have not worked out yet, and give people a real say in how the change is put into practice even when the decision itself is not up for debate. Almost every change that goes badly in a small business goes badly because one of those four questions was left hanging and people filled the silence themselves.

That is the whole method, and it is not complicated. What makes it hard is that the instinct pulls the other way. When a change is coming you want to have it fully worked out before you talk about it, because half an answer feels unprofessional. Meanwhile the team has seen the meeting in the diary, noticed the new supplier, watched two managers go quiet, and started guessing. You are never choosing between telling them and not telling them. You are choosing between your version and theirs.

Why does change feel like a threat even when it is good news?

Change removes certainty, and people treat uncertainty as risk. It does not matter much whether the change is objectively positive — a new system that will save everyone an hour a day still lands as "something I know how to do is being replaced by something I do not". Underneath the operational questions, most people are working out three things: am I still needed, am I still respected, and am I about to look incompetent in front of people I work with.

This is where the emotional change curve is useful. People move through a fairly predictable sequence — shock, resistance, a dip, then exploration and commitment — and they do not all move at the same speed. As the owner you have usually been living with the change for weeks before anyone else hears about it, so you are already at acceptance while the room is still at shock. Expecting the team to arrive where you are on the day you tell them is the single most common leadership mistake in a change, and it makes normal reactions look like disloyalty.

Step 1: Work out what is actually changing before you say anything

Write down, in plain sentences, exactly what will be different on the other side. Not the strategy behind it — the daily reality. Who reports to whom. Which jobs move. What stops. What starts. Which clients get contacted differently. If you cannot write it in a page, you are not ready to announce it, and the questions you cannot answer will be the first ones asked.

Then do the harder pass: for each person in the team, write one line on what this specifically means for them. A restructure that reads as sensible on an organisation chart can mean one person losing the part of the job they liked most. You want to know that before they tell you, because your response to it will set the tone for everyone watching.

Step 2: Communicate early, with the gaps left visible

Tell people while the change is still being shaped, not once it is finished. The formula that works is: here is what is happening, here is why, here is what we have decided, here is what we have not decided yet, and here is when I will next update you. That last part carries more weight than owners expect. A team can live with not knowing for two weeks. They cannot live with not knowing indefinitely, because open-ended uncertainty is what turns into job hunting.

Do it in person and do it in one sitting where you can. Telling a few people first so they can help you land it usually means the rest hear it second-hand within the hour, and being in the group that found out late is a genuine insult that will be remembered long after the change itself is forgotten.

Step 3: Answer "what does this mean for me?" explicitly

Owners answer the first two questions well and skip the third, because it feels personal and it is the one most likely to produce an awkward response. It is also the only question most people are actually listening for. Until someone knows whether their job, their pay, their hours and their standing are affected, they are not processing anything else you say.

Say it plainly, including when the answer is uncomfortable. "Your role does not change at all" is a sentence worth saying out loud to the four people it applies to. "Your role changes and we need to talk about it properly this week" is better than a vague reassurance that unravels a fortnight later. The formula for change makes the point neatly: change happens when dissatisfaction, a clear picture of the future and a first practical step together outweigh the cost of moving. Vagueness attacks the middle term.

Step 4: Give away the "how"

You may not be able to share the decision. You can almost always share the implementation. Sequencing, who takes which piece, what a sensible handover looks like, which bit of the plan will break in week one — the people doing the work know things about that you do not. Involving them is not a courtesy exercise; it produces a better plan and it converts spectators into participants.

Be honest about which is which. If the decision is made, say it is made. Consulting on something you have already settled is worse than not consulting at all, because it teaches people that your questions are theatre. Give away the part you can genuinely give away and defend the rest openly.

Step 5: Watch for the quiet ones

Vocal disagreement is manageable — it is visible, and you can answer it. The bigger risk in a small team is quiet disengagement, because it looks like acceptance right up until someone resigns. During a change, run short one-to-ones with everyone, and ask real questions rather than requesting updates. "What is the part of this you are least comfortable with?" gets you further than "any concerns?", which reliably produces the word no.

If the same worry surfaces in three separate conversations, treat it as information about the plan rather than a mood to be managed. Sometimes the team is right and the change needs adjusting. Saying so publicly costs you nothing and buys an enormous amount of credibility for the next one.

Step 6: Hold a rhythm until the change is old news

Most changes are announced once and then assumed to have landed. In practice, a change needs a rhythm: a weekly ten-minute slot for the first month where progress and problems are surfaced, then a fortnightly one, then it folds back into normal management. Say the same things repeatedly. The point at which you are bored of your own message is roughly the point at which the team has heard it.

Then close it. Tell people it is done, say what improved, and name the people who made it work. Changes that are never formally finished leave a team permanently braced for the next announcement, which is exhausting and quietly expensive.

What does this look like in practice?

Take a nine-person business moving from everyone doing everything to two defined teams with a lead each. For example, the owner spends a week writing the plan, then talks to the two new leads individually before anything is announced, so neither hears about their own promotion in a group. The whole team is told on the Monday: what changes, why, what happens to each person, what is not decided yet, and that there will be an update every Friday for six weeks.

Weeks one and two are messier than expected — work falls between the two teams, and one person makes it clear in a one-to-one that they think the split is arbitrary. The plan gets one visible amendment as a result. By week eight nobody refers to it as the new structure, and the owner closes it in a Friday meeting by naming what has improved. Twelve weeks, one adjustment, one difficult conversation handled properly. That is a change going well, not a change going perfectly, and it is worth knowing the difference before you start.

A checklist for the first four weeks

• Before the announcement. One page describing life on the other side. One line per person on what it means for them. The two or three questions you cannot yet answer, written down so you do not fumble them.
• Day one. Everyone hears it at the same time, from you, with the reason attached. Diarise the next update in the room.
• Week one. A one-to-one with every person, no agenda, one real question each.
• Weeks two to four. A standing ten-minute slot on progress and problems. Fix the first thing that breaks visibly, so people see the plan is not sacred.
• End of the change. Say it is finished, say what improved, name who carried it.

None of this requires a particular personality. It requires you to be clear before you are comfortable, and to keep talking after the interesting part is over. That is a skill you can build deliberately, and it is exactly the ground leadership coaching covers — alongside the related problem of what to do when someone will not come with you, which is the subject of our guide to managing poor performance. If the change involves building a stronger team structure as you go, our guide to building a high-performing team picks up where this one stops.