Comparing two ways of handling incoming requests

Compare two request routes on the same job: track each from arrival to a usable response. Define eligible requests, keep urgent and restricted work on its approved route, and examine ownership, resolution, quality and effort. A faster acknowledgement is only one part of the result.

Define the routes

Consider direct assignment and a shared queue with a rotating intake owner. Under direct assignment, the requester chooses an owner. Under the shared route, one person reviews eligible requests and assigns them, with the intake role passed between designated owners.

Set the rotation schedule and handover process before the trial: specify how open requests and relevant context are passed on, and who provides cover when the scheduled owner is unavailable. These are possible trial designs; neither is inherently better.

Write the rules a requester and worker would follow: where a request arrives, what information it must include, who acknowledges it, sets its priority, assigns the work and checks completion, and how a misdirected request is recovered. Keep required service standards, approvals and the completion rule consistent across both routes.

Exclude work that cannot safely enter either route, such as a live issue requiring an established incident response or information needing restricted access. Tell requesters which route applies during the trial so they do not send the same request twice.

Trial Design for Request Handling Routes

Make the comparison useful

Choose comparable request types and a review period before starting. Inspect the existing record for volume, work mix, time to an owner, time to a usable answer, reassignments and unresolved items. Record material changes in demand or staffing during the trial.

If similar teams use different routes at the same time, compare their starting conditions as well as their results. If one team tries the routes in successive periods, changing demand or deadlines may explain part of the difference. Two totals beside each other do not make a controlled test.

For the shared route, record which intake owner handled each request, any handover between owners, and whether the assignment decision changed after handover. Compare decisions across owners using the same rules, and note any gaps in cover.

Ask people using each route what caused waiting. A shared queue may offer a clear entry point but depend heavily on its intake owner. Direct assignment may suit familiar work but leave an unfamiliar requester guessing. Check these possibilities against actual cases.

Choose a route or revise the design

At review, inspect comparable cases rather than selecting the route with the best single average. Check whether one route moved effort from requesters to a coordinator, or helped ordinary requests while leaving complex ones unowned. Include people receiving the completed work.

Keep the route that handles the intended request types with acceptable quality, cover and effort. If a shared queue depends on one person, establish cover before extending it. If direct assignment works for specialist requests but not general enquiries, test a clearly defined split route. Record the rule that applies next, its owner and the next review point.

Key Outcomes from Route Comparison Trial