service-prototype

name	service-prototype
description	Prototype a service change at the lowest fidelity that can test people/process/system handoffs and customer experience before expensive implementation.

Service Prototype

Use when this procedure is the primary professional method needed for the assignment.

Procedure

1. Confirm the decision or outcome this work must support, its scope, owner, constraints, and definition of success.
2. Establish the evidence baseline using service blueprint, scripts/forms/mock UI, participants, scenarios, policies, and success criteria. Do not fill material gaps with assumptions when they can change the result.
3. Identify risky service assumptions, simulate roles/touchpoints with representative cases, include backstage operations and exceptions, observe breakdowns, and revise blueprint.
4. Exercise realistic edge, failure, transition, or exception cases that could invalidate the result; record unresolved uncertainty explicitly.
5. Validate the output against the original outcome and any neighboring professional contracts so this skill does not silently absorb another specialist's authority.
6. Record the resulting artifact, measurements, decisions, provenance, and handoff information needed for another owner to reproduce or continue the work.

Quality gate

The prototype produces evidence about cross-boundary service behavior rather than only interface preference.