How to brief a process-improvement firm so the work survives the handoff

Picture the first week after a process-improvement engagement ends. An invoice arrives without the usual reference. The process diagram has a box for “approve invoice,” but the person doing the work cannot tell who should investigate the missing information or when the invoice should be returned.

The diagram may be accurate for ordinary cases. The operating procedure is unfinished.

A better brief defines the work the company must be able to carry out after the consultant leaves. That includes the difficult handoffs, the exceptions and the person allowed to change the process. Use the invoice example below as an illustrative commissioning exercise; it is not a case study or a claim about savings.

Decide which part of improvement you are buying

Start by asking a firm to identify the boundary of its offer. Does it diagnose the problem, design a future process, implement the changes, train the team or remain involved while the new routine settles?

Centric Consulting separates documentation, prioritization, focused improvement and implementation in its service descriptions. That distinction is helpful when reading a proposal: an analysis engagement and an implementation engagement can both be legitimate, while leaving very different amounts of work with the client.

Look for the organizational work around the process, too. Credera lists roles, metrics and vendor expectations alongside process optimization. Leanscape describes improvement work with managers and the internal routines needed to continue after its team steps back.

These are examples of advertised scope, not proof of results on your project. Ask the proposed delivery lead to translate their offer into the outputs your team will receive and the work your own employees must perform.

Give the engagement a beginning and an end

“Improve finance operations” is too broad for a useful first assignment. For the fictional invoice process, a workable boundary might begin when an invoice reaches the company’s designated channel and end when it is either approved for the next step or returned with a documented reason.

The boundary excludes later payment execution and wider accounting policy decisions. Those may matter to the business, but including them silently would make this pilot harder to compare, staff and accept.

Ask the consultant to inspect how the work currently happens before designing the replacement. Supply an authorized, appropriately handled sample of ordinary and exceptional cases. Include examples that waited, moved backward or required someone to find information outside the formal workflow. A meeting about the official procedure alone may miss the work people perform to keep it moving.

Have the firm distinguish a recorded observation from a proposed explanation. “This case waited for the approver to return” and “absence coverage is causing most delays” are different claims. The second needs more support. Keeping that distinction visible helps the company avoid redesigning around an interesting anecdote.

Name the owner who can settle an exception

An executive sponsor can authorize the project, but someone closer to the work must maintain the resulting process. Name an internal owner who can resolve ambiguous cases, approve updates and bring other departments into a decision.

In the invoice example, that owner should settle questions such as who investigates a missing reference, who substitutes for an absent approver, and what information must accompany a returned item. The consultant can propose a design; the appropriate company decision makers must authorize the rules.

Record disagreements while the project is still active. If operations wants a faster route and finance needs another check, the handoff should contain the agreed decision and its reason. A clean diagram that conceals an unresolved disagreement will not settle it later.

Ask the consultant to maintain a short decision log. It should explain what changed, who approved it and which open questions remain. That gives the next owner enough context to revise the process deliberately.

Pilot a complete slice of the work

Choose a pilot that reaches the defined end of the process. For the illustrative invoice engagement, that could mean one team’s incoming invoices, with an agreed route for exceptions that cannot be handled inside the pilot. Avoid calling a new submission form a completed improvement when approval and return handling remain unchanged.

Write down what stays constant during the pilot and which changes need explicit approval. If the team changes the entry rules, software and staffing at the same time, interpreting the result becomes harder. The consultant should explain the tradeoff and help the owner keep a record of material changes.

Agree how the company will observe the pilot. Useful records might include arrival and completion times, returned items, missing information and work reopened after an apparent finish. Define what each record means, where it comes from and who reviews it. A shorter elapsed time has limited value if the team has simply stopped recording difficult cases.

Do not set an arbitrary improvement percentage to make the brief sound commercial. First establish which result matters, which cases are included and which checks protect quality. The initial pilot can earn its value by exposing a workable design and the remaining constraints, even before the company is ready to claim a sustained benefit.

Accept the operating system, not just its presentation

Use a practical acceptance worksheet at the final review. These are proposed checks for the fictional pilot; adapt them to your process.

Use staff practice as part of delivery. Ask the consultant to watch an operator use the procedure, note where it breaks down and revise it with the team. A presentation can introduce the process; it does not establish that the instructions are usable.

Make the last meeting an operating review

Agree the support period and escalation route for problems discovered after handoff. Keep open items separate from accepted deliverables, with an owner and a next action for each. If some implementation work is excluded, make that exclusion visible before the engagement closes.

At the final meeting, put the actual internal owner in charge. Have that person explain the latest pilot result, describe an exception and identify the next change they would consider. The consultant can fill gaps, but the company should be able to run the discussion.

That is a concrete finish line for a process-improvement purchase: people can do the work, explain the rules and maintain the process. The documents are useful because they support that capability.

Sources

• Centric Consulting: business process improvement services.
• Credera: operational excellence.
• Leanscape: consulting approach and engagement models.