<aside> 🎤

📖 How to Use This Dashboard

This template is designed to centralize research, design, tasks, and deliverables for each project.

Duplicate this page at the start of every new project, then follow these steps:

Step 1: Set Up Your Project Summary

• Fill in the Project Info table (Phase, Deadline, Owner, Priority).
• Add Stakeholders and key links (Figma, Jira, Miro).

Step 2: Add Research

• Use the Research Repository to log interviews, usability tests, and analytics.
• Link research insights to Personas and Journey Steps.

Step 3: Define Personas & Journey

• Add or update personas in the Personas Gallery.
• Fill out the User Journey steps and emotions.

Step 4: Track Work

• Create tasks in the Tasks Database and use the Kanban board to manage progress.
• Track component requests in Component Requests if new UI patterns are needed.

Step 5: Deliverables & QA

• Log all design deliverables in the Deliverables Table and update their status.
• Collect stakeholder feedback in the Feedback & QA Tracker.

Step 6: Wrap Up

• Fill in Metrics to measure impact.
• Run a Design Retrospective to capture learnings for future projects. </aside>

1. Design Project Dashboard

• Purpose: A single hub per project where all research, designs, and tasks live.
• Common Elements:
  • Project brief (problem statement, goals, KPIs)
  • Key links (Figma file, Jira board, style guide)
  • Stakeholders & deadlines
  • Quick status update (In Discovery → In Design → In Dev → Released)

Project brief

<aside> 🎯

Goal: Increase checkout conversion 3.2% → 5% by Q3

Context: 60% checkout drop-off due to form friction

KPIs: Conversion, Bounce, NPS (list them).

</aside>

Key links

Status:

• 🟠 In Design

Deadline: September 30, 2025

Priority: 🔥 High

Owner:

Links:

🎨[Figma File]

[Miro Board]

📋[Jira Board]

🧠[Research Repo]

🧩[Design System/Style Guide]

Stake Holders (who’s who, when’s what)

Stakeholders

Quick status update (Discovery → Design → Dev → Released)

Project Info

2. Research and Insights

• Purpose: Centralized place to store user research findings.
• Structure:
  • Database with: Research Type (Interview, Survey, Usability Test), Participants, Date, Key Insights, Links to Recordings
  • Tags for Personas, Pain Points, Themes
  • Views: Table (raw data), Gallery (persona cards), Board (by theme)