United We TransformCreate teamsGrade your agenda
Exercises/Context Sharing/Card Prompt Mapping
Relationship Mapping ยท Context Sharing

Card Prompt Mapping

Small groups lay out topic prompt cards, cluster them into themes, and record their team's specific context around each element. The result is a shared visual map of the project scope with concrete notes on priorities and blind spots.

15 minutesTIME
4 to 24 peopleGROUP SIZE
In person, Remote, HybridSETTING
4 materialsMATERIALS
Planning pillar: Personalization UWT groups this context sharing activity under Personalization in its Gathering Effectiveness planning framework.

Choose this exercise

Purpose: Map the parts of a project or topic together so participants align on shared terminology and current context.

Use it when: Use at project kickoff or sprint planning when a team needs to define scope across multiple angles without starting from a blank page.

Skip it when: Skip when the meeting requires a quick binary decision or when a structured backlog already defines all immediate work.

Group arrangement: Table groups of 3 to 5 participants working in parallel

Timing: 15 minutes suggested by UWT based on the 6 standard MethodKit conversation patterns (discuss, map, sort, brainstorm, prioritize, develop)

Materials and tools

Before participants arrive

  1. Print and cut one set of Project Building Blocks cards for each table.
  2. Place card sets, sticky notes, and pens in the center of each small group table.
  3. Clear table space so cards can be spread out flat.

Say this to open

Most planning sessions start from zero. Today we will use concept prompt cards to pull context out of our heads and onto the table. Each card represents one angle of our project. In small groups, you will spread the cards out, select the ones relevant to our current work, cluster them into themes, and add sticky notes showing our current reality for each card.

How to run it

  1. Introduce and spread cards 3 minutes

    Deliver opening script. Direct tables to divide into groups of 3 to 5. One person at each table spreads the card deck face up so every card title is visible. Participants review cards silently.

  2. Select and cluster themes 4 minutes

    Table members sort cards into three piles: Relevant Now, Relevant Later, and Not Applicable. Move the Relevant Now cards to the center. Group these selected cards into 2 to 4 thematic clusters.

  3. Annotate current context 5 minutes

    Participants write short notes on sticky notes (one fact, constraint, or decision per note) and attach them directly next to the corresponding card. For example, next to 'Target Audience', write 'Junior developers onboarding this quarter'.

  4. Debrief and capture 3 minutes

    Ask groups to pause. Take a photo of each table's mapped arrangement. Hear brief observations from two tables on key discoveries or blind spots surfaced by the cards.

Debrief questions

Finished output: A photographed tabletop card map with sticky notes capturing the group's agreed project elements and context.

Remote

Set up a shared digital whiteboard (such as Miro or Mural) with each card title represented as a digital rectangle. Place small groups in breakout rooms of 3 to 5 people. Groups drag cards into columns (Relevant Now, Later, Not Applicable) and attach digital sticky notes beside them. Breakouts return to main room at minute 12.

Hybrid

In-person members gather around a physical table while remote members join a breakout room with a digital board containing identical card titles. Appoint one in-person scribe to take a mid-point photo and post it to the remote group's channel, or maintain two separate maps that are compared in the final debrief.

Access and participation choices

If the session gets stuck

Groups spend all their time debating whether a single card is relevant.
Remind tables that cards can be placed on the border between Now and Later. Tell them to log the disagreement on a sticky note and move to the next card.
One dominant participant dictates card placement for the entire table.
Ask each participant to pick two cards they personally consider vital, place them on the table, and explain why before open clustering begins.

Terms used here

Project Building Blocks (Printable Card Deck)

Target AudienceProblem StatementCore Value PropositionKey ConstraintsTimeline & MilestonesBudget & ResourcesSuccess MetricsDependenciesTechnical ArchitectureCommunication ChannelsRegulatory & LegalUser Feedback ChannelsTeam Roles & OwnershipLaunch StrategyRisks & UnknownsMaintenance & Handoff
Live facilitator

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.

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: d7ac66a10e9418225747a632273a0d6d7cd5450f6f0e32f62610ca06e4cdef83

# Card Prompt Mapping

Small groups lay out topic prompt cards, cluster them into themes, and record their team's specific context around each element. The result is a shared visual map of the project scope with concrete notes on priorities and blind spots.

**Time:** 15 minutes. 15 minutes suggested by UWT based on the 6 standard MethodKit conversation patterns (discuss, map, sort, brainstorm, prioritize, develop)
**People:** 4 to 24. Table groups of 3 to 5 participants working in parallel

## Choose this exercise

**Purpose:** Map the parts of a project or topic together so participants align on shared terminology and current context.
**Use it when:** Use at project kickoff or sprint planning when a team needs to define scope across multiple angles without starting from a blank page.
**Skip it when:** Skip when the meeting requires a quick binary decision or when a structured backlog already defines all immediate work.

## Materials and tools

