methodatlas
Session Builder

Plan my session

Plan a concrete work block with agenda, roles, preparation, and a copyable result artifact.

Method session30-45 minWorkshop or asyncContent groups

Session: Card Sorting

The plan translates the method into a concrete facilitated work block. Your inputs flow directly into the session brief and work artifact.

Derived automatically

Method session with 5-15. The plan uses the existing method logic and the runsheet.

Runsheet
Participation logic
Team round, shared work and alignment

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome logic
Finish artifact

The session works directly toward Content groups. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    0-5 min

    5 min

    Explain the item set, the goal, and the sort mode. Make sure everyone understands whether the sort is open or closed. Hint: If the sort mode is unclear, participants will invent different rules. State the mode before the first card is moved.

    FacilitatorContent groups
  2. 2

    5-15 min

    10 min

    Let participants move cards into groups or categories. Observe patterns, hesitation, and cards that are difficult to place. Hint: Do not guide the grouping too early. The point is to learn the user's mental model, not to coach the result.

    FacilitatorLabel set
  3. 3

    15-25 min

    10 min

    Review the clusters, ask for labels, and capture why certain items were grouped together or kept apart. Hint: Ambiguous labels are often more valuable than perfect agreement. Record the uncertainty instead of forcing a false consensus.

    FacilitatorIA hypotheses
  4. 4

    25-35 min

    10 min

    Compare the results across participants, highlight stable clusters, and mark items with inconsistent placements. Hint: Look for patterns, not just majority votes. Repeated disagreements are clues for weak labels or a wrong taxonomy.

    FacilitatorContent groups
  5. 5

    35-45 min

    10 min

    Translate the findings into navigation or label hypotheses and note which items need a second test such as tree testing. Hint: A sort result is a hypothesis, not the final IA. Always end with the next validation step.

    OwnerLabel set
  6. 6

    Publish artifact

    10 min

    Check the artifact for completeness, define location, set version or status, and name review recipients.

    OwnerContent groups
Usable artifact

Session Brief

For invitations, boards, tickets, PR descriptions, or workshop notes.

session-brief.md

Session Brief: Card Sorting

Goal

Artifact: Content groups

Working Question

How do people naturally group and label these items?

Context

Target audience, list of content items, and the decision to run an open or closed sort; any existing navigation or taxonomy assumptions.

Setup

  • Format: Method session
  • Duration: 30-45 min
  • Mode: Workshop or async
  • Participants: One facilitator; five to fifteen participants or test users; one observer or note taker; optionally one person who watches for label ambiguity.
  • Owner: One facilitator
  • Participation mode: Team round, shared work and alignment
  • Outcome logic: Finish artifact

Participation Logic

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome Logic

The session works directly toward Content groups. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Card set or digital sorting board; label stickers or text cards; timer; notes for clusters and edge cases; camera or export tool.

Preparation

Prepare one card per item. Keep the wording short and consistent. Decide in advance whether participants create their own labels or sort into predefined groups.

Agenda

  1. 0-5 min (5 min) Owner: Facilitator Action: Explain the item set, the goal, and the sort mode. Make sure everyone understands whether the sort is open or closed. Hint: If the sort mode is unclear, participants will invent different rules. State the mode before the first card is moved. Output: Content groups

  2. 5-15 min (10 min) Owner: Facilitator Action: Let participants move cards into groups or categories. Observe patterns, hesitation, and cards that are difficult to place. Hint: Do not guide the grouping too early. The point is to learn the user's mental model, not to coach the result. Output: Label set

  3. 15-25 min (10 min) Owner: Facilitator Action: Review the clusters, ask for labels, and capture why certain items were grouped together or kept apart. Hint: Ambiguous labels are often more valuable than perfect agreement. Record the uncertainty instead of forcing a false consensus. Output: IA hypotheses

  4. 25-35 min (10 min) Owner: Facilitator Action: Compare the results across participants, highlight stable clusters, and mark items with inconsistent placements. Hint: Look for patterns, not just majority votes. Repeated disagreements are clues for weak labels or a wrong taxonomy. Output: Content groups

  5. 35-45 min (10 min) Owner: Owner Action: Translate the findings into navigation or label hypotheses and note which items need a second test such as tree testing. Hint: A sort result is a hypothesis, not the final IA. Always end with the next validation step. Output: Label set

  6. Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: Content groups

Closeout

  • Update result artifact: Content groups
  • Define location, version, and review recipients.
  • Define owner, next step, and review date.
Usable artifact

Work artifact

Pre-filled starting point based on the matching template.

work-artifact.md

Content groups: Card Sorting

Working Question

How do people naturally group and label these items?

Context

Target audience, list of content items, and the decision to run an open or closed sort; any existing navigation or taxonomy assumptions.

Participants

  • Owner: One facilitator
  • Participants: One facilitator; five to fifteen participants or test users; one observer or note taker; optionally one person who watches for label ambiguity.

Input

Card set or digital sorting board; label stickers or text cards; timer; notes for clusters and edge cases; camera or export tool.

Template

Card Sorting Working Template

Goal

Shows how users group and label content.

Context

When and for what do we use this method?

Input

Which data, observations, decisions, or materials are available?

Execution

Short notes along the runsheet.

Output artifacts

  • Content Groups:
  • Label Set:
  • IA Hypotheses:

Assumptions and open questions

  • ...

Decision / Next step

Owner, date, and success signal.

Completion Check

  • Content groups is complete enough for review:
  • Location:
  • Version / status:
  • Review by:
  • Next step:

Next Step

  • Review result
  • Mark open questions
  • Schedule review or decision
Template base

Card Sorting Working Template

View templateCompact working template for Card Sorting with context, input, output artifacts, and next step.
markdown

card-sorting-working-template.md

Compact working template for Card Sorting with context, input, output artifacts, and next step.

Card Sorting Working Template

Goal

Shows how users group and label content.

Context

When and for what do we use this method?

Input

Which data, observations, decisions, or materials are available?

Execution

Short notes along the runsheet.

Output artifacts

  • Content Groups:
  • Label Set:
  • IA Hypotheses:

Assumptions and open questions

  • ...

Decision / Next step

Owner, date, and success signal.

Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits Content groups.
  • Record date, target audience, and sort mode. Keep separate versions for open and closed sorts, and note which items changed between runs.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet