How to roll out planning software step by step

Rolling out software in a small technical company has one particular feature: nobody in it has the role of systems administrator. The deployment has to be handled by the same person who also plans, sells and occasionally drives out to a customer. The procedure has to reflect that.

The following breakdown into days is a working proposal, not a measured promise. A small team with a few live orders can move faster; a larger company or a more complex data transfer will need more time.

Monday: the foundation

• Create the company and add the technicians. For each one, enter straight away the skills that decide where they can go.
• Go through the default order statuses and appointment types. Rename whatever does not match your practice. Do not add anything you are not yet sure you need.
• Enter the known absences for the next two months.

What to avoid: inventing the perfect tag structure. You will add tags in a month, once you see what you need to filter by.

Tuesday: running orders

Enter the orders that are currently running. Not the archive and not last year's orders, just the current ones. For each one, the name and the customer are enough; the rest gets filled in as you go.

Do not transfer the history. It is days of work and nobody will ever look at it. Leave the old system available as read-only.

Wednesday: the first real week

Plan next week in the new tool, and only in it. If planning goes on in both tools for a long time, the team will not switch, because the spreadsheet remains the source of truth.

Thursday: the technicians

Show the technicians the mobile view in practice: send them the link and let them open their own day. Match the length of the demonstration to how many tasks you want from them in the first phase.

Give them a single requirement: in the morning, look at your phone to see where you are going. Add starting work, logging tasks and a short note for the office as further habits only once the team has found its way around the daily plan.

Friday: the first appointment offer

One concrete result convinces the team best. Take an order where an appointment is being arranged, generate an offer and send the link. As soon as the customer picks one of the options, you can show the team the whole process on a real response.

Second week: no changes

Do not add anything, just collect feedback. Most of it at first concerns habit, not the tool, and loses weight after the first few days of use.

Third week: fine-tuning

Now you know what you really need. Add tags and missing skills and adjust the text of the appointment offer so that it matches the way you express yourselves. This is the right moment, not day one.

The five most common reasons a roll-out fails

1. Parallel operation without an end. As long as there are two truths, the old one wins.
2. Migrating the history. It consumes a large part of the roll-out and nobody ever looks at it.
3. Too much configuration at the start. Twenty order statuses nobody can tell apart.
4. The technicians were given no reason. If they get no benefit from the tool, they will not use it. The benefit is knowing where they are going, without phone calls.
5. One person rolls it out in secret. A tool the team does not know about is not a rolled-out tool.

A roll-out is not a project. It is a decision about the day from which the new plan applies.

How to tell it worked

• The manager does not open Excel in the morning, because there is nothing in it.
• Technicians call the office noticeably less.
• You answer the question who is free next week during the call.
• Appointments are arranged by link and the specific choices come back into the overview.

If three of the four points hold after a few weeks, the foundation works. Fine-tune the rest according to what the team actually uses.