Questions to ask before paying for a process review

A process review sounds clean: you'll pay someone to examine how you work, find problems, propose fixes. The reality is messier. You're inviting a stranger into your operations, relying on their judgment to spot what matters, and betting that their recommendations will actually move the needle. Before you sign and pay, you need to know whether you're hiring someone who'll ask the right questions, or someone who'll deliver a polished report that sounds urgent but doesn't fit your world.

The consultant's answers to your questions will tell you whether they understand your business or are applying a template. A good answer is specific, honest about trade-offs, and grounded in what they've learned about you. An evasive answer is vague, all-purpose, or pushes back on your constraints as if you don't know your own operation.

What problem are you actually here to solve?

Start by asking: what does success look like when this is done? Not in consultant-speak, but in your language. If they answer "improved efficiency" or "streamlined workflows", push back. Ask them to tell you what changes, and for whom.

A strong answer names the specific pain point: "You've told me customer orders are taking too long to fulfil, your team is stuck on manual data entry between systems, and you're losing repeat business because of delays. If we fix that, your fulfillment time drops from seven days to three, and your team has breathing room." Notice they've repeated *your* problem and tied the outcome to *your* metric.

An evasive answer sounds like: "We'll identify inefficiencies and create a roadmap for continuous improvement." Or worse, they tell you the problem you should care about instead of the one you named.

Next, ask: how much of this review is about diagnosing what's broken versus prescribing what you should buy or build? This matters because some consultants make their money on follow-up implementation or by recommending software they have relationships with. You're not hiring them to be a salesperson. A credible answer acknowledges the tension: "The review will show you options — some cost money, some are about reorganising what you already have. I'll be honest about both, and you'll decide what's worth doing."

Then ask: if we find out the biggest problem is that we need to hire someone or restructure the team, will you tell us, or will you find a process solution instead? This is where you learn if they're genuinely independent. A consultant who won't name staffing gaps as gaps is protecting their fee, not your business.

How will you actually understand our operation?

Many process reviews fail because the consultant never sees how things really work. Ask: who will you spend time with, and for how long? The answer should include your team doing the actual work — not just managers. If they say they'll interview leadership and review documents, that's a red flag. Processes live in what people actually do, the workarounds they've invented, the bottlenecks only they know exist.

A credible answer is concrete: "I'll spend two days here, I'll shadow a few people through their actual day, I'll ask your team what slows them down and where they improvise, and I'll look at the systems and paperwork together with the people using them."

Ask them: what will you do if we tell you something, but your observation says otherwise? The honest answer is "I'll ask more questions and work from what I see, not just what I'm told". This shows they know that people often don't realise what they're actually doing or why.

Finally, ask: when do I get to see drafts, and what happens if I think you've missed something? If they say the final report comes at the end and that's the deliverable, you're not getting partnership, you're getting a document. A better model gives you visibility along the way, space to correct misunderstandings, and a chance to push back before they've built their whole analysis on a faulty premise.

These questions are your filter. The consultant who answers them directly, admits what they don't yet know, and builds in feedback loops is the one most likely to produce a review that actually serves your business. The one who glosses over the details or keeps their process opaque is hoping you won't notice the gap between what they promised and what they deliver.

When you're ready to move forward with a consultant whose answers make sense, Strove's verified consultants in process and operations improvement have profiles showing their approach and past projects, so you can check how they've worked with similar businesses before you commit.