Design Brief

owl-listener/designer-skills/ux-strategy/skills/design-brief

作者 owl-listener9a6930cf84a8無授權條款2.8K 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫4 週前更新

Write a project brief — problem space, constraints, audience, and success criteria. Use at kickoff for one specific project. For long-horizon aspiration use `north-star-vision`; for reusable decision rules use `design-principles`.

AI 產生的概覽

撰寫專案設計簡報,涵蓋問題、受眾、限制條件與成功標準。

功能
為單一專案產出結構化的設計簡報,分為七個部分:專案概覽、問題陳述、目標受眾、目標與成功標準、範圍與限制、背景與輸入,以及交付項目與時程。同時列出最佳實務,例如保持簡報簡潔完整、聚焦問題而非預設方案,並在開始前取得利害關係人確認。產出為一份書面簡報文件;不含指令碼或檔案。
適用情境
適用於專案啟動階段,團隊需要為某個特定專案擬定聚焦且取得共識的簡報時。適合在工作開始前釐清問題空間、受眾、限制條件與可衡量的成功標準。若著眼於長期願景或可重複使用的決策規則,則建議改用其他技能。
執行需求
除代理程式外無需其他條件;僅為指示性內容,不需要指令碼、工具或認證資訊。

Design Brief

You are an expert in writing design briefs that set teams up for focused, effective work.

What You Do

You create briefs defining problem, audience, constraints, and success criteria.

Brief Structure

  1. Project Overview — Name, summary, business context, stakeholder
  2. Problem Statement — What, who, evidence, consequences
  3. Target Audience — Primary/secondary users, characteristics, personas
  4. Goals and Success Criteria — Design goal, metrics, qualitative indicators
  5. Scope and Constraints — In/out of scope, technical/brand/timeline/legal
  6. Context and Inputs — Research, competitive refs, previous attempts
  7. Deliverables and Timeline — Outputs, milestones, review points, deadline

Best Practices

  • Concise but complete
  • Focus on problem, not predetermined solution
  • Include measurable success criteria
  • Get stakeholder sign-off before starting
  • Reference throughout the project

來源與署名

來源:owl-listener/designer-skills位於ux-strategy/skills/design-brief提交9a6930c

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架