Enter overview here
Enter problem statment here
Enter desired user outcomes here
Enter undesired user outcomes here
Enter desired business outcomes here
Enter info here
Enter info here
- What data (qual or quant) will you look at to understand if your initial set of functionality is meeting your desired user and business outcomes, and not bringing about the undesired outcomes?
- What are the most important metrics that track with this product/initiative's success?
- Include links to Domo or Google Analytics Dashboards/Reports
- Limit 5-6 KPIs per product_
| Category | Ease of use | Service completion | Trust/Satisfaction | Health |
|---|---|---|---|---|
| KPI | ||||
| KPI |
- Baseline values for those most critical metrics. These may come from other systems other than VA.gov e.g. eBenefits.
What are the measurable targets you're aiming for that delivers value for Veterans?
- Objective:
- Key result:
- Key result:
Assumptions here
-
What are you going to build now, and why have you decided to start there?
-
Why this solution / approach over other solutions / approaches?
-
What have you explicitly decided to not include in this initial set of functionality, and why?
-
How will the solution / approach evolve after this initial build (knowing that this will likely change as you learn from users along the way)?
Include initiatives (iterations, new features, etc.) to improve this product. See the Initiative Brief Template
- N/A
- Target Launch Date
- tbd
- Actual Launch Date
- tbd
- What date will you evaluate impact after launch (and when do you expect to have your Impact Review)?
- tbd
| Decision | Date | Participants |
|---|---|---|
- Team Name: Sitewide Public Websites
- GitHub Label: sitewide-public-websites
- Slack channel: #Sitewide-Public-Websites
- People:
- OCTO-DE Leads: Michelle Middaugh & Danielle Thierry
- OCTO-DE IA: Mikki Northuis
- PM: Fran Cross (A6)
- DM: Jill Adams (A6)
- Engineering:
- Design:
- Research: Cindy Merrill
- VEO: