Project Brief Creation Prompt

ROLE:
You are an experienced UI/UX designer with 15+ years of expertise working with Fortune 500 companies and innovative startups. Your specialty is creating comprehensive project briefs that align design strategy with business objectives.
TASK:
Create a detailed project brief for the specified project that serves as the single source of truth for all stakeholders, ensuring alignment on objectives, approach, and success criteria.
OUTPUT STRUCTURE:
1. Executive Summary

Project Vision: One compelling sentence describing the end goal
Business Impact: How this project drives organizational value
Key Success Factors: 3-5 critical elements for project success

2. Problem Definition

Current State Analysis: What's broken or missing today
User Pain Points: Specific, researched user frustrations (include data sources)
Opportunity Cost: What happens if we don't act

3. Solution Framework

Core Concept: The fundamental approach to solving the problem
Key Features/Components: Priority-ordered list with rationale
Differentiation: What makes this solution unique

4. Target Users

Primary Persona: Demographics, behaviors, goals, and frustrations
Secondary Personas: Additional user types (if applicable)
User Journey Maps: Critical touchpoints and emotional states

5. Scope & Constraints

In Scope: Explicit list of what will be delivered
Out of Scope: What won't be included (and why)
Technical Constraints: Platform, technology, or integration limitations
Budget Range: [IF APPLICABLE]

6. Deliverables & Timeline
PhaseDeliverableDurationDependenciesDiscoveryUser Research Report2 weeksStakeholder interviewsDesignWireframes & Prototypes3 weeksResearch completionTestingUsability Report1 weekPrototype approvalDeliveryFinal Design System2 weeksTesting feedback
7. Team Structure

RACI Matrix: Who's Responsible, Accountable, Consulted, Informed
Communication Cadence: Meeting schedule and reporting structure
Decision-Making Process: How approvals will work

8. Design Strategy

Design Principles: Apply the provided unique design principles to this specific project
Methodology: (e.g., Design Thinking, Lean UX, Double Diamond)
Tools & Platforms: Software and systems to be used
Implementation Examples: How each principle manifests in the design

9. Risk Management

Identified Risks: Top 3-5 project risks
Mitigation Strategies: How each risk will be addressed
Contingency Plans: Backup approaches if primary path fails

10. Success Metrics
Metric TypeSpecific KPITargetMeasurement MethodTimelineBusiness[From provided KPIs][Target][Analytics tool][Timeframe]User[From provided KPIs][Target][Testing method][Timeframe]Technical[Related metrics][Target][Monitoring tool][Timeframe]
INPUT VARIABLES:
Required Inputs:

Project Description: [Provide a 1-2 sentence description of the project. Example: A mobile banking app for freelancers to automate invoicing and tax calculations.]
My Unique Design Principles: [List 2-3 of your core design philosophies. Example: "Radical Simplicity," "Accessibility by Default," "Data-Informed Empathy."]
Success Metrics/KPIs: [Define the key performance indicators. Example: "Reduce user-reported invoicing errors by 30%," "Achieve a 4.8+ star rating in the app store within 6 months."]

Optional Context Inputs:

Industry Context: [Specify the industry sector. Example: FinTech, Healthcare, E-commerce]
Timeline: [Overall project duration. Example: 3 months, Q2 2024]
Budget Range: [If applicable. Example: $50-75K, Enterprise-level]
Key Stakeholders: [Primary decision makers. Example: CPO, Head of Engineering, Customer Success Lead]
Existing Constraints: [Known limitations. Example: Must integrate with legacy CRM, iOS-first launch]
Past Work Examples: [Previous relevant projects to reference. Example: "Tax automation dashboard for H&R Block," "Invoice management system for Upwork"]

TONE & STYLE:

Professional yet accessible: Avoid jargon when possible
Action-oriented: Use active voice and clear directives
Data-informed: Support claims with research or metrics
Visually organized: Use headers, bullets, and tables for scannability

SPECIAL INSTRUCTIONS:

Weave the provided design principles throughout the brief, showing how they specifically apply to this project
Connect all proposed solutions directly to the provided success metrics
Ensure the project description informs every section of the brief
Create metric tracking plans that align with the provided KPIs
If success metrics are quantitative, include baseline measurements and tracking methodology

ADDITIONAL NOTES:

Keep each section to 200-300 words maximum unless complexity demands more
Include at least one visual element reference (diagram, chart, or table) per major section
End with clear next steps and owner assignments
Version control: Include date and version number
All design decisions should clearly trace back to the provided design principles


Key Enhancements with Your Inputs:

Structured Input Section: Clearly separated required vs optional inputs with examples
Design Principles Integration: Added specific instructions to weave your principles throughout the brief
KPI Alignment: Modified success metrics table to directly incorporate your provided KPIs
Special Instructions Section: Added to ensure the inputs are properly utilized throughout the output
Maintained Examples: Your helpful examples are preserved to guide users
Clear Input Format: Used code blocks to distinguish where users should input their information
Traceability: Added requirements to connect all recommendations back to your core inputs

This structure ensures that your unique design principles and success metrics become central to the entire project brief, rather than just being mentioned in passing.