The Hardest Part Isn’t the Design
You’ve mapped your processes. You’ve found the bottlenecks. You’ve designed a better solution, maybe even set up automation. And now comes the hardest part: getting people to actually use it.
Because a new process on paper or in a system doesn’t mean anyone will follow it. Most organizational changes don’t fail because of bad design. They fail because of bad implementation.
Why Changes Fail: The 5 Most Common Reasons
1. Nobody explained why People don’t resist change itself. They resist being changed without explanation. When someone doesn’t understand the reason, they naturally stick with what they know.
2. Too much at once A new CRM system, a new approval process, new reports, and an organizational restructure - all starting Monday. The result? Overwhelm, frustration, and a return to old habits.
3. Nobody is responsible “We agreed on this in the meeting.” But who specifically is making sure it happens? Change without a clear owner is a wish, not a plan.
4. The old way is still possible If people can do things the old way, they will. When the new process exists alongside the old one, the easier one always wins - and easier means the one they already know.
5. Nobody asks if it’s working The change is implemented and then… silence. Nobody asks after a month: “Is it working? What bothers you? What’s missing?” Without feedback, problems accumulate until people stop using the new process entirely.
The Pilot Approach: Start Small
The most effective way to implement change is not to implement it everywhere at once.
How to do it:
- Pick one team or one department. Ideally one where people are open to change and where you’ll see results quickly.
- Let the new process run for 2-4 weeks. Long enough for real problems to surface, not just initial discomfort.
- Actively collect feedback. Not with a survey, but with a conversation. Three questions are enough: What works? What doesn’t? What’s missing?
- Adjust the process based on reality. No design survives contact with practice unchanged. That’s fine - adjust and continue.
- Only then roll out to everyone else. With concrete results and the experience of the pilot team.
The pilot has another advantage: the team that tested the process becomes a natural ambassador. Their colleagues are more likely to be convinced by a peer’s experience than by a management directive.
What to Tell Your Team: A Communication Template
When implementing change, you need to say five things. Clearly, concisely, without corporate jargon:
| Question | What to answer |
|---|---|
| What’s changing? | Specific description: “Starting next week, we’ll submit orders through a new form instead of email.” |
| Why? | A reason that makes sense: “Because we’ve been losing requests and can’t track their status.” |
| What does it mean for you? | Practical impact: “Instead of email, you’ll fill out a form - takes the same time. Plus, you’ll be able to see what’s happening with your request.” |
| When? | Clear timeline: “Pilot from April 15, company-wide from May 1.” |
| Who to ask? | Specific person: “If you have questions or issues, reach out to Petra. It’s her project.” |
That’s it. No 30-slide presentation. Five answers that fit in a single email.
How to Measure If It’s Working
You don’t need to build complex dashboards. A simple principle is enough: compare before and after.
3 questions to ask after one month:
- Is it faster? How much time did the process take before and how much does it take now?
- Are there fewer errors? How many things got lost, duplicated, or went wrong?
- Do people prefer the new way? Ask directly - not whether it’s great, but whether it’s better than before.
Tracking table
| Metric | Before change | After 1 month | Target |
|---|---|---|---|
| Order processing time | 45 minutes | ? | 25 minutes |
| Lost requests / month | 6 | ? | 0 |
| Team satisfaction (1-5) | 2.5 | ? | 4 |
Fill in the “before” values before implementing the change. Otherwise, you have nothing to compare against.
How to Handle Resistance
Resistance isn’t the enemy. Resistance is feedback. When someone says “this won’t work,” they often mean “there’s a problem you haven’t seen.”
4 principles:
Listen first. Before you argue, ask: “What specifically bothers you about this?” You’ll often learn something useful.
Find champions. In every team, there’s someone who sees the benefit and has influence over others. Involve them in the pilot. Let them speak for you.
Make the new way easier than the old way. If the new process requires more steps, more clicks, or more thinking, people will go back to the old one. Simplicity is the best argument.
Celebrate small wins. “Thanks to the new process, we didn’t lose a single order this week.” Concrete results are more convincing than any amount of explaining.
From Practice: The IT Company That Got It Right on the Second Try
An IT services company with 45 employees redesigned their customer ticket handling process. The old approach was chaotic - tickets got lost, customers waited, nobody knew who was working on what.
First attempt: On Monday, an email came from management: “Starting today, we’re using the new ticket system. Here’s a link to the guide.” By Wednesday, half the team was entering tickets the old way - the new system felt slow and confusing.
Second attempt: They selected one team (5 people) to test the new process for 3 weeks. During testing, they discovered two ticket statuses were missing and the form was unnecessarily long. They fixed it. The pilot team then presented results to everyone else: “We no longer waste time figuring out who’s working on what. We can see it at a glance.”
The result: Within 2 months, all teams switched voluntarily. Not because they had to - but because they could see it worked. Average ticket resolution time dropped from over 4 days to under 2 days.
Series Wrap-Up
We’ve walked through the entire journey together:
- Recognize the problem - where things in your company aren’t working as well as they could
- Map how it actually works - not how you think it works
- Find the waste - steps that don’t add value
- Design the target state - what it should look like
- Choose your tools - technology that supports the new process
- Automate repetitive steps - save time for work that actually matters
- Implement the change and make it stick - because without people, no process works
The key principle running through everything: Start small, prove it works, then expand.
You don’t need to be a process expert. You don’t need to know any methodology. You just need to look at how things actually work in your company and ask: “Can this be done more simply?”
Most of the time, the answer is yes.
Need Help?
If you’d like help with any of these steps - from mapping your processes to choosing the right tools to implementing change - get in touch. This is exactly what we do, and we’d be happy to help you find the places where a small change delivers a big result.