Management Consultant

How do you find the root cause of an operational problem when the client has already told you what they think it is?

I treat the client's explanation as one hypothesis among several and go look at the process in person before accepting it. Walking the floor, pulling the transaction data and talking to the people who do the work usually surfaces a handoff or a measurement issue that nobody in the leadership meeting had seen, and that is often where the problem lives.

How do you decide which stakeholders need to be involved in shaping a recommendation versus only informed of it?

I map everyone who can block the change or has to live with it, then ask which of them hold information or authority the recommendation depends on. Those people are involved early, because a recommendation they helped shape is one they will defend later. Everyone else gets a clear, timely briefing so the change does not surprise them.

How do you build an implementation plan that survives contact with a client organization that is already stretched thin?

I sequence the plan so the first wave delivers something visible within a quarter and needs the fewest people, which earns the goodwill for the harder waves. I also name the specific client staff for each workstream and check their current availability, because a plan built on unnamed capacity is a plan that will slip on day one.

How do you quantify the impact of an operational fix before the client has committed resources to it?

I build the estimate from the client's own numbers, like cycle times, error rates or headcount, and apply conservative improvement assumptions that I can defend with a comparable case. I show the range rather than a single figure, because an honest range survives scrutiny from the finance team while a point estimate invites an argument about decimals.