Blog · Enterprises

How to implement a new system without your team rejecting it

A new system works when the team uses it. For that to happen, the people who will use it need to take part from the assessment stage, understand how it helps in their daily work, learn it with support, and have someone to ask during the first few weeks. When this does not happen, rejection sets in: parallel spreadsheets, constant comparisons with the old way of working, and a system that is only partially used.

By Ana Laura Mazas, Co-founder of LogTech® and organizational psychologist · 3 min read

Why resistance appears

Resistance to a new system is rarely about the technology itself. It usually has other causes:

None of these reactions is irrational. They are expected responses to a change in how people work, and it is best to treat them as part of the project, not as an obstacle created by the people involved.

Before development: listen to the team

The people who do the work every day know the critical points in the process, the usual exceptions and the informal workarounds they rely on. Including them in the assessment improves the system and, at the same time, helps them recognize it as something designed for them. We recommend talking with each area, observing how the work is actually done, and validating the first designs with the team.

During implementation

  1. 01

    Explain the purpose

    What specific problem the system solves in each person's work.

  2. 02

    Train by role

    Each person learns the part of the system they will use, with examples from their own work.

  3. 03

    Identify go-to people

    Team members who learn first and support the others.

  4. 04

    Roll out in stages

    One area or one process at a time, so the change stays manageable.

  5. 05

    Plan for the transition period

    During the first few weeks, tasks may take longer. This is expected, and it is worth saying so openly.

After delivery

The role of those who lead

The managers of each area play a central role: if they keep asking for the usual spreadsheet, the team concludes that the system is optional. Using it themselves, acknowledging the effort involved in learning it, and sustaining the change over time make the difference.

Frequently asked questions

Short answers to the most common questions on this topic.

How long does it take for a team to adopt a new system?

It depends on the scope and on the team. What matters is providing particular support during the first few weeks, which is when it becomes clear whether the system will be used or abandoned.

What should I do if someone refuses to use it?

It is best to have a conversation to understand what lies behind it: difficulty, fear, lack of time, or a real problem with the system. Often a necessary improvement comes to light.

Is training a separate service?

At LogTech® Software & Soluciones Tecnológicas, training is part of the implementation: when we deliver a system, we support the team as they start using it.

More articles

How we work at LogTech®

At LogTech® Software & Soluciones Tecnológicas, we develop the system and support the team throughout its implementation. We start by understanding how each area works, train people in their own context, and remain available while they settle into the new workflow. This approach, which brings technology and people together, also draws on organizational psychology. More details on our implementation and training page.

Hablemos de tu proyecto

¿Listo para automatizar tu futuro?