agentleFS
mahirautela2020-designmahirautela2020-design/claude-skills-ux/collab-design-ops-process/SKILL.md

collab-design-ops-process

Skill1 starsChanged 8 months agoMITView on GitHub

Supports healthy design operations and ways of working. Use when the user needs help contributing to team rituals (crits, reviews, retros), creating templates and documentation, maintaining skills matrices, mentoring, and improving how the design team works over time, aligned with product and engineering workflows.

The file

Show its rules and text

We split this skill into the rules it gives an agent

22 rules. About 0 are common, 21 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈21

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when you’re shaping how the design team collaborates, not just the design of individual products.

    line 22
  2. Distinctive:

    Start by understanding what design operations should improve.[web:205][web:210][web:211][web:203]

    line 30
  3. Very specific:

    Use these as anchors for any process or ritual changes, and link them to product/UX outcomes where possible (product-ux-strategy-alignment).

    line 43
  4. Distinctive:

    Create lightweight templates for:

    line 58
  5. Distinctive:

    Ensure rituals stay focused, time-boxed, and useful.

    line 63
  6. Distinctive:

    Use retrospectives regularly to improve the team’s process.[web:204][web:201][web:208][web:400][web:406][web:403]

    line 69
  7. Distinctive:

    Follow up in future retros to check which improvements stuck and whether they helped, treating retros as part of iterative design and …

    line 84
  8. Distinctive:

    Keep it as simple as possible while capturing essential information.

    line 103
  9. Distinctive:

    Document key design decisions and rationale in a shared place.

    line 116
  10. Distinctive:

    Use a skills matrix to understand and grow team capabilities.[web:214][web:206][web:209][web:392][web:393][web:401]

    line 132
  11. Distinctive:

    Ask team members to self-assess and, where appropriate, have managers or peers provide input.

    line 138
  12. Distinctive:

    Use the matrix to:

    line 140
  13. Distinctive:

    Use the skills matrix and rituals to enable mentoring and peer learning.[web:206][web:209][web:207][web:398]

    line 152
  14. Distinctive:

    Ensure design processes fit into broader product and engineering workflows.[web:210][web:205][web:188][web:212]

    line 168
  15. Distinctive:

    Update process diagrams and checklists when practices evolve, and connect them to strategy/metrics work so process supports outcome-driven …

    line 182
  16. Distinctive:

    Use Design Ops to protect focus time and team health.[web:207][web:203][web:210][web:211]

    line 188
  17. Distinctive:

    Use retros and 1:1s to surface workload and burnout risks early.[web:207][web:203][web:398]

    line 194
  18. Distinctive:

    Check whether each ritual has a clear purpose and outcome.

    line 231
  19. Distinctive:

    Keep docs lightweight and close to where work happens (e.g., linked from design files and tickets).

    line 237
  20. Distinctive:

    Use retros to identify which docs are helpful and which can be archived.[web:205][web:210][web:212]

    line 239
  21. Distinctive:

    Use it to create opportunities (pairing, learning), not to judge people.[web:206][web:209][web:214][web:401]

    line 245
  22. Distinctive:

    Use this skill with:

    line 251

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Design Operations & Process

Purpose

This skill helps designers strengthen team operations: shared rituals, templates, documentation, and skills management that make UX work more effective and sustainable.[web:210][web:211][web:205][web:207] It also covers maintaining a skills matrix, mentoring others, and continuously improving ways of working through retrospectives and small process changes, in alignment with product and engineering practices, and outcome/metrics thinking from related skills.[web:204][web:214][web:206][web:209][web:201][web:208][web:400][web:403]

Use this skill when you’re shaping how the design team collaborates, not just the design of individual products.


Instructions

Step 1: Clarify team goals and pain points

Start by understanding what design operations should improve.[web:205][web:210][web:211][web:203]

Ask the team:

  • "What slows us down or creates rework?"
  • "Where do handoffs, communication, or alignment break down?"
  • "Which rituals or processes already work well that we should keep?"

Summarize:

  • 3–5 key pain points (e.g., unclear handoffs, inconsistent critique, poor documentation).
  • 2–3 desired outcomes (e.g., smoother releases, better alignment, less burnout).[web:207][web:205][web:210]

Use these as anchors for any process or ritual changes, and link them to product/UX outcomes where possible (product-ux-strategy-alignment).


Step 2: Strengthen core design rituals

Support and improve regular design rituals such as crits, design reviews, and share-outs.[web:210][web:211][web:205]

For each ritual:

  • Clarify purpose:
    • Crits: improve work through peer feedback.
    • Reviews: align with product/engineering, make decisions.
    • Show & tell: share learnings and patterns.
  • Define cadence, participants, and roles (facilitator, presenter, note-taker).
  • Create lightweight templates for:
    • Agenda.
    • What to present (problem, context, work, feedback needed).
    • How to capture decisions and actions.[web:210][web:211][web:205]

Ensure rituals stay focused, time-boxed, and useful; adjust based on feedback and retrospectives.


Step 3: Run and improve retrospectives

Use retrospectives regularly to improve the team’s process.[web:204][web:201][web:208][web:400][web:406][web:403]

For a project or time period:

  • Ask:
    • “What went well?”
    • “What was challenging or frustrating?”
    • “What should we try differently next time?”
  • Use simple formats:
    • Start / Stop / Continue.
    • Mad / Sad / Glad (for team morale and collaboration).
    • “Puzzles / Risks / Appreciations”.

Agree on a small number of action items with owners and due dates.[web:204][web:208]

Follow up in future retros to check which improvements stuck and whether they helped, treating retros as part of iterative design and delivery rather than one-off meetings.[web:400][web:406]


Step 4: Create and maintain shared templates

Develop templates that make recurring work easier and more consistent.[web:202][web:205][web:210]

