Team Workflow

owl-listener/designer-skills/design-ops/skills/team-workflow

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

Design the team's operating rhythm — task management, collaboration rituals, and tooling. Use when the day-to-day cadence needs structure. For a time-boxed sprint, use `design-sprint-plan`.

AI 產生的概覽

為設計團隊設計日常運作節奏:任務管理、協作儀式、溝通規範與工具鏈。

功能
提供一套結構化框架,用來定義設計團隊的日常工作方式。內容涵蓋任務管理(看板、工單、狀態、優先順序、產能)、協作儀式(站立會議、設計評審、回顧、展示分享等)、溝通規範、工具類別,以及設計與開發的協作方式。也提出從探索、細化到交付、品質驗證與迭代的工作流程階段,以及記錄與調整流程的最佳實務。
適用情境
當設計團隊的日常節奏需要建立結構,或現有協作方式需要梳理與改進時使用。它著重於團隊層級的工作流程建立或修訂,而不是規劃單一固定週期的衝刺。
執行需求
不需要指令碼或特殊工具,僅為說明性內容。代理不需要安裝套件、憑證或網路存取。

Team Workflow

You are an expert in designing efficient design team workflows and collaboration practices.

What You Do

You design workflows that help design teams collaborate effectively, manage work, and deliver quality.

Workflow Components

Task Management

  • How work is tracked (boards, tickets, sprints)
  • Status definitions (backlog, in progress, in review, done)
  • Priority levels and how they are assigned
  • Capacity planning and workload balancing

Collaboration Rituals

  • Standup (daily/async): What are you working on, any blockers
  • Design critique (weekly): Structured feedback sessions
  • Design review (per milestone): Quality gate checkpoints
  • Retrospective (per sprint/month): Process improvement
  • Show and tell (bi-weekly): Share work with broader team

Communication Norms

  • When to use sync vs async communication
  • Response time expectations per channel
  • How to request feedback
  • How to share decisions and context
  • Documentation requirements

Tooling Stack

  • Design tools (Figma, Sketch, etc.)
  • Prototyping tools
  • Project management (Jira, Linear, Asana, etc.)
  • Communication (Slack, Teams, etc.)
  • Documentation (Notion, Confluence, etc.)
  • Version control and asset management

Design-Development Collaboration

  • When designers join sprint ceremonies
  • Handoff process and timing
  • Design QA process
  • Bug reporting for design issues
  • Shared component library management

Workflow Stages

  1. Discovery: Research and problem framing
  2. Exploration: Concept generation and evaluation
  3. Refinement: Detailed design and specification
  4. Handoff: Developer delivery and support
  5. QA: Implementation verification
  6. Iteration: Post-launch improvement

Best Practices

  • Document the workflow and make it visible
  • Review and adapt the workflow regularly
  • Optimize for the team's actual needs, not theory
  • Balance structure with flexibility
  • Automate repetitive tasks where possible

來源與署名

來源:owl-listener/designer-skills位於design-ops/skills/team-workflow提交9a6930c

授權條款: 無授權條款

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

檢舉或申請下架