Change management in GTM: make adoption part of the commercial plan

A new GTM strategy can be clear in a presentation and still remain absent from everyday decisions. The CRM fields have changed, the training is complete and the launch email has gone out. Yet opportunity reviews, customer handoffs and prioritisation continue much as before.

That gap is where change management belongs. It connects the intended commercial direction to the behaviour needed to deliver it.

Adoption is not a communications task to add after design. It is part of the operating design itself.

Begin with the business reason for change

‘We are introducing a new process’ describes an action, not a reason. Teams need to understand what is not working, why it matters and what a better outcome would look like.

For example, a redesigned sales-to-delivery handoff might aim to reduce ambiguity about customer commitments. Its purpose is not simply to make everyone complete another form.

Describe the commercial problem in language the affected teams recognise. Be equally clear about what the change will not solve. This creates a more credible starting point than promising that a new tool or structure will fix everything.

Translate the change into specific decisions

Broad expectations such as ‘be more customer-centric’ are difficult to act on. Define what people will do differently at the moments that matter.

Who qualifies an opportunity? What evidence is required before a deal advances? Who approves an exception? What must delivery know before a commitment is made?

Write down the owner, the decision, the inputs and the handoff. Check whether the new expectation fits available time, authority and capacity. If it does not, resistance may be a useful signal about the design rather than a lack of commitment.

Involve the people closest to the work

Leadership alignment matters, but it does not replace frontline input. Sellers, managers, marketers and customer-facing delivery teams can reveal where a proposed workflow collides with reality.

Use a bounded pilot with a clearly defined team or customer segment. Observe the work, collect feedback and decide what to simplify before extending it.

A hypothetical example: a new account-planning template may look comprehensive but be too demanding for smaller accounts. The pilot could reveal the need for a lighter version rather than more reminders to complete the original. This is an illustrative scenario, not a client case study.

Enable the manager, not only the individual

A training session can introduce a method. Manager routines help turn it into a habit.

Give managers practical examples, coaching questions and clear escalation paths. Align review meetings with the new decisions rather than asking teams to work one way and report another.

Also examine incentives. A team asked to prioritise margin while being rewarded only for bookings is receiving conflicting instructions. Communication cannot resolve an operating contradiction that remains in place.

Treat AI adoption as a workflow change

An AI tool changes more than the speed of a task. It can change who produces an output, who checks it and who remains accountable for the decision.

Define permitted data, review requirements and situations where the tool should not be used. Make it clear how people report poor outputs or unintended consequences without fear of being judged for raising a problem.

Measure usefulness in the actual workflow, including rework and review effort. Usage alone does not establish better quality or commercial value.

Measure adoption and outcomes separately

Completion metrics are useful but incomplete. Attendance, logins and filled-in fields tell you that an action occurred; they do not necessarily show that the work improved.

Pair adoption evidence with an outcome appropriate to the change. For a handoff redesign, examine whether agreed information is present and whether avoidable clarification or rework decreases. For a qualification change, examine evidence quality alongside progression and conversion.

Agree on a baseline and review cadence. Use the review to adapt the design, not merely to enforce compliance. Retain what improves the work and remove steps that add burden without value.

Change becomes sustainable when leaders reinforce it, managers can coach it and teams can see why it helps. The launch is a milestone. Changed practice is the work.

Explore the revenue engine methodology, or start a strategy conversation.