Dashboard Requirements

What it does

This skill analyzes existing Product on Purpose dashboard data and generates a structured requirements document. It identifies key performance indicators (KPIs), user stories, and acceptance criteria based on observed usage patterns and reported issues within the dashboard. The output is formatted as a clear, actionable document suitable for engineering teams or further refinement by product managers.

When to use it

• Rapid Requirements Definition: Quickly generate initial requirements when starting a new feature development cycle.
• Dashboard-Driven Insights: Translate observed user behavior and reported issues from the Product on Purpose dashboard into concrete needs.
• Alignment with User Needs: Ensure that development efforts are directly aligned with how users are actually interacting with the product.
• Reducing Ambiguity: Create a shared understanding of requirements between product, design, and engineering teams.

Key capabilities

• KPI identification from dashboard data
• User story generation based on usage patterns
• Acceptance criteria definition for user stories
• Structured requirements document output

Example prompts

• "Analyze the Product on Purpose dashboard data and generate a requirements document focusing on user onboarding."
• "Based on reported issues in the dashboard, create user stories and acceptance criteria for improving search functionality."
• "Generate a list of KPIs that would indicate successful adoption of the new feature based on dashboard usage."

Tips & gotchas

The quality of the generated requirements depends heavily on the completeness and accuracy of the data within the Product on Purpose dashboard. Ensure the dashboard is capturing relevant user interactions and feedback for optimal results.