Skip to content

Consultor de Marketing Digital

Book a call (opens in a new tab)

Menu

Book a call (opens in a new tab)

Digital transformation · Adoption

New tools are only worth it if the team actually uses them

I support the rollout of new tools and processes in your store so the team understands them, adopts them and does not drift back to old habits.

Book a call (opens in a new tab)

In short

Change management and adoption is the work of preparing and supporting people when a business changes its tools or processes, so the change is actually used. For online shops and SMEs, that means involving the team early, giving hands-on training, creating simple documentation and following up on usage in the first weeks. It is for businesses that have already invested in new tools or processes and need the team to build them into daily work.

Why changes do not stick

  • The team was not consulted

    The tool was chosen without asking the people who will use it, and the team feels their job has been made harder.

  • One-off, generic training

    There was an initial demo, but nobody showed each person how to do their own specific tasks.

  • Parallel systems

    The new tool runs alongside the old spreadsheet, and the data ends up split between the two.

How I support change

I involve the team before the change, not after. Training is organised by role and task, documentation is short and practical, and usage is followed up so difficulties are spotted early.

  • Conversations with the team before the change to surface concerns
  • Role-based training using each person's real tasks
  • An internal go-to person for day-to-day questions
  • A set date for switching off the old system

What you get

  • Change plan

    Who is affected, what changes for each person, and a timeline for communication, training and launch.

  • Training sessions

    Hands-on, role-based training, in person or remote, built around your store's real tasks.

  • Support documentation

    Short guides and step-by-step videos for the most frequent tasks, easy to look up.

  • Early-weeks support

    Regular check-ins to answer questions, gather feedback and adjust whatever is needed.

  • Adoption indicators

    A simple way to track whether the tool is being used as intended.

How the work runs

  1. Preparation

    I identify who is affected, gather concerns and set the communication and training plan.

  2. Training

    I run role-based training and hand over the documentation before launch.

  3. Launch

    I support the launch closely, responding quickly to questions and problems.

  4. Consolidation

    I track adoption indicators, adjust training and confirm parallel systems have been retired.

Tools I use

  • Notion
  • Loom
  • Google Workspace
  • Slack
Does this make sense for a small team?

Yes. In a small team, every person who does not adopt the change has a big effect on the outcome. The format scales down: fewer sessions, more direct support.

Can you support adoption of a tool you did not choose?

Yes. I am often brought in after a tool has already been chosen or installed. I start by understanding how it is configured and where the team is struggling, and only then prepare the training.

What if someone keeps resisting the change?

Resistance usually has a concrete reason: a task that got harder, a lack of training or a fear of getting things wrong. I try to understand that reason with the person and adjust the configuration, training or process. If resistance persists, the management decision rests with whoever leads the team.

Related tools

Some links are affiliate links: if you sign up, I may earn a commission at no extra cost to you. It never changes my assessment. How this works

Related articles

Invested in a tool your team does not use?

Book a discovery call. I will work out where adoption is failing and show you how to get it moving.

Book a call (opens in a new tab)

Newsletter

Practical notes for WooCommerce stores