Users move to the new interface when they're ready
Screen by screen or team by team. The old interface stays as a fallback until the new one earns the trust of the people who use it.
How we switch users over
Example: a job panel at a field service company.
- 1Pilot groupA first group of users works in the new interface and sends feedback.
- 2FixesWe fix the pilot feedback before the new interface reaches more people.
- 3Team by teamWe switch one team at a time. Anyone can go back to the old interface with one click.
- 4Old one switched offWhen nobody uses the old interface any more, we switch it off.
Signs you need a gradual rollout
Users dislike change
You can't stop
Different teams, different needs
Mistakes cost money
Tools for a safe switch-over
Every user can go back to the old interface until the new one wins them over.
Interface switch
Same login
Feedback channel
Usage stats
Short training
Switch-off plan
How we track the rollout
Every week we look at how many people work in the new interface and how many go back to the old one.
- 1Users on the new interface
- 2Returns to the old one
- 3Feedback received
- 4Feedback fixed
When returns to the old interface drop to zero, it can be switched off.
Common questions
Isn't running two interfaces expensive?
Both use the same backend, so the extra cost only applies during the transition.
Who decides when a team moves over?
You, together with the team lead. We provide the usage and feedback data.
What if people don't want to switch?
We find out what's holding them back and improve the new interface. It's usually a few specific screens.
Is data entered in the new interface visible in the old one?
Yes. Both work on the same data.
Tell us who uses the system
Let us know how many people and teams work in it and how the last change went. We reply within one business day.