Use this checklist to plan one small pilot. Start with a task your staff can rehearse in a test account with invented records.
Start with a task staff can describe
[ ] Name the task, the staff member who does it and the person waiting for it.
[ ] Observe a recent instance using authorized records. Note where someone had to wait, repeat work or look elsewhere.
[ ] Find the system of record for the input and the result. Check whether the current tool can handle the task with a setting or a change to staff procedure.
[ ] Name the decision owner, the day-to-day reviewer, an alternate and the person who can turn off access.
Current task ______
Desired change and reason ______
Existing method and option to keep it ______
Check information, actions and access
[ ] List the smallest set of information the task needs and where each field comes from.
[ ] Ask the account administrator to show who can see the test records and how to turn access off.
[ ] Ask vendors to document access and limits for the actual account, including who can see inputs and how the firm can export and delete data.
[ ] Identify any write, send or status change, who approves it and where staff can confirm it happened.
[ ] Record any unresolved permissions, sources or routing questions.
Records and permissions to verify ______
Owner for unresolved questions ______
Compare the current method and the pilot
[ ] Define the current period, channel and count of eligible attempts. Keep missing or unmatched records visible.
[ ] Choose an observable result, such as complete callback requests over handoffs attempted. Decide what would count as good enough to keep the change.
[ ] Rehearse allowed actions, a blocked action, a missing recipient and an uncertain retry using invented records in a test environment.
[ ] Test the manual fallback, including who gets the work and how staff recover pending items.
[ ] Set a stop rule, a review date and a place to record the decision.
Baseline (count, denominator, dates) ______
Pilot measure and review date ______
Stop condition and fallback owner ______
Keep, revise or stop decision and reason ______
A fictional starting point
A trust firm’s intake lead suspects that callback requests wait in several inboxes. The team first traces a test request and identifies who should claim it. For the pilot, the team proposes a single review queue. It plans to compare complete handoffs and unresolved requests within the same channel and time periods. Staff rehearse the manual route before granting the assistant any access.
Use the result to decide whether to keep testing, change the setup, or stop the pilot. Note the account and settings you tested. For a worked example, read the software handoff article.