The project asks for a user representative, and the same enthusiastic colleague attends every session. User acceptance testing needs participants who cover the intended operational tasks and exceptions, with an appropriate owner authorised to accept the result. One available person may not represent every role that must use it.
PMI discusses acceptance criteria in requirements work. This article focuses on who supplies the operational evidence and how their participation is arranged, rather than writing another acceptance-criteria template.
Photo by Microsoft Edge on Unsplash.
Map tasks before inviting people
List the work the proposed solution must support. Include routine completion, missing information, corrections, handoffs and relevant supervision. Identify which roles understand those situations from actual work.
Avoid choosing participants solely by seniority or technical confidence. A manager may know the intended outcome while a coordinator knows the daily exceptions. Both can contribute different evidence without either pretending to cover the whole service.
Use a participation coverage map
For each material task or scenario, capture:
Operational role and relevant experience.
Participant and backup.
Suitable authorised example or test material.
Preparation, session and follow-up time required.
Access and instruction needed.
Evidence the participant will provide.
Person authorised to assess and accept the result.
Confirm availability with the operational owner. An invitation does not create protected time or transfer responsibility for the participant's normal client work.
A hypothetical acceptance gap
A new booking process is tested by the project coordinator and a supplier. Normal bookings work. The operational team later finds that a rescheduled appointment requires a different approval and record update, a case neither participant usually handles.
A better participation plan includes the role managing reschedules and the owner of the approval rule. Their session checks the agreed scenario and records any defect or unresolved business decision. The sponsor can then judge the evidence against the intended use.
This does not mean every employee must attend every test. Select relevant coverage and explain which roles or scenarios remain untested.
Separate observation from acceptance authority
Participants report what happened, difficulties encountered and whether the agreed task could be completed. The authorised recipient decides acceptance under the governance. A participant's positive comment is not automatically formal sign-off.
Where users disagree, investigate whether the cause is a defect, an unclear requirement or different operating needs. Avoid deciding by whichever participant speaks most confidently. Record the question and the owner who can resolve it.
Prepare participation early enough to matter
Give people the current instructions, scope and purpose before the session. Explain how findings will be handled and when corrections will be rechecked. Include follow-up capacity so the first test is not the only realistic opportunity to obtain operational evidence.
The small-team project planning guide helps connect those sessions to dependencies and dates. For the connected task, read How to Write Project Acceptance Criteria People Can Actually Check. If user acceptance is planned around whoever happens to be free, discuss your project requirements.
