Getting a team properly on board with a new project doesn't come down to one big announcement done well.

It's the accumulation of a lot of smaller things, done consistently, over the whole life of the change rather than just at the start of it. 

At JCM, this is what Business First, Software Later actually looks like in practice, and it's the difference between a project that lands and one that quietly gets worked around. 

These are, in our experience, the ten things that make the most difference.

If a team only hears about a new project once everything's already been decided, you've missed the best opportunity you had to build genuine buy-in.

Involving people while there's still room to shape the details, even in small ways, changes how they experience the whole project.

It stops feeling like something being done to them and starts feeling like something they had a hand in.

People can cope with a great deal of change if they understand the reason behind it.

Skipping straight to what's changing and how, without properly explaining why it matters and what problem it solves, is one of the most common causes of quiet resistance.

Take the time to connect the change to something the team already cares about, whether that's less frustration in their day, better information, or fewer awkward moments with customers.

In almost every team, there are a handful of people whose opinion genuinely shapes how others feel about something new.

Identify them early, bring them into the process before everyone else, and give them a clear understanding of what's changing and why.

Their support, modelled naturally in day-to-day conversations, tends to move a team faster than any formal communication ever will.

A change that's a minor adjustment for one part of the business might be a significant upheaval for another.

Take the time to map out who's actually affected, and how, rather than treating the whole team as one audience with one message.

The finance team, the people on the shop floor, and the customer-facing staff are usually all experiencing the same project quite differently.

​​​​​​​A single well-crafted announcement isn't a communication plan.

People need to hear important messages more than once, in more than one way, before they properly land.

A project that only gets communicated at kickoff and at launch will leave people confused in between.

Short, regular updates, even when there isn't much new to say, keeps people feeling informed rather than left in the dark.

​​​​​​​Most changes involve a period where things feel slightly harder before they get easier, and pretending otherwise tends to backfire.

If you're upfront about the fact that the first few weeks might be a bit clunky while everyone finds their feet, people are far more forgiving when that's exactly what happens.

Setting an honest expectation is more reassuring than a falsely smooth promise.

​​​​​​​Asking for feedback only works if people believe something will happen with it.

A suggestion box nobody ever mentions again quickly teaches a team that feeding back is pointless.

Create a simple, visible way for concerns and ideas to be raised, and make sure people can see that at least some of what they raise leads to a genuine response or change.

​​​​​​​People often struggle in silence rather than admit they haven't got to grips with something new, particularly if asking for help feels like it reflects badly on them.

Make it clear, repeatedly, that asking questions is expected and welcomed, not a sign of falling behind.

The businesses that get this right tend to normalise it from leadership downwards, with senior people visibly asking questions themselves.

​​​​​​​The first small successes of a new project are easy to let pass unremarked, but they matter more than they seem to.

A quick mention that a particular team solved a problem faster, or that a process that used to take an afternoon now takes twenty minutes, gives everyone else proof that the change is worth the disruption.

Momentum builds from visible, specific wins far more than from general reassurance that things are going well.

​​​​​​​

​​​​​​​It's common for senior leaders to be highly visible at the start of a project and then quietly disappear once the initial launch is done.

That gap gets noticed, and it sends an unintended signal that the project was never really a priority.

Staying visibly engaged throughout, asking how things are going, and being seen to use or reference the new way of working yourself, tells the team the change actually matters.

Change management isn't a phase, it's the whole project

None of these are complicated on their own, but together they represent a genuinely different way of running a project than treating change management as a single communication sent at launch. It's the same principle behind everything we do at JCM: business first, software later, and the team brought along every step of the way.

The businesses that get real, lasting engagement from their teams are the ones who treat these as ongoing habits, not a box ticked once near the beginning.

If you're planning a new project and want a partner who treats change management as part of the plan from day one, not an afterthought, we'd love to talk to you.