- One deck of topic cards (or the provided printable Project Building Blocks) per table
- One pad of 3x3 inch sticky notes per table
- One fine-tip marker per participant
- Tabletop space or wall space for each small group

## Before participants arrive

1. Print and cut one set of Project Building Blocks cards for each table.
2. Place card sets, sticky notes, and pens in the center of each small group table.
3. Clear table space so cards can be spread out flat.

## Say this to open

Most planning sessions start from zero. Today we will use concept prompt cards to pull context out of our heads and onto the table. Each card represents one angle of our project. In small groups, you will spread the cards out, select the ones relevant to our current work, cluster them into themes, and add sticky notes showing our current reality for each card.

## How to run it

### 1. Introduce and spread cards (3 minutes)

Deliver opening script. Direct tables to divide into groups of 3 to 5. One person at each table spreads the card deck face up so every card title is visible. Participants review cards silently.

### 2. Select and cluster themes (4 minutes)

Table members sort cards into three piles: Relevant Now, Relevant Later, and Not Applicable. Move the Relevant Now cards to the center. Group these selected cards into 2 to 4 thematic clusters.

### 3. Annotate current context (5 minutes)

Participants write short notes on sticky notes (one fact, constraint, or decision per note) and attach them directly next to the corresponding card. For example, next to 'Target Audience', write 'Junior developers onboarding this quarter'.

### 4. Debrief and capture (3 minutes)

Ask groups to pause. Take a photo of each table's mapped arrangement. Hear brief observations from two tables on key discoveries or blind spots surfaced by the cards.


## Debrief questions

- Which card triggered the most discussion or revealed an unspoken assumption?
- What important project element was in the Relevant Later pile that someone expected in Relevant Now?
- How did mapping these elements change your view of our immediate priorities?

**Finished output:** A photographed tabletop card map with sticky notes capturing the group's agreed project elements and context.

## Remote

Set up a shared digital whiteboard (such as Miro or Mural) with each card title represented as a digital rectangle. Place small groups in breakout rooms of 3 to 5 people. Groups drag cards into columns (Relevant Now, Later, Not Applicable) and attach digital sticky notes beside them. Breakouts return to main room at minute 12.

## Hybrid

In-person members gather around a physical table while remote members join a breakout room with a digital board containing identical card titles. Appoint one in-person scribe to take a mid-point photo and post it to the remote group's channel, or maintain two separate maps that are compared in the final debrief.

## Access and participation choices

- Provide large-print card text for participants with visual strain.
- Participants may contribute by writing sticky notes, moving physical cards, or speaking observations.
- Anyone may choose to observe silently or pass on verbal reporting during debrief.

## If the session gets stuck

**Groups spend all their time debating whether a single card is relevant.**

Remind tables that cards can be placed on the border between Now and Later. Tell them to log the disagreement on a sticky note and move to the next card.

**One dominant participant dictates card placement for the entire table.**

Ask each participant to pick two cards they personally consider vital, place them on the table, and explain why before open clustering begins.


## Terms used here

- Prompt card: A physical or digital card showing a single concept or domain element used to stimulate focused discussion.

## Participant material: Project Building Blocks (Printable Card Deck)

Target Audience
Problem Statement
Core Value Proposition
Key Constraints
Timeline & Milestones
Budget & Resources
Success Metrics
Dependencies
Technical Architecture
Communication Channels
Regulatory & Legal
User Feedback Channels
Team Roles & Ownership
Launch Strategy
Risks & Unknowns
Maintenance & Handoff

## Sources and adaptation

Observed in MethodKit workshop materials and product descriptions (MethodKit, 2012-2026), describing cards used for mapping, sorting, prioritizing, and discussing shared context.

Retained the defining MethodKit mechanic of using topic prompt cards to establish a shared language through sorting, mapping, and annotating. Added a specific 15-minute 4-step facilitation sequence, subgroup sizing, access accommodations, and a neutral 16-item Project Building Blocks card deck template to make the activity fully runnable from the page.

[MethodKit](http://www.methodkit.com/shop/methodkit-with-trends/)

[MethodKit](http://www.methodkit.com/shop/methodkit-with-tech-building-blocks/)

[MethodKit](http://www.methodkit.com/shop/methodkit-with-human-needs/)

[MethodKit](https://methodkit.com/author/methodkitadmin/)

Current run sheet: https://unitedwetransform.com/exercises/methodkit-methodkit/

Sources and adaptation

Observed in MethodKit workshop materials and product descriptions (MethodKit, 2012-2026), describing cards used for mapping, sorting, prioritizing, and discussing shared context.

Retained the defining MethodKit mechanic of using topic prompt cards to establish a shared language through sorting, mapping, and annotating. Added a specific 15-minute 4-step facilitation sequence, subgroup sizing, access accommodations, and a neutral 16-item Project Building Blocks card deck template to make the activity fully runnable from the page.

See our editorial policy for AI use, sourcing and corrections.

Pairs well with