Party Invitations

Choose this exercise

Purpose: Translate onboarding and initial user engagement requirements into concrete expectations using the metaphor of hosting a social gathering.

Use it when: Use when designing onboarding flows, first-time user experiences, or welcome communications that currently feel vague, technical, or cold.

Skip it when: Skip when the service context is purely transactional, regulatory, or hostile, where social hospitality metaphors distract from legal or technical constraints.

Group arrangement: Solo drafting, followed by triads or quads (pairs if 4 or 5 total), concluding with whole-room synthesis.

Timing: Gamestorming lists 30 to 60 minutes. 45 minutes provides 5 minutes of introduction, 12 minutes of solo writing, 13 minutes of subgroup comparison, and 15 minutes of onboarding synthesis.

Materials and tools

• Blank sheets of paper (at least 2 sheets per participant)
• Markers or pens (1 per participant)
• Wall tape or pushpins to hang subgroup summary sheets
• Whiteboard or flip chart with dry-erase markers

Before participants arrive

1. Write the target product, service, or process clearly at the top of the whiteboard.
2. Set up three columns on the main whiteboard: Party Metaphor Element, Onboarding Reality, and Design Actions.
3. Place blank paper and markers at every seat.

Say this to open

Think about the first time someone encounters our offering. Imagine that this product or service is actually a real-life party or event, and you must write the invitation to get people there. On your paper, write an invitation that specifies the name of the gathering, dress code, what guests need to bring, what the host provides, directions to get there, and RSVP requirements. Be as specific and realistic as possible.

How to run it

1. Introduce the party metaphor 5 minutes

   Speak the opening script. Clarify the target offering. Give one neutral example: a developer tool might be framed as a late-night hackathon where the host supplies pizza and power cords while guests bring their own laptops and credentials. Point out that tone can range from a backyard potluck to a formal gala depending on perception. State that everyone drafts solo first.

2. Draft individual invitations 12 minutes

   Participants work quietly on paper to draft their invitation. Prompt them to include concrete details: who is invited, dress code, location, arrival instructions, refreshments, what guests must bring, and what the host provides. Participants may rewrite or refine their draft as ideas evolve. Stop when time expires.

3. Compare elements in small groups 13 minutes

   Form groups of 3 to 4. For 4 or 5 total participants, use one or two pairs. For groups with odd remainders (such as 13 or 17), make one group of 5 or allow a trio. Direct groups to review invitations element by element: party name, dress code, guest burden versus host supplies, and arrival steps. Each group records key contrasts on one summary sheet (or directly on the shared digital board for remote and hybrid rooms). Have each in-person group tape their summary sheet next to the main whiteboard.

4. Map invitation details to onboarding realities 15 minutes

   Bring the room together facing the main whiteboard, using the pre-drawn columns: Party Metaphor Element, Onboarding Reality, and Design Actions. Pull 1 to 2 contrast examples from the posted group sheets for each element (dress code, arrival directions, host provisions). Facilitate translating these metaphors into design decisions: What does 'bring your own food' mean for user data entry? What does 'black tie' say about barrier to entry? Fill in concrete agreements in the Design Actions column. Up to 6 group contributions fit this debrief window.

Debrief questions

• What did our different dress codes or themes reveal about how approachable or intimidating our offering currently feels?
• What burden did your invitation ask guests to bring, and can the host provide more of that instead?
• Which specific line from today's invitations should become part of our real welcome messaging or onboarding steps?

Finished output: A three-column whiteboard map translating party metaphors into onboarding realities and concrete design actions, supported by posted subgroup contrast sheets.

Remote

Participants write solo on paper or in personal notes. Send groups into breakout rooms of 3 to 4 to compare elements and record their key contrasts on a shared digital whiteboard. Convene in the main room and transcribe selected points into a three-column digital board for whole-room synthesis.

Hybrid

In-person participants form groups locally and remote participants work in a dedicated breakout room. Both in-person and online groups type or paste their contrast notes into a shared digital board displayed in the physical room. The facilitator alternates between an in-person table and a remote speaker when mapping points into the three columns.

Access and participation choices

• Participants may sketch an invitation card visually, write plain bullet points, or type notes on a personal device.
• Anyone may choose not to read their own draft aloud; non-sharing participants can act as the small-group scribe who records contrasts on the summary sheet.

If the session gets stuck

Participants write generic marketing copy rather than a party invitation.

Remind them to use party mechanics: specify actual clothes, food, arrival doors, and host responsibilities.

Discussions stall on literal party details instead of connecting back to the product.

Intervene and ask: If your party requires a secret password at the door, what does that mean for our user sign-up or verification step?

Terms used here

• Onboarding: The series of initial interactions, explanations, and setup steps a new user experiences when starting with a product or service.