Participant journey
Clarify invitation, sign-in, plan set-up, monthly action, progress, export, and program completion.
Purpose
Product Definition in plain language
Turn a strong prototype into an approved, buildable, supportable release plan. This is where the Foundation decides what the first release must accomplish for participants—and what should wait.
Candidate scope
What this phase could include
- Participant journey from access through monthly use and completion
- Program rules, participant-facing wording, and success definition
- Data inventory: what to collect, why it is needed, and who may see it
- Roles and permissions for participant and administrator
- Launch / Next / Later classification for every identified capability
- Architecture, backup, restore, independent testing, and release acceptance plan
Working detail
What we would define together.
Data and privacy
Collect only planning-level information needed for coaching. Avoid account credentials, account numbers, Social Security numbers, documents, and similar high-risk data.
Launch definition
Create a practical, written feature list and exclusions list that both sides can use to prevent accidental scope expansion.
Acceptance criteria
Define the tests and observable conditions that must be met before the release is accepted and deployed.