Dashboard Product Framing

Dashboard Product Framing

When to Use

• A screenshot or mockup exists but requirements are still fuzzy.
• Teams want to build a dashboard before clarifying users and decisions.
• A dashboard needs to be treated like a product, not just a page.

Workflow

1. Identify primary users, secondary users, and their operating cadence.
2. Define the core decisions the page or webspace must support.
3. Separate primary actions from passive monitoring.
4. Define the core page purpose: landing page, command center, detail page, or workflow queue.
5. Translate the vision into page sections, drill paths, and success criteria.

Output Template

# Dashboard Product Brief

## Product goal
- ...

## Primary users
- Role:
- Cadence:
- Key decisions:

## Core jobs to be done
- Monitor:
- Investigate:
- Escalate:
- Approve:

## Page types
- Landing page:
- Detail page:
- Workflow page:

## Success criteria
- Adoption:
- Time saved:
- Decision quality:

Quality Checklist

• Each section supports a real user decision.
• Monitoring and action workflows are both explicit.
• Success criteria go beyond visual polish.
• The page is framed as part of a broader product surface.