Editorial note: This article is a fictional reconstruction of situations businesses may face. Its purpose is to inform and raise awareness about possible risks and responses. People, events, data and outcomes should not be interpreted as actual cases, verified facts or results achieved by LC. Each organization needs its own assessment.
Company leadership introduces a tidier work system. The team stays quiet and keeps using old spreadsheets. Marcos reads it as resistance to change. When he asks why, he learns the migration requires duplicate entry for weeks and gives no answer about who fixes errors. Listening to those objections does not mean giving up the goal.
Explain the problem and acknowledge the cost
Marcos shows cases of lost information the system should prevent. He also estimates transition hours, training and support. Promising an easy change when it is not harms trust. Communication improves when people understand why change matters and what resources they will have while learning.
Test with the people doing the work
A small group uses the new approach on real cases. It finds unnecessary fields, missing permissions and exceptions the design ignored. Marcos keeps a way to fix problems and tells the team which suggestions were adopted. Participation is not a vote on every detail; it brings operational knowledge in before rollout.
Measure adoption and outcomes together
The team reviews correct use, duplicate work and cases no longer lost. If a tool is used only because it is mandatory but consumes more time, rollout needs adjustment. Marcos names owners and a support period. Change becomes real when it can be sustained without a permanent campaign.
Listening to operational friction helps design change that lasts.
BRING IT TO YOUR BUSINESS
Three questions to get started.
- What problem will the team see solved?
- What extra work does transition create?
- Who will fix rollout problems?
Does this sound like a challenge in your business? We can start with a conversation.
Talk to LC↗