Mapping Design Operations
Teams map their design operations function onto a structured canvas, trace services back to specific internal and external groups, and mark current operational strengths and bottlenecks.
Choose this exercise
Purpose: Visually map how a design operations function delivers services, connects to collaborator groups, and encounters operating constraints.
Use it when: Use when clarifying operational roles, intake paths, and delivery bottlenecks between design teams and partner departments like product, engineering, or procurement.
Skip it when: Skip if the team has no shared design delivery model, or if the meeting's purpose is to resolve an interpersonal grievance rather than organizational workflow.
Group arrangement: Working teams of 3 to 6 people per canvas poster.
Timing: 60 minutes for a foundational working session; public source notes formats ranging from 15-minute individual sketches to multi-day sessions.
Materials and tools
- 1 large canvas poster (A0 size or whiteboard) per group of 3 to 6
- Sticky notes in at least 4 distinct colors per group (including green and pink/red for critique)
- Dark chisel-tip markers (1 per participant)
- Roll of painter's tape to mount posters
- Camera or smartphone to document results
Before participants arrive
- Draw or tape the Design Ops Canvas sections onto wall posters or whiteboards: center circle 'Who are we? / Collaborators', central block 'What do we do? / Services', surrounding blocks 'How do we work? / Practices & Tools', and bottom block 'What constrains us?'.
- Distribute color sticky notes and markers to each station.
Say this to open
Today we are mapping how our design team operates within the larger organization. We will identify who we serve, the specific value we deliver, our operational practices, and the constraints that slow us down. Everyone will draft notes silently first, then post and organize them together.
How to run it
Map collaborator groups 10 minutes
Explain the canvas layout using the opening script. Direct teams to start in the center circle: 'Who are we?' Each person writes key collaborator groups on sticky notes (for example, internal engineering teams, product managers, or external agencies). Use a dedicated color for each group type. Post and de-duplicate notes in the center circle.
Map services and value delivered 15 minutes
Move to the 'What do we do?' section. Participants write specific services or value propositions the design function provides to those collaborators (such as design system governance, vendor onboarding, or sprint tooling). Match the note color to the collaborator segment it serves. If a service serves two groups, write two corresponding color notes. Post them in the section.
Map practices, tools, and constraints 15 minutes
Working clockwise around the canvas, map the remaining operational blocks: tools, processes, and rituals. Finish with the bottom section: 'What constrains us?' (budget limits, approval delays, tooling fragmentation). Keep using related colors where connections exist.
Assess strengths and bottlenecks 10 minutes
Hand out green and red sticky notes (or mark notes with '+' and '-'). Each person places up to two green notes next to high-functioning areas and up to two red notes next to acute operational friction points.
Debrief and select priorities 10 minutes
Gather the whole room. Have each group share their top operational strength and their primary constraint. Run a short whole-room debrief using the provided questions.
Debrief questions
- Which collaborator group has the clearest operational connection to design, and which is most ambiguous?
- Where are red constraint flags clustering on the canvas?
- What is one immediate change to our operating practices that would remove a highlighted constraint?
Finished output: A completed Design Operations Canvas poster documenting collaborator groups, delivery services, supporting practices, and tagged operational bottlenecks.
Remote
Set up a digital whiteboard with the four canvas zones marked. Assign each participant a dedicated sticky note color for their collaborator types. Run silent drafting in parallel, then use voice turns to cluster. Use virtual green and red tags for the assessment step.
Hybrid
Pair in-person and remote participants at the same digital board so physical attendees do not create an offline parallel version. Designate an in-room participant to echo physical room questions into the shared meeting audio.
Access and participation choices
- Provide high-contrast markers and allow using typed digital stickies or marked symbols (+ and -) instead of relying solely on color recognition.
- Participants may choose to observe silently or write private notes during drafting without posting every item.
If the session gets stuck
- Participants write broad aspirations instead of current working reality.
- Prompt them to document only services and tools that were actively used within the last 30 days.
- Disagreements arise about whether a service is actually delivered effectively.
- Instruct the team to place the service card in the middle section and flag it with a red assessment note for discussion during debrief.
Terms used here
- Design Ops: The organizational practices, workflows, and tools that support design teams in delivering their work efficiently.
Run this exercise live
The facilitator console stays in this browser. Its QR handoff is a short-lived participant snapshot containing only public exercise instructions, phase, prompt, and timer state.
What participants need now
Materials:
This is a participant-safe snapshot, not a response form. It sends nothing back to the facilitator.
Run this with your AI assistant +
Works with Claude, ChatGPT, Gemini, or your own local model: paste this prompt and your AI will co-facilitate this exercise with you.
Help me prepare and run the exercise below. First ask for my participant count, time, setting, access needs and intended result. Check these against the stated limits. Use the supplied rules and materials. Explain any proposed changes before using them, and label them as adaptations. Do not invent source claims or require personal disclosure. Give me one step at a time when I say start. I manage the people, physical activity and clock; do not claim to observe the room. Ask me what happened before choosing a next step. Reference revision: 672e408abfb5864317228d38d9e193e984071cabe4c56f2408faf4fb46fa4771 # Mapping Design Operations Teams map their design operations function onto a structured canvas, trace services back to specific internal and external groups, and mark current operational strengths and bottlenecks. **Time:** 60 minutes. 60 minutes for a foundational working session; public source notes formats ranging from 15-minute individual sketches to multi-day sessions. **People:** 3 to 18. Working teams of 3 to 6 people per canvas poster. ## Choose this exercise **Purpose:** Visually map how a design operations function delivers services, connects to collaborator groups, and encounters operating constraints. **Use it when:** Use when clarifying operational roles, intake paths, and delivery bottlenecks between design teams and partner departments like product, engineering, or procurement. **Skip it when:** Skip if the team has no shared design delivery model, or if the meeting's purpose is to resolve an interpersonal grievance rather than organizational workflow. ## Materials and tools - 1 large canvas poster (A0 size or whiteboard) per group of 3 to 6 - Sticky notes in at least 4 distinct colors per group (including green and pink/red for critique) - Dark chisel-tip markers (1 per participant) - Roll of painter's tape to mount posters - Camera or smartphone to document results ## Before participants arrive 1. Draw or tape the Design Ops Canvas sections onto wall posters or whiteboards: center circle 'Who are we? / Collaborators', central block 'What do we do? / Services', surrounding blocks 'How do we work? / Practices & Tools', and bottom block 'What constrains us?'. 2. Distribute color sticky notes and markers to each station. ## Say this to open Today we are mapping how our design team operates within the larger organization. We will identify who we serve, the specific value we deliver, our operational practices, and the constraints that slow us down. Everyone will draft notes silently first, then post and organize them together. ## How to run it ### 1. Map collaborator groups (10 minutes) Explain the canvas layout using the opening script. Direct teams to start in the center circle: 'Who are we?' Each person writes key collaborator groups on sticky notes (for example, internal engineering teams, product managers, or external agencies). Use a dedicated color for each group type. Post and de-duplicate notes in the center circle. ### 2. Map services and value delivered (15 minutes) Move to the 'What do we do?' section. Participants write specific services or value propositions the design function provides to those collaborators (such as design system governance, vendor onboarding, or sprint tooling). Match the note color to the collaborator segment it serves. If a service serves two groups, write two corresponding color notes. Post them in the section. ### 3. Map practices, tools, and constraints (15 minutes) Working clockwise around the canvas, map the remaining operational blocks: tools, processes, and rituals. Finish with the bottom section: 'What constrains us?' (budget limits, approval delays, tooling fragmentation). Keep using related colors where connections exist. ### 4. Assess strengths and bottlenecks (10 minutes) Hand out green and red sticky notes (or mark notes with '+' and '-'). Each person places up to two green notes next to high-functioning areas and up to two red notes next to acute operational friction points. ### 5. Debrief and select priorities (10 minutes) Gather the whole room. Have each group share their top operational strength and their primary constraint. Run a short whole-room debrief using the provided questions. ## Debrief questions - Which collaborator group has the clearest operational connection to design, and which is most ambiguous? - Where are red constraint flags clustering on the canvas? - What is one immediate change to our operating practices that would remove a highlighted constraint? **Finished output:** A completed Design Operations Canvas poster documenting collaborator groups, delivery services, supporting practices, and tagged operational bottlenecks. ## Remote Set up a digital whiteboard with the four canvas zones marked. Assign each participant a dedicated sticky note color for their collaborator types. Run silent drafting in parallel, then use voice turns to cluster. Use virtual green and red tags for the assessment step. ## Hybrid Pair in-person and remote participants at the same digital board so physical attendees do not create an offline parallel version. Designate an in-room participant to echo physical room questions into the shared meeting audio. ## Access and participation choices - Provide high-contrast markers and allow using typed digital stickies or marked symbols (+ and -) instead of relying solely on color recognition. - Participants may choose to observe silently or write private notes during drafting without posting every item. ## If the session gets stuck **Participants write broad aspirations instead of current working reality.** Prompt them to document only services and tools that were actively used within the last 30 days. **Disagreements arise about whether a service is actually delivered effectively.** Instruct the team to place the service card in the middle section and flag it with a red assessment note for discussion during debrief. ## Terms used here - Design Ops: The organizational practices, workflows, and tools that support design teams in delivering their work efficiently. ## Sources and adaptation Observed in Gamestorming (mapping-design-operations), referencing the Design Operations Canvas. Retained the 5-step sequence from Gamestorming: mapping stakeholders, value propositions, operational blocks, constraints, and green/red assessment. UWT structured the timing into a 60-minute session, added concrete grouping rules, hybrid accommodations, and a neutral debrief structure. [gamestorming.com](https://gamestorming.com/mapping-design-operations) Current run sheet: https://unitedwetransform.com/exercises/mapping-design-operations/
Sources and adaptation
Observed in Gamestorming (mapping-design-operations), referencing the Design Operations Canvas.
Retained the 5-step sequence from Gamestorming: mapping stakeholders, value propositions, operational blocks, constraints, and green/red assessment. UWT structured the timing into a 60-minute session, added concrete grouping rules, hybrid accommodations, and a neutral debrief structure.
See our editorial policy for AI use, sourcing and corrections.