You have been told to move fast and to go slow, probably by the same adviser. Both are right, and neither is a plan: momentum matters and uncertainty is expensive, but you do not yet understand what you bought. The mistake is applying one speed to everything.
Some changes should happen on day one. Some should wait a year. A few should never happen. The art is sorting them, and having the discipline to hold the ones that should wait. For the broader leadership picture, turn to leading the change after an acquisition.
The risk runs both ways
Going slow has a price. Good people want to know where they stand. Dual systems cost money. Problems that need fixing get worse. A buyer who changes nothing for a year may find that the integration never starts.
Going fast has a price too. Every change is a withdrawal from the trust you have with the people and customers. Make too many at once and the account runs dry. The performance dip that follows change gets deeper when changes pile up, and the people you most need begin to look elsewhere.
Sort every change by two questions
For each proposed change, ask how much it helps if done now, and how much damage it could do if done badly. High benefit and low risk goes first. High benefit and high risk needs a plan. Low benefit and high risk waits, or never happens. Low benefit and low risk can be done whenever someone has time.
Also ask what depends on it. A change that blocks others goes earlier. A change that depends on others waits for them.
What should move immediately
Things that protect the business: payroll, banking, insurance, safety, legal compliance, and access to systems. Communication to employees and customers. Retention of the critical few. Control of cash. These are not improvements. They are the minimum for a safe start, and the first days of the 100 day integration plan lay them out.
What should wait: pay structure, titles, systems, branding, pricing, and organization. Make those changes after you understand how the business works.
Signals to slow down or speed up
Slow down if you see departures among the people you meant to keep, complaints from key customers, a drop in service levels, or confusion on the floor about who decides. Speed up if people are asking for direction, if parallel systems are costing you accuracy, or if the delay itself is creating rumors.
Check these every two weeks with a short list and honest answers. Pace is not a decision you make once. It is a dial you adjust. For the communication of hard decisions, see who to tell about cuts, and when. For the case where their system is simply better, read when their system is better than yours. I would not make more than a few visible changes in the same month, and I would explain each one.
Decision table: do it now, plan it, or wait
Apply to every proposed change. Write the answer on the tracker.
| Question | If yes, it points to | If no, it points to |
|---|---|---|
| Does it protect the business: payroll, cash, compliance, safety? | Do it now | It is an improvement. Sort it by benefit and risk below |
| Does it threaten the people or customers you must keep? | Wait, or redesign it with their input | Check what depends on it |
| Does a lot depend on it? | Plan it carefully and sequence it early | Check benefit and risk |
| Is the benefit large and the risk low? | Do it in the first hundred days | Check the last row before you commit |
| Is the benefit small or the risk unclear? | Wait for evidence, or drop it | Schedule it in the normal rhythm |
A thirty, ninety, three hundred sixty five view
Use three horizons. In the first thirty days, protect: cash, payroll, safety, communication, and the critical few. By day ninety, stabilize and learn: map the customers, the dependencies, the real processes, and the true profit. Within the first year, improve: pricing, systems, structure, and synergies, in the order the evidence supports.
Write each proposed change into one of the three buckets and ask someone to challenge the placement. The most common error is putting a year one change into the first thirty days because it is easy to start. The second most common is leaving a safety or cash item until later because it feels dull. Check both.
A rule I use
Never make more than a few visible changes in the same month. People can absorb a couple of changes. They cannot absorb ten. Pick the three that matter most, explain them, and do them well. Add the next set when the first is settled.
The order matters: protect the business, then improve it, then drive growth. Speed is not a virtue by itself.
Get the 100 day integration tracker
The tracker puts an owner, a date, and a status on every integration task from pre-close to day 100, so decisions like this one get made on purpose and followed up.
One email with the download, and occasional Building Results notes. Opt out any time.
Questions
How quickly should you make changes after acquiring a business?
Set the pace change by change. Do the changes that protect the business immediately, such as payroll, cash control, compliance, and communication. Wait on pay structure, titles, systems, branding, and organization until you understand how the business works. Slow down if key people or customers show strain, and limit visible changes to a few at a time.
What should I never change in the first month?
Anything that touches the pay or role of the critical few before you understand it, and anything that touches how top customers are served.
How do I know if I am moving too fast?
Departures, complaints from key customers, falling service levels, and confusion about who decides.
Is it ever right to wait a full year?
For some changes, yes, especially systems and brand. Set a date so waiting does not become never.