How to build a company culture open to technology innovation

Software can go live while half the team stays on the old method. Change management in an SME is light but real: sponsor, super-users, shutting down parallels and measuring adoption — not a theatre of kick-off slides.

Train on daily cases. Turn off one parallel at a time. If usage stays low, fix friction before adding features.

Adoption over go-live

Name a sponsor and area super-users for the first fifteen days. Schedule short sessions on real tasks, not the full manual.

Measure real usage. Celebrate closed parallels. Keep a visible exception log so old habits do not silently return.

What to leave out on purpose

The first release is not the moment to prove everything the tool can do. Leave out features without an owner, integrations to little-used systems, automations on rare exceptions and aesthetic reports not tied to a decision. Expanding after the numbers is courage. Expanding before is anxiety dressed as ambition.

Dirty data, dirty results

If records and inputs are messy, any automation or language model amplifies the mess. Dedicate an explicit block to minimal clean-up on the MVP perimeter: duplicates, required fields, out-of-range values. That is not «IT work». It is operational truth.

Training that sticks

Short sessions on the team's real cases. A checklist within reach. A super-user per area for the first fifteen days. Avoid catalogue courses that end in a certificate and zero change the following Tuesday.

How you know you are improving

Do not multiply dashboards. Pick a few indicators tied to the process you are touching — on build a company culture open to, cycle time, output quality and adoption of the official flow usually suffice. Set baseline in week zero. Review at thirty days. If numbers do not move, change process and inputs before you change the tool.

A detail that makes the difference

Block calendar time for the pilot. Without dedicated slots the project stays «between other things» and never really starts. The operating owner updates status every week in five minutes: done, blocked, next step. It is not elegant. It works.

How you know you are improving

Do not multiply dashboards. Pick a few indicators tied to the process you are touching — on build a company culture open to, cycle time, output quality and adoption of the official flow usually suffice. Set baseline in week zero. Review at thirty days. If numbers do not move, change process and inputs before you change the tool.

A detail that makes the difference

Block calendar time for the pilot. Without dedicated slots the project stays «between other things» and never really starts. The operating owner updates status every week in five minutes: done, blocked, next step. It is not elegant. It works.

What to leave out on purpose

The first release is not the moment to prove everything the tool can do. Leave out features without an owner, integrations to little-used systems, automations on rare exceptions and aesthetic reports not tied to a decision. Expanding after the numbers is courage. Expanding before is anxiety dressed as ambition.

Dirty data, dirty results

If records and inputs are messy, any automation or language model amplifies the mess. Dedicate an explicit block to minimal clean-up on the MVP perimeter: duplicates, required fields, out-of-range values. That is not «IT work». It is operational truth.

Training that sticks

Short sessions on the team's real cases. A checklist within reach. A super-user per area for the first fifteen days. Avoid catalogue courses that end in a certificate and zero change the following Tuesday.

Dirty data, dirty results

If records and inputs are messy, any automation or language model amplifies the mess. Dedicate an explicit block to minimal clean-up on the MVP perimeter: duplicates, required fields, out-of-range values. That is not «IT work». It is operational truth.

Practical schema to bring to a meeting

Short version to bring to a meeting.

Steps

1. Write the business goal in one sentence + out of scope.
2. Name owner and sponsor.
3. Define an MVP with acceptance criteria.
4. Run a real-user pilot and log exceptions.
5. Review KPIs; go/no-go on expansion.

Quick checklist

• Goal written down.
• Owner active.
• MVP defined.
• Pilot planned.
• KPI baseline set.

KPIs (max three)

• Average process time (before/after).
• Error or rework rate.
• % usage of the official flow.

Practical value (and the next step)

Software going live is not enough if half the team stays on the old method. Practical value is real adoption: fewer parallels, fewer errors and work flowing on the new system.

Name a sponsor and super-users, shut down one parallel at a time and measure real usage. Train on daily cases, not the whole manual.

If you want a second opinion on the scope of your case, Foggetti Studio can help you read the current state and define a realistic MVP.