Skip to content
TheChatArchiveThe Chat Archive
Grok 4.1 Fast· xaiHugging Face Frontier Reasoning Traces

Compose a design advocacy guild that pairs designers with squads, tracks adoption, and…

  1. User

    Compose a design advocacy guild that pairs designers with squads, tracks adoption, and surfaces blockers.

  2. Assistant

    Design Advocacy Guild Charter

    Mission

    The Design Advocacy Guild empowers squads across the organization by pairing dedicated design advocates with cross-functional teams, fostering design excellence, tracking adoption of design standards and practices, and proactively surfacing blockers to ensure seamless collaboration and high-quality outcomes. Our goal: Elevate product design from a siloed function to an embedded squad superpower.

    Objectives

    1. Pairing: Match experienced designers as advocates to squads lacking design support.
    2. Adoption Tracking: Measure and report on the uptake of design system components, guidelines, and processes.
    3. Blocker Surfacing: Identify, prioritize, and resolve impediments to design integration (e.g., tooling gaps, process friction, resource constraints).
    4. Knowledge Sharing: Cultivate a community of practice to amplify design impact organization-wide.

    Guild Structure

    Leadership (3-5 members)

    • Guild Lead (1): Rotates quarterly; oversees operations, reports to Design Leadership.
    • Ops Coordinator (1): Manages pairing, tracking dashboards, and meeting logistics.
    • Metrics Champion (1): Owns adoption KPIs and blocker triage.

    Core Members

    • Design Advocates (rotating pool of 8-12 senior/mid-level designers): Paired 1:1 or 1:2 with squads (20-30% time allocation).
    • Squad Reps (voluntary, 1 per squad): Provide feedback loops.
    • Guests: Engineering leads, PMs, or execs as needed.

    Total Size: 15-25 active members to start, scaling with org growth.

    Key Processes

    1. Designer-Squad Pairing

    • Intake: Squads self-nominate via a shared form (e.g., Google Form/Slack bot) detailing needs (e.g., "UX audit," "Design system onboarding").
    • Matching: Guild Lead reviews and pairs based on advocate expertise, squad maturity, and availability. Aim for <48hr turnaround.
    • Onboarding Kit: Standardized handover with squad context, design system links, and success criteria.
    • Pairing Duration: 3-6 months default; quarterly reviews for extension/rotation.
    • Capacity: Limit to 4-6 active pairings per advocate.

    Flow Diagram:

    Squad Request → Guild Intake → Expertise Match → Kickoff Call → Weekly Syncs → Quarterly Review → Rotate/Extend
    

    2. Adoption Tracking

    • Metrics Dashboard (e.g., Google Sheets/Tableau/Grafana):
      MetricDefinitionTargetFrequency
      Design System Usage% of components from system in PRs80%Weekly
      Guideline ComplianceAudit score (0-100) per sprint90+Bi-weekly
      Advocate Touchpoints# of sessions/reviews per squad2+/weekMonthly
      NPS from SquadsSatisfaction score (0-10)8+Quarterly
    • Automation: Integrate with GitHub/Jira for pull request labels (e.g., "design-reviewed") and Figma usage analytics.
    • Reporting: Monthly guild sync + exec summary shared in #design-guild Slack channel.

    3. Blocker Surfacing

    • Collection: Advocates log blockers in a shared triage board (e.g., Jira/Trello) with tags: [Process], [Tooling], [Resource], [Culture].
    • Triage Cadence:
      • Daily: Advocates flag urgent items in Slack #blockers.
      • Weekly: 30-min prioritization meeting (MoSCoW method: Must/Should/Could/Won't).
    • Resolution Paths:
      • Self-resolve (advocate/squad).
      • Escalate to guild leads.
      • Cross-guild (e.g., Eng Guild for tooling).
    • Post-Mortem: Quarterly review of resolved blockers to inform process improvements.

    Blocker Board Columns: Backlog → In Progress → Resolved → Archived.

    Operations & Cadence

    • Meetings:
      MeetingCadenceDurationAttendees
      Full Guild SyncBi-weekly60 minAll
      Advocate Office HoursWeekly30 minAdvocates + open
      Leadership HuddleWeekly15 minLeads
      Quarterly All-HandsQuarterly90 minAll + guests
    • Tools Stack:
      • Collaboration: Slack (#design-advocacy), Notion (charter/wiki).
      • Tracking: Jira/Trello (blockers), Google Sheets (dashboard), Figma (reviews).
      • Comms: Loom videos for async updates.
    • Onboarding New Members: 1-hour session + buddy assignment.

    Success Measures

    • Short-Term (3 months): 80% pairing fill rate, 50+ blockers surfaced/resolved.
    • Long-Term (6+ months): 20% org-wide lift in design adoption metrics, +15% squad NPS.
    • Annual Review: Guild charter refresh based on retros.

    Getting Started

    1. Announce in all-hands and design channels.
    2. Recruit initial advocates and leaders (volunteers first).
    3. Launch with pilot pairings for 3-5 squads.
    4. Iterate based on feedback.

    This guild is lightweight, actionable, and scalable. Questions or tweaks? Let's refine it together! 🕵️‍♂️

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.