Turnaround and disruption an ops engagement realistically involves

You're three weeks into a deal your operations team said would collapse without changes. Your founder is asking when things get better. Your consultant is asking for another fortnight to map workflows. You're wondering if you've hired someone to rubber-stamp what you already know or if the slowness is part of actually fixing it.

This is when most businesses hit the real question: how fast should turnaround actually happen?

Speed isn't the measure—comprehension is

A consultant who promises to fix your operations in two weeks is either not looking carefully or selling you a surface wash. Real disruption takes time because the things slowing you down are usually invisible until someone sits in the noise and traces them. That tracing phase—which feels like stalling—is where the leverage lives.

What matters is *active progress you can see*, not arrival at a finish line. You should see diagrams by week two, a list of quick wins by week three, and the shape of the bigger changes by week four. If your consultant is still interviewing people and asking "why do you do it that way?" beyond three weeks, either the business is genuinely tangled or the engagement isn't moving. Ask for a progress sync; don't assume silence means depth.

What actually changes the timeline

The speed of an ops overhaul hinges on factors mostly outside the consultant's control. If your team is busy fighting fires, real change gets squeezed into margins. If the people who own each process are reluctant or sceptical, implementation stalls. If data lives in your founder's head or scattered across spreadsheets, mapping takes longer.

The consultant's pace depends on access. Can they shadow a full day of operations? Can they interview the people running each function without that person rescheduling twice? Do you have a single point of contact who unblocks questions, or does every query need sign-off? Consultant skill matters, but your internal friction matters more.

One often-missed factor: how many process layers you're trying to fix at once. Trying to overhaul sales *and* ops *and* finance simultaneously is slower than picking one, fixing it hard, and letting the wins fund the next phase. Scope creep doesn't accelerate change; it spreads effort thin.

How to ask for urgency without breaking the work

If you genuinely need fast movement, don't ask for speed—ask for priority. Tell your consultant which process is actively damaging the business right now. Give them that one first. Make sure your team knows this engagement is a working priority, not something people fit in around regular jobs. Create a small steering group that meets weekly so blockers get surfaced and cleared immediately.

Be specific about your deadline if it exists. "We need the sales process fixed before Q3 contracts" is actionable. "This is urgent" is not. Urgency without a real constraint often leads to consultants cutting corners or teams cutting the engagement short before changes stick.

Payment structures can also matter. If your consultant is charging by the day, they have no incentive to move fast. If the fee hinges partly on delivery of specific milestones by agreed dates, there's alignment. You don't need to be adversarial about this—it's fair to ask how their model encourages pace, and to expect a timeline before you commit.

When change gets stalled—and how to tell

A realistic engagement has phases: discovery (usually two to three weeks), diagnosis (one week), planning (one week), and implementation support (whatever length you've agreed). Each phase should produce something you can see—a report, a decision, a pilot, a new process map.

If weeks five and six bring no visible output, ask directly. Either the engagement has hit a genuine complexity you didn't know about—which your consultant should explain—or the work has lost momentum. Neither means you've hired wrong necessarily, but both mean you need to recalibrate: extend the timeline, narrow the scope, or both.

The consultants worth keeping are those who hit their own milestones, flag risks early, and don't hide behind jargon when you ask "where are we?" Finding someone with a track record of actually moving ops needn't be slow—Strove lets you compare consultants and read what they've delivered before you commit.