What makes more sense: a simple tool that can do little, or a powerful system that is never pushed to its limits? If those were the only choices, the simple tool would win – no rollout effort, but permanently mediocre efficiency in return. Anyone who wants to truly improve their processes should therefore not cut corners on rollout and training. A system whose strengths nobody puts to use is of no use at all.
How long does a rollout take?
A sensible rollout usually takes between 5 and 10 days – training already included. It is theoretically possible to attempt it on your own, but that is not recommended. It depends on your level of expertise and the time you are willing to invest yourself.
The standardised procedure
So that the rollout succeeds quickly and systematically, we work according to a fixed pattern.
Working block by block
The most important point: we work block by block.
- In the first kick-off we plan concretely which modules you start with in which order.
- Each module is given a four-hour block and a scheduled date. That way you know exactly which day, say, the finance module falls on, and can bring in the right expert from your organisation.
- This settles in advance when the system will be fully configured – and lets the consultants plan their time better (they, too, work in four-hour blocks, so the day doesn’t become fragmented).
How a block runs
- Closing of the previous topic (this is omitted the first time).
- Interview to clarify and document the concrete requirements.
- The consultant configures the system.
- At the end we demonstrate the solution and fine-tune it.
Every process has to be discussed, fine-tuned, demonstrated and signed off in this way. A shared, pre-filled document keeps everything on track and gives you something to follow – it also records who still has to do what and what is already finished.
The most important tip: training only in the finished system
Never run training in a system that isn’t yet set up. Otherwise the participants won’t know whether they are looking at an interim state or whether something will still change – and they end up disappointed, or build up reservations that you later have to break down again with great effort. Only once everything is in place should the training sessions be discussed and carried out.
Notes
- Planning conserves energy: an unplanned rollout that drags on endlessly consumes a great deal of energy and is rarely successful. It is better to do it professionally and to a schedule.
- Before the rollout comes the test: Testing teamspace properly. After it follows the transition into productive operation: Going live & support contract.
Related topics
- Testing teamspace properly Basics Concept
- Going live & support contract Basics Concept
- The modules at a glance Basics Concept