Digital product pilot test plan

# Pilot brief · [product alias]

## Decision and scope
- Decision this pilot can inform: [one practical uncertainty]
- Decision owner and date needed: [ ]
- Product version, build reference, device, and test environment: [ ]
- Intended buyer task and evidence behind that choice: [ ]
- Product areas included / explicitly excluded: [ ]
- Task(s) and observable completion checks: [link to task rows]
- What would cause a hold or stop: [ ]

## Participant fit and invitation
- Relevant task experience required: [describe behavior, not sensitive traits]
- Recruitment route and why this person is a useful fit: [ ]
- Conflicts or prior involvement that affect interpretation: [ ]
- Invitation states purpose, time, voluntary nature, and stop option: [ ]
- Incentive, timing, and terms are the same regardless of opinion or result: [ ]
- Accessibility and participation adjustments offered: [ask what is useful; do not request a diagnosis]

## Consent, evidence, and data plan
- Notice and approved consent process reference: [ ]
- Recording: off by default; separate permission and retention rule if applicable: [ ]
- Minimal observations to keep and reason: [ ]
- Approved restricted evidence location and access owner: [ ]
- Neutral participant alias used in this workspace: [ ]
- Data access, removal date, and person verifying removal: [ ]
- Real personal, client, account, and payment data excluded: [ ]

## Interpretation boundary
- Number of participants and why: [ ]
- How recruitment and task wording limit the conclusion: [ ]
- Evidence that would change the release decision: [ ]
- Claims this pilot cannot support, including demand or sales: [ ]