How to pilot a capacity increase while protecting quality

01

Define the pilot and comparison

Select one location, work type or team and define the change, start date, end date and owner. Describe what stays in the normal process, which cases are excluded and how urgent or unusual work will be handled. Tell the people receiving the output what is changing.

Record a baseline using the same definitions you plan to use during the pilot. Include completed work and turnaround time. Record corrections and customer issues as well. Note differences in demand or work complexity that could make the periods difficult to compare.

02

Set checks and decision rules

Agree who will inspect output, how samples will be selected and how failures will be recorded and corrected. Define a quality threshold and an escalation route appropriate to the work before the trial begins. For high-consequence work, use the approval and review procedures already required for that work.

Assign someone authority to pause the pilot if an agreed threshold is breached or an unexpected problem appears. Keep the previous process available where feasible and record open work so a pause does not leave requests without an owner.

03

Review results before expanding

Compare completed work and turnaround time with the baseline, then inspect corrections, customer feedback and downstream workload. Look at the number of items reviewed as well as any rate. A small sample or a change in the work mix may make the result uncertain.

Ask the people doing and receiving the work what failed and what took extra effort. Decide whether to extend the trial, revise it, stop it or expand it. Record the reasons, the person responsible and the next review date; continue the quality checks after any expansion.

For example, a team might try a revised intake form for one request type over a defined period. Before starting, it agrees who checks a sample, what constitutes a missing requirement and who can pause the trial. At review, it compares the number completed with corrections found and the time spent by the receiving team. If output rises but corrections or downstream delays also rise, investigate those failures before expanding the form.

Do not infer a permanent effect from a short trial with few items. If demand, staffing or the request mix changed during the trial, document the difference and consider another observation period. If the trial ends, assign every open request to a named owner and tell affected teams which process applies next.

04

Document the pilot decision

Write the pilot decision on one page before launch: the work included, baseline period, added volume, measures, review dates and the person who can stop the trial. Add a balancing measure for the team receiving the work, such as time spent correcting incomplete submissions. Review it even if the trial team reports faster output.