The 90-day operations reset: a field guide
A structured way to find and remove the friction that is quietly eating your margin, without pausing the business to do it.
Most operational problems in growing businesses are not dramatic. They are small, repeated and invisible from the top: a quote that takes three days because it needs two approvals, a job that is scheduled twice because two spreadsheets disagree, an invoice that goes out a week late because someone was on holiday. Individually they cost minutes. Together they cost margin, morale and customers.
The following 90-day outline is a planning framework for examining these problems in three phases. It is not a promise that every operations project will fit that timetable.
Days 1–30: See the work
Begin by mapping how work actually flows, rather than relying only on the formal process. Talk to the people doing the work, trace a selection of recent jobs from enquiry to completion, and record the hand-offs, waiting and workarounds.
The output is a shared map that the people doing the work can review and correct. Record the friction points it reveals without assuming a particular number or scale of improvement.
Days 31–60: Fix the top five
Not all friction is equal. Compare the identified issues by frequency, impact and effort to address them. Use that comparison to select a manageable set of priorities and review them with the people involved.
Each fix gets an owner, a deadline and a one-page standard operating procedure. Fixes that require new software are deferred to phase three unless the software already exists in the business.
Days 61–90: Make it stick
A process improvement that lives in one person's head is a process improvement with a shelf life. The final month is about embedding: a short weekly operations review, a visible measure for each fixed process, and a simple mechanism for the team to log the next friction points as they find them.
Outputs to work towards
- A baseline for lead time on the selected process, so any subsequent change can be assessed
- A documented operating model the business did not previously have
- A prioritised backlog for the next 90 days, owned by the team rather than a consultant
Build a useful process record
Choose a real example
Use a recent job or order, rather than describing only the ideal process.
Separate work from waiting
Record where someone actively worked on the item and where it waited for information, capacity or a decision.
Record the hand-offs
Note what information moves with the work and whether the next person has what they need.
Review the map together
Ask the people involved to correct missing steps or exceptions before choosing a change.