United We Transform | Facilitator run sheet

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.

60 minutes | 3 to 18 people

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

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

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

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

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.