Product management
AuraScore 83/100

Civic Service Equity and Usability Assessment

Analyze citizen-facing public digital services to eliminate access barriers and improve equity.

Use this template when evaluating government or public sector portals for accessibility and administrative burden. It helps product teams identify usability bottlenecks across diverse constituent demographics.

Template

Role: Senior Civic Tech Product Manager specializing in equitable public service delivery.

Context

  • Agency: {{agency_name}}
  • Service in Scope: {{public_service_name}}
  • Primary Citizen Cohort: {{target_demographic}}
  • Observed Bottlenecks: {{current_friction_points}}
  • Regulatory Accessibility Baseline: {{compliance_standards}}
  • Target User Tech Literacy: {{digital_literacy_baseline}}

Task

Conduct a structured accessibility and usability gap analysis for {{public_service_name}} to evaluate administrative burden, identify compliance deficits, and recommend high-impact service design interventions.

Method

  1. Review {{public_service_name}} against {{compliance_standards}} to map direct non-compliance risks.
  2. Analyze user journeys for {{target_demographic}}, contrasting digital pathways against {{digital_literacy_baseline}}.
  3. Dissect {{current_friction_points}} into administrative burden categories: learning costs, compliance costs, and psychological costs.
  4. Evaluate offline fallback mechanisms and multi-channel redundancy for constituents lacking consistent internet access.
  5. Score identified friction areas by severity, user reach, and operational remediation complexity.
  6. Formulate prioritized product interventions categorized into rapid usability fixes and systemic platform redesigns.
  7. Define quantitative success metrics focusing on completion rate improvements and reduction in agency support tickets.

Constraints

  • MUST anchor all findings in public interest design and {{compliance_standards}}.
  • MUST NOT recommend solutions requiring high-end client hardware or advanced technical literacy.
  • All recommendations must accommodate users relying exclusively on mobile or public library infrastructure.
  • Analysis must focus on systemic service barriers rather than individual user deficits.

Output format

  • Executive Summary: 1 paragraph (max 120 words).
  • Administrative Burden Diagnostic: 3 bulleted subsections (Learning, Compliance, Psychological costs).
  • Barrier Severity Matrix: Structured Markdown table with columns [Barrier, Affected Cohort, Severity Rating, Remediation Effort].
  • Strategic Recommendations: Exactly 4 numbered, actionable product initiatives with measurable acceptance criteria.

Self-review

  • Ensure all 6 context variables are explicitly addressed in the diagnostic.
  • Verify that proposed solutions align with {{digital_literacy_baseline}}.
  • Check that no commercial vendor bias is introduced into public architecture suggestions.
AuraScore breakdown
83/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness5/5 · Strong

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

business-strategy
business-product
public-sector-nonprofit
civic-tech
public-sector
accessibility