Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

Converting a Discovery Brief to a Design Brief

Once a Discovery Brief has a DDQS ≥ 6 and is advancing to Specification, UX typically needs a Design Brief — a structured handoff document that translates the problem definition into actionable design scope, user tasks, and a phased delivery timeline.

Recommended: Use product-os

With product-os, you can convert a Discovery Brief to a Design Brief directly — no copy-pasting required.

  1. Open product-os (Claude desktop with the product-os project)

  2. Say: "Convert the Discovery Brief for [Project Name] to a Design Brief" — or paste the Confluence page URL

  3. Claude fetches the brief from Confluence and generates the Design Brief using the standard CXT prompt template

  4. Review and edit the output in the conversation

  5. Ask Claude to publish the Design Brief to Confluence:

Manual Path: Google Gemini (or any AI assistant)

If product-os is not available:

  1. Navigate to Gemini (or Claude.ai, ChatGPT, etc.)

  2. Open a new chat and paste in the Prompt Template below

  3. Open your Discovery Brief in Confluence

  4. Ctrl+A to highlight all → paste into a Google Doc → Ctrl+A → right-click → "Copy as Markdown"

    • If you do not see "Copy as Markdown": Google Doc → Tools → Preferences → Enable Markdown

  5. Paste your Discovery Brief into the prompt where indicated ({PASTE FULL DISCOVERY BRIEF HERE})

  6. Execute the prompt

  7. Copy the generated Design Brief and create the document in Confluence under Products and Initiatives → [Product Area]

Prompt Template

You are an exacting UX research assistant and product strategist. Your task: **Transform the supplied Discovery Brief into a Design Brief** that matches the format and tone below without inventing facts or features not present in the source. Follow every instruction precisely. --- ## **0. Inputs** **Discovery Brief:** <<<DISCOVERY_BRIEF_START>>> {PASTE FULL DISCOVERY BRIEF HERE} <<<DISCOVERY_BRIEF_END>>> **Additional Guidance (optional):** {ANY SPECIAL NOTES OR OVERRIDES} --- ## **1. Output Requirements** Return one Design Brief with **all** of the following sections **in order**: 1. \# Design Brief – {Concise Feature Name} 2. \#\# Project Introduction – One paragraph, source-based only. 3. \#\# Users and Needs – Bullet list of user groups → goals/constraints. 4. \#\# Tasks – Ordered list of primary user actions. 5. \#\# Timeline and Deliverables – Insert the fixed scaffold below. | Phase | Core Activities | Typical Outputs | | ----- | ----- | ----- | | Kick-off & Alignment | Scope review, success-metric check, tech constraints, design-system audit | - Updated brief & open questions list | | Lo-Fi User Flows + Wireframes | Map happy/edge flows, rapid sketching, internal critique | - Annotated flow diagrams - Low-fidelity wireframes | | Hi-Fi Visual Design | Apply branding, states, responsive breakpoints, define micro-interactions | - High-fidelity Figma screens - Component specs | | Interactive Prototype | Connect screens, add motion, input validation states, animate micro-interactions | - Clickable prototype | | Usability Test & Iteration | 5–8 participant test, analytics review, iterate | - Test report - Revised prototype | | Accessibility & Edge-Case Review | WCAG checks, keyboard nav, color contrast fixes | - a11y checklist | | Design QA & Dev Handoff | Redlines, tokens, asset exports, Figma links, design-QA support during build | - Finalized Figma screens - Full prototype + Loom walkthrough | *Stakeholders can adjust dates and owners after generation.* Formatting rules: * Use concise, plain-language bullets. * No buzzwords or speculative features. Cite only what exists in the Discovery Brief. * If a required detail is missing, leave it out, or perform web research. Do **NOT** fabricate or guess. Always clearly state if you leave it out, or research it. * Do not emit explanatory meta-text, apologies, or system messages. Deliver just the Design Brief. --- ## **2. Evaluation Checklist (for your own hidden reasoning – do not output)** * Did I faithfully map every point from Discovery → Design? * Did I exclude anything not supported by the source? * Is the style clear, direct, and free of fluff? * Is "Timeline and Deliverables" scaffold inserted verbatim? Return only the finished Design Brief that passes this checklist.

Reference