New systems are supposed to make work easier. But if your team sees an ERP rollout, new approvals, or performance dashboards as extra work layered on top of an already full day, adoption can stall, and the business keeps paying for the old way and the new one.
For a business growing from $3 million to $10 million, change management is how you protect momentum while building the systems that make the next stage possible. The goal isn’t simply to launch software. It’s to help people understand, use, and sustain better ways of working.
Why change management matters at $3M–$10M
At this stage, growth often exposes the limits of founder-led, spreadsheet-driven operations. Approvals depend on who is available. Information lives in separate systems. A month-end close takes longer than it should. The owner is still the person everyone asks when a process gets stuck.
A new system can connect processes and improve visibility, but only if people use it consistently. If employees keep tracking inventory in spreadsheets or send approvals through informal messages, you may have more software without better control.
That’s why business transformation needs both process optimization and attention to the people doing the work. Clear leadership, useful training, and ongoing reinforcement help build a business culture where new routines make sense, and stick.
Start with the work, not the software
Before choosing what to configure or train, identify what needs to improve. Make the business problem specific and connect it to outcomes your team can recognize.
For example:
- If purchase approvals are slow, map where requests wait and who has decision authority.
- If sales-to-operations handoffs are inconsistent, define what information operations needs and when.
- If forecasting relies on manual updates, identify which teams own the inputs and how often they need to refresh them.
Then explain the reason for change in plain language: what is getting in the way today, what the new process will improve, and what will be different in someone’s role. Be candid about what is still undecided.
This is also where leaders need to agree on the behaviors they will model. If you ask employees to use a new approval flow but executives continue to bypass it, your team gets a clear message about which process really matters.
Give employees a role in designing the change
People are more likely to raise practical concerns when they have a way to influence the solution. Include representatives from the teams that will use the system in process mapping, testing, and rollout planning.
Ask them:
- Where does the current process slow down or create rework?
- What information do you need to complete this step?
- What could cause someone to go back to the old workaround?
- What would make the new process easier to follow?
This isn’t a requirement to let every preference determine the design. It’s a way to uncover real constraints early, improve the process, and build shared ownership.
Research from Prosci’s change management best practices highlights employee engagement and participation as important contributors to change success. For a smaller business, that can be a focused group of frontline users and managers, not a large transformation office.
Make training practical and role-specific
A login guide isn’t enough. People need to practice the tasks they’ll perform in real work: entering a purchase request, routing an approval, updating an order, or reviewing a dashboard.
Use short sessions, realistic scenarios, simple job aids, and time to ask questions. Train managers and team leads to coach the new process, too. They are often the first people employees approach when something feels unclear.
A good rollout also makes room for different learning needs. Some employees will be comfortable exploring a new system; others may need more guided practice. Treat questions as useful feedback, not evidence that someone is resisting change.
A practical 90-day change rollout
A 90-day plan can give your team structure without forcing every business into the same implementation calendar. Adjust the pace to the number of processes and people involved.
Days 1–30: Align and prepare
- Choose the business outcomes the change needs to support.
- Map affected roles, current workflows, and likely pressure points.
- Select frontline users and managers to help review the future process.
- Set the communication cadence and explain what is changing, and why.
- Capture baseline measures, such as approval time, reporting delays, or close duration.
Days 31–60: Test and build capability
- Configure and test the workflow with representative users.
- Run role-based training using realistic scenarios.
- Invite employees to flag confusing steps and recurring issues.
- Identify super-users who can provide peer support.
- Confirm that managers know how to reinforce the process and escalate problems.
Days 61–90: Launch and reinforce
- Roll out in a controlled sequence, with support available during the transition.
- Review adoption and operational results at least weekly.
- Fix process issues, data problems, and training gaps promptly.
- Share progress and recognize teams demonstrating the new habits.
- At day 90, decide what needs further coaching, refinement, or expansion.
A launch date is a milestone, not proof that change has taken hold.
Measure adoption, not just activity
Performance dashboards for business can help leaders see where the rollout is working and where employees need support. But a login count or training attendance figure alone can give a misleading picture.
Track a small set of measures across three levels:
Use: Are people completing the required workflow in the new system? Are requests, orders, or updates still being handled in spreadsheets or side channels?
Proficiency: Are transactions accurate? How often do steps need to be corrected? Are task completion times improving? Which questions or support requests keep coming up?
Business impact: Are approval times, reporting delays, close duration, forecast accuracy, or inventory errors moving in the right direction?
Set a baseline before rollout so you can compare results. Review measures regularly and use them to remove friction, not to shame employees for struggling with an unfamiliar process. Prosci recommends looking at speed of adoption, ultimate utilization, and proficiency, alongside the business outcomes the change is meant to support.
Handle objections with clarity and respect
“We don’t have time for this.”
Acknowledge the workload. Then explain what time or rework the change is intended to reduce, and plan training around operational demands. Don’t pretend implementation takes no time.
“The old process works.”
Ask what “works” means. It may work for one person while creating delays or risk elsewhere. Compare the current process with the proposed one using specific examples.
“This is too expensive.”
Consider the full cost of current workarounds: repeated data entry, delayed decisions, errors, and dependence on a few key people. Make the business case with realistic assumptions, not promised returns.
“We’ll do it later.”
Later can mean more growth layered onto processes already under strain. You don’t need to change everything at once, but you do need a clear first step and a decision about what the business can’t afford to leave unresolved.
Make the new system part of how you operate
Sustainable change isn’t a one-off project. It becomes part of leadership routines: managers review the right measures, teams raise blockers early, and leaders reinforce agreed processes consistently.
That is the connection between Leadership & Accountability and Culture & Engagement. Accountability clarifies ownership; engagement helps people understand the purpose and participate in improving how work gets done. Brown Paper Analytics’ Leadership & Accountability approach and change management support focus on making expectations, adoption, and follow-through visible.
ERP and dashboards are essential infrastructure for scaling, not optional software upgrades. But the system alone won’t create a stronger operating model. Your people, processes, and leadership habits have to move with it.
Choose your next step
If your business is preparing for an ERP rollout, new dashboards, or approval workflows, start by assessing readiness: where work gets stuck, who the change affects, and what should improve first.
Book a discovery call with Brown Paper Analytics to discuss an ERP readiness assessment or process-to-system roadmap for your next stage of growth.