A new management system should make work easier. But in the first days of a rollout the opposite can happen: staff can't find the data they need, orders are recorded in two places, and the manager keeps hearing “the old way was faster”.
To reduce these difficulties, decide in advance what you are changing, who is responsible and how the team will keep serving clients during the transition.
Let's look at how to organise that transition step by step.
1. Start with one clear problem
“We want to digitise the business” doesn't help you decide where to start. Instead, describe the problem that gets in the way of everyday work.
For example:
- Information about orders is scattered across emails, messages and different spreadsheets.
- A salesperson can't say for sure whether a product is in stock.
- Finding out when an order will be ready means calling several people.
- The client's payment has arrived, but the person in charge of the order doesn't know.
Choose one main problem to solve in the first phase. Then put the expected result into words.
Example: “Every active lead must have one record, an owner, a current stage and an agreed deadline.”
A statement like this already shows what needs setting up in the system and what the team needs to learn.
2. Describe the workflow you have today
Before configuring the system, find out how the work is actually done today. Involve the people who receive, carry out and deliver the orders.
In a sample furniture workshop, the process might look like this:
Request → measuring → quote → approval → production → delivery → closing
For each stage, answer four questions:
- Who is responsible?
- What information do they need?
- How do you know the stage is finished?
- Who is the next step handed to?
This often uncovers problems that need solving before you even choose software. For example, if nobody is responsible for agreeing the delivery date with the client, adding a “Visit” stage to the system isn't enough. Someone has to own that task.
Build the initial setup around a simple, clear process. You can develop it later based on real experience.
3. Appoint someone to lead the rollout
The team needs to know who to go to with questions, who approves working rules and who stays in touch with the specialist implementing the system.
In a small business this can be the manager or an employee who knows the processes well. What matters is that they actually have time for it.
Their main tasks are to:
- collect the team's requirements and questions,
- agree the scope of the first phase,
- organise data checks and training,
- log problems and follow them up until they are solved.
Also decide who can approve extra costs or changes to the way work is done. That avoids the rollout stalling because decisions haven't been made.
4. Prepare your data before moving it
The quality of the data you move into the new system affects work from day one. Duplicate clients, outdated prices or wrong stock levels will cause confusion in the new environment too.
First decide what you need to get started. This may include:
- details of current clients and suppliers,
- active products and services,
- open orders,
- checked stock levels,
- outstanding payments.
Then remove duplicates, agree on names and decide which fields are required.
Example: if the same product is called “Table white” in one file and “White table” in another, importing by name alone can create duplicate cards. A single product code helps identify it.
Before the full migration, test a small batch of data. Check that amounts, dates, units of measure and links between records came across correctly.
Keep a copy of the original data as well, and decide who may open or change it.
5. Run a limited pilot
Run the pilot within one team, branch or process. Choose a scope where you can test ordinary working situations and support participants quickly.
Don't test only the happy path. Also try:
- changing an order,
- a cancellation or return,
- a partial payment,
- replacing the person responsible,
- correcting a wrong entry.
Before the pilot, decide under what conditions you're ready to widen the rollout.
For example: every pilot order has an owner and a deadline, staff can do the main actions on their own, and checks of payments and stock show no unexplained differences.
Tie the length of the pilot to the work being tested. If the process includes production and delivery, you need to see those stages finish too.
6. Teach everyone what they need for their own job
After a long tour of the whole system, an employee may still not know how to register tomorrow's order.
Organise training by role and around real tasks:
- Salesperson — create a client and order record, find the current status.
- Warehouse staff — record stock movements and check stock levels.
- Production lead — see tasks, update stages and deadlines.
- Manager — find delays, view key figures and who is responsible.
Have each participant carry out their main actions themselves on test data. Prepare short instructions for frequent tasks too.
During training, write down people's questions. If several people find the same step unclear, review the setup and the working rule as well.
7. Decide clearly where the final information lives
One of the most confusing moments in a transition is when the same order has different data in a spreadsheet, in the system and in a messaging group.
For each process you launch, decide where the current, confirmed record is kept.
For example:
“From launch day, new orders are registered and updated in the management system. The old spreadsheet is kept as a read-only archive.”
Some data may need temporary parallel records for comparison. If so, define its purpose, owner and end condition in advance, and take the extra workload into account.
The team must know exactly who checks and confirms the correct version when data doesn't match.
8. Prepare launch day and a fallback plan
Pick a relatively quiet period for launch. Check logins, user permissions and the devices and connections needed for work in advance.
Also confirm:
- who is available for urgent questions,
- how problems are logged,
- which problems require work to pause temporarily,
- how work continues if the system is unavailable.
For example, if the system is temporarily down, orders can be taken on a prepared paper form. Someone should be assigned to enter those records once it's back and check that no duplicates were created.
If sales, payments or deliveries depend on the process, discuss the recovery steps before launch.
9. In the first weeks, measure results and remove obstacles
After launch, regularly gather the team's observations: which step takes too long, which data is missing and which action is often done wrong.
Judge the result against the problem you chose at the start. Useful measures might be:
- the number of orders without an owner or deadline,
- the time it takes to find an order's status,
- the share of late orders,
- the number of data corrections and duplicate records,
- the main actions staff still need help with.
Record the same measures before the rollout so you can compare. How often people log in isn't enough to tell whether work has improved.
If a problem persists, find out why: perhaps the setup is awkward, data is missing, someone needs more training, or the working rule still isn't clear.
Before launch, go through this checklist
- The first-phase problem and the expected result are clear.
- Work stages and owners are agreed.
- Someone is leading the rollout.
- Data has been cleaned, checked and backed up.
- Changes, cancellations and error corrections have been tested too.
- Staff have tried their main actions.
- It's decided where confirmed information is kept.
- A procedure for carrying on during an outage is ready.
- The measures for judging the result are defined.
A management system rollout succeeds when the team understands what changes in their work and who will help them move to the new way of working. Moving in small, tested steps lets you spot problems while they're still easy to fix.
Where should you start in your business? Pick one process where information often gets lost or work gets delayed. Describe its stages, owners and the data needed. With that description you can contact the TM Hub team to discuss the scope of the first phase.