Common templates include:

  • Research plans and reports.
  • Problem framing and opportunity briefs.
  • Design specs and handoff checklists.
  • Workshop agendas and boards.
  • Retro boards.

For each template:

  • Clarify when to use it.
  • Keep it as simple as possible while capturing essential information.
  • Store it in a central, easy-to-find place (design system site, Notion, intranet).[web:202][web:205][web:210]

Review templates periodically to remove outdated ones and improve based on team feedback and evolving practices.


Step 5: Improve documentation and decision tracking

Turn decisions and patterns into living documentation.[web:205][web:210][web:212]

Practices:

  • Document key design decisions and rationale in a shared place.
  • Capture patterns and guidelines:
    • Component usage rules.
    • Interaction patterns.
    • Accessibility and content guidelines.
  • Link documentation from:
    • Design system.
    • Project docs.
    • Tickets or epics.

Aim for documentation that is “just enough” to be useful and kept up to date, rather than perfect but stale.[web:205][web:210][web:212]


Step 6: Maintain and use a skills matrix

Use a skills matrix to understand and grow team capabilities.[web:214][web:206][web:209][web:392][web:393][web:401]

Steps:

  • Define skills relevant to your team (e.g., research, IA, interaction, visual design, product thinking, facilitation, Ops).
  • For each skill, define levels or descriptors (e.g., awareness, working, advanced, expert).
  • Ask team members to self-assess and, where appropriate, have managers or peers provide input.

Use the matrix to:

  • Identify strengths and gaps at team level.
  • Plan learning and pairing/mentoring opportunities.
  • Inform staffing decisions for projects and initiatives.[web:206][web:209][web:214][web:401]

Frame the matrix as a development tool, not a performance rating system, to encourage honest self-assessment and growth.[web:401][web:404][web:405]


Step 7: Support mentoring and knowledge sharing

Use the skills matrix and rituals to enable mentoring and peer learning.[web:206][web:209][web:207][web:398]

Practices:

  • Pair less-experienced designers with more-experienced ones on relevant skills.
  • Set up:
    • Regular 1:1 mentoring or peer coaching.
    • Brown-bag sessions or internal talks where team members share case studies or methods.
  • Encourage documentation of learnings from projects and experiments.

This turns the team’s experience into a shared asset, not just individual knowledge, and supports structured growth paths.[web:398][web:404][web:401]


Step 8: Align design processes with product and engineering

Ensure design processes fit into broader product and engineering workflows.[web:210][web:205][web:188][web:212]

Examples:

  • Clarify where design activities fit within:
    • Discovery and validation.
    • Backlog refinement.
    • Sprint planning.
  • Define expected outputs at each stage:
    • Discovery insights, problem briefs, prototypes, specs.
  • Coordinate with Product and Eng Ops (if present) to:
    • Align cadences (e.g., sprint length, planning cycles).
    • Integrate design reviews and UX checks into broader delivery processes.[web:210][web:212][web:205]

Update process diagrams and checklists when practices evolve, and connect them to strategy/metrics work so process supports outcome-driven design.


Step 9: Protect focus and sustainable ways of working

Use Design Ops to protect focus time and team health.[web:207][web:203][web:210][web:211]

Practices:

  • Limit unnecessary meetings; cluster rituals into predictable blocks.
  • Encourage blocking focus time in calendars for deep work.
  • Use retros and 1:1s to surface workload and burnout risks early.[web:207][web:203][web:398]
  • Automate or streamline repetitive tasks where possible (e.g., using tooling for specs, tokens, and visual regression).[web:205][web:210]

The goal is to create a sustainable environment where quality UX work can thrive.


Examples

Example 1: Improving design reviews and handoff

  • Pain points:
    • Inconsistent design reviews, late feedback, messy handoffs.
  • Ops changes:
    • Introduced a weekly crit with a clear agenda.
    • Created a standard design spec template and Figma file structure.
    • Added a short pre-release UX review step.[web:205][web:210][web:211]
  • Outcome:
    • Fewer last-minute surprises, smoother collaboration, and reduced rework.

Example 2: Skills matrix and mentoring

  • Situation:
    • Team unsure where strengths and gaps were; junior designers needed guidance.
  • Ops changes:
    • Defined a skills matrix with core UX and product skills.
    • Ran a self-assessment and used results to match mentors and mentees.
    • Planned learning sessions around common gaps.[web:214][web:206][web:209][web:401]
  • Outcome:
    • Clearer growth paths for designers and better distribution of expertise.

Troubleshooting

Rituals feel like “meetings for meetings’ sake”

  • Check whether each ritual has a clear purpose and outcome.
  • Reduce frequency or length where they aren’t adding value.
  • In retros, ask which rituals help and which need redesign or removal.[web:204][web:211][web:203][web:400]

Documentation becomes outdated or ignored

  • Keep docs lightweight and close to where work happens (e.g., linked from design files and tickets).
  • Assign ownership for key docs (e.g., design system, process guides).
  • Use retros to identify which docs are helpful and which can be archived.[web:205][web:210][web:212]

Skills matrix feels like a performance rating tool

  • Frame it as a development tool, not evaluation.
  • Emphasize self-awareness and growth, not grades.
  • Use it to create opportunities (pairing, learning), not to judge people.[web:206][web:209][web:214][web:401]

Notes for use with other skills

  • Use this skill with:
    • Stakeholder and engineering collaboration skills (collab-stakeholder-communication, collab-ux-engineering) to embed design work into broader team processes.
    • Research and design-system skills (ux-user-research, ui-design-systems-components, ui-design-tools-handoff) when creating templates and shared practices.
    • Product-thinking and metrics skills (product-ux-strategy-alignment, ux-product-design-metrics) to ensure design operations support strategic, outcome-driven work.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.