Public Digital Service Discovery Assessment
Synthesize citizen research, legal mandates, and operational gaps into an actionable public sector service discovery report.
Use this template when concluding the discovery phase for a citizen-facing government service. It translates user feedback, accessibility rules, and statutory constraints into a clear MVP product roadmap.
Role: Principal Civic Tech Product Manager with 15+ years leading digital service transformations in government agencies.
Context
- Sponsoring Agency: {{agency_name}}
- Primary Citizen Cohort: {{citizen_cohort}}
- Current Operational Bottleneck: {{current_service_bottleneck}}
- Legal & Statutory Mandate: {{statutory_mandate}}
- Target Accessibility Standards: {{accessibility_standards}}
- Target Implementation Horizon: {{pilot_timeline}}
Task
Synthesize citizen research findings, policy constraints, and operational bottlenecks into a comprehensive discovery report that defines the minimum viable product (MVP) scope, citizen journey baseline, and pilot release criteria for {{agency_name}}.
Method
- Analyze {{citizen_cohort}} pain points and map the end-to-end user journey against {{current_service_bottleneck}}.
- Cross-reference proposed digital interventions against {{statutory_mandate}} to confirm regulatory compliance.
- Evaluate technical feasibility and offline accessibility needs under {{accessibility_standards}}.
- Formulate the core problem statement and draft quantifiable public value metrics.
- Define the MVP feature backlog, separating essential citizen self-service workflows from deferred enhancements.
- Identify delivery risks across inter-agency data sharing, digital literacy barriers, and legacy system integration.
- Construct a phased release plan aligned with the target window of {{pilot_timeline}}.
Constraints
- MUST adhere strictly to {{accessibility_standards}} without assuming uniform high-speed broadband access.
- MUST NOT introduce operational workflows that require citizen paper filing unless legally mandated by {{statutory_mandate}}.
- Recommendations must prioritize equitable access for underserved members of {{citizen_cohort}}.
- Keep all budget and timeline estimations bounded strictly within {{pilot_timeline}}.
Output format
Deliver a formal structured report containing the following exact sections:
- Executive Summary (max 200 words)
- Citizen Journey & Problem Statement
- Regulatory & Accessibility Requirements Matrix
- MVP Scope Definition & Feature Prioritization
- Risk Assessment & Mitigation Plan
- Pilot Implementation Roadmap Total report length must be between 900 and 1400 words.
Self-review
- Confirm {{agency_name}}, {{citizen_cohort}}, and {{statutory_mandate}} are explicitly addressed in the problem statement.
- Verify that every recommended MVP feature maps directly to resolving {{current_service_bottleneck}}.
- Ensure all accessibility constraints under {{accessibility_standards}} are incorporated into acceptance criteria.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.