Hire an operations consultant when a recurring problem is affecting performance, crosses team boundaries and needs focused diagnosis or implementation support that the organisation cannot provide alongside day-to-day work.
Do not hire one simply because operations feel busy. First identify the outcome that is at risk, the part of the operating system that may be causing it and who inside the organisation will own the result.
The quickest test
Outside support is usually worth considering when all four statements are true:
- The problem is affecting a business outcome. It is slowing delivery, increasing rework, weakening service or preventing leaders from making reliable decisions.
- The cause is not contained within one role. The issue involves handovers, information, priorities or decisions across several people or teams.
- Previous fixes have not held. A new spreadsheet, meeting or instruction produced temporary movement but the problem returned.
- There is an internal sponsor. Someone with authority can provide access, make decisions and own the new setup after the consultant leaves.
If the fourth condition is missing, commissioning a consultant will not create it. External support can make the problem and choices clearer. It cannot replace leadership ownership.
Seven signs that the problem may justify outside help
1. Growth has made ordinary work harder
Processes that worked through informal conversations can break when volume, headcount or locations increase. Work starts waiting between teams. Exceptions become normal. Senior people are pulled into routine decisions because nobody has redesigned the way work should move at the new scale.
An operations consultant can follow the real workflow, identify where the old model has reached its limit and build a simpler process with explicit ownership.
2. Leaders cannot get one reliable view of performance
Different teams use different definitions. Reports arrive late. Management meetings spend more time debating the number than deciding what to do about it.
This is not always a dashboard problem. The underlying issue may be unclear measures, fragmented data ownership or a reporting cycle that has accumulated too many manual steps. The right engagement starts with the decisions leaders need to make, then works backwards to the information and routine required.
3. The same operational issue keeps returning
A recurring problem often survives because each team fixes the part it can see. One team adds a check. Another creates a tracker. A third adds an approval. Local fixes can make the end-to-end process slower without removing the original cause.
Independent diagnosis is useful when the organisation needs somebody to follow the whole route and test assumptions that have become normal.
4. Too many decisions depend on one person
When the same founder, director or specialist approves every exception, the problem is not only workload. Decision rights, thresholds or information may be missing.
The useful output is not a generic responsibility chart. It is a practical decision model that states who can decide, what evidence they need and when the issue must be escalated.
5. A technology change is exposing weak processes
Replacing a system does not resolve unclear ownership or inconsistent ways of working. It can make those weaknesses more expensive.
Operations support is valuable before or during implementation when the organisation needs to agree the workflow, roles, controls and measures that the technology must support. If the process is not ready, start with the AI and automation readiness test before choosing another tool.
6. A priority change has no credible route into daily work
Leadership may agree the direction while teams continue to work through old priorities, reporting and routines. This is where operational design and change adoption meet.
The consultant should translate the intended change into specific processes, decisions, measures and leadership behaviours. Communications and training may support the change, but they cannot substitute for that operating detail.
7. The work is important, but nobody can own it alongside their role
An internal leader may understand the problem and still lack the capacity to diagnose it, coordinate several teams and support implementation. That is a legitimate reason to use temporary specialist support.
The test is whether the engagement creates capacity for a defined outcome. It should not quietly become permanent responsibility without a conscious decision.
When not to hire an operations consultant
Do not commission an operations project if:
- the leadership team has not agreed what it is trying to achieve
- the issue is primarily unresolved behaviour or performance by one person
- the organisation wants validation for a solution it has already chosen
- nobody can provide access to the people, work and data involved
- there is no capacity to test or adopt a new setup
- the real need is continuing executive ownership rather than a defined improvement
The final point matters. If the organisation needs somebody to lead operations month after month, compare a consultant with a fractional COO. A consultant is a better fit when the goal is to diagnose and improve a specific operating system that an internal owner can then run.
Decide whether to keep the work internal
Use the internal team when the problem is well defined, sits within one area and the team has the expertise, authority and time to fix it. External support adds less value when the solution is clear and implementation does not cross organisational boundaries.
Consider a consultant when one or more of these are missing:
| Question | Keep it internal when | Consider outside support when |
|---|---|---|
| Is the cause clear? | Evidence points to a defined constraint | Teams disagree or the problem moves between functions |
| Is there capacity? | A named owner has protected time | The work repeatedly loses priority to daily operations |
| Is specialist design needed? | The team has solved a similar issue | The process, reporting or governance model needs redesign |
| Is neutrality important? | One team can resolve the issue fairly | Priorities or responsibilities are contested |
| Can implementation be owned? | The team can test and embed the change | Coordination or adoption needs focused support |
Scope the first engagement around a decision
Avoid starting with a long list of activities. A useful initial brief can fit on one page:
- Problem: what is happening and where it is visible
- Consequence: which outcome, customer, cost or decision is affected
- Boundary: which workflow, teams or reporting cycle is in scope
- Decision: what leadership must be able to decide at the end of the diagnosis
- Operating output: what process, ownership, reporting or governance should exist
- Measure: how the organisation will know the change is helping
- Internal owner: who will sponsor the work and own the result
The UK Government’s Consultancy Playbook is written for public procurement, but two principles transfer well to any organisation: define outcomes and value clearly, then plan knowledge and skills transfer from the start.
What a credible first month should produce
The exact output depends on the problem, but a focused first phase should normally leave the client with:
- an evidence-based description of the current problem
- a view of the end-to-end workflow, including exceptions and informal workarounds
- agreement on the main causes rather than a list of symptoms
- a small number of prioritised changes with owners
- a baseline and measures for the outcome
- a clear decision on whether to implement internally or commission further support
Be cautious if the first phase only produces interviews, workshops and a broad transformation roadmap. Activity is not the same as a diagnosis.
Questions to ask before appointing anyone
Ask the consultant:
- What would you need to observe, not just be told?
- How will you distinguish the cause from the symptoms?
- What time and access will you need from our team?
- What will be usable at the end of the first phase?
- How will you test the proposed change in real work?
- What will the internal owner need to maintain?
- What evidence would make you recommend no further consulting work?
The answers should reveal a method, not only confidence.
Where LUKiN fits
LUKiN works with organisations where the direction is broadly understood but execution has become unreliable. The problem usually sits in processes, management reporting, project governance or change adoption.
The work combines diagnosis with practical design and implementation. In one engagement with a growing service organisation, LUKiN simplified more than 18 core processes, clarified responsibilities across six teams and established one shared operating rhythm. Read the operating model case study for the problem, approach and reported result.
If the operating cause is not yet clear, the Operational Performance Diagnostic is the most useful starting point. If the constraint is already defined, explore process improvement consulting.