Time
Four touchpoints, 20–30 min each
People
Core team, plus stakeholders in framing

Overview

The spine of a Kairos discovery. You start with a rough guess at what users are trying to get done and sharpen it four times as evidence arrives. It is the same board section each time, not a new artifact — the value is in seeing the list change. The Discovery Introduction puts it plainly: the exercise frames the user’s task together with their motivation and desired outcomes, to support prioritisation.

  • When to use it.

    At all four phase touchpoints, detailed below. If you only do it once, do it in framing, where it is prioritised against the problem statement in its own scope-prioritisation workshop.

  • Who to involve.

    The core team throughout. Bring stakeholders in for the framing workshop, since that is where scope gets debated. The concept discovery and validation touchpoints work better small.

  • Effort.

    Low prepMedium engagement

    Set the board up once; after that each touchpoint is a working session rather than a workshop.

  • Outcomes.

    A list of jobs the team agrees on, sharpening each time, ending as a now / next / later prioritisation at handover. Along the way it produces the success metrics for each concept.

  • Recommendations.

    Keep one board, not four — duplicate the frame if you want a record of each phase, but work in the same place, because the comparison is the point. Write jobs, not features: “confirm a technician is qualified before dispatching” is a job; “certification filter on the dispatch board” is a solution wearing a job’s clothes. And resist making it look finished in pre-framing. Early JTBDs are meant to be wrong.

The four touchpoints

PhaseWhat happens hereEffort
Pre-framingDraft assumed JTBDs from stakeholder input, to sharpen the discovery brief~20 min, self-⁠paced
FramingJTBD scope-prioritisation workshop, aligned to the problem statementPart of the framing workshop
Concept discoveryRefine JTBDs and formulate success metrics per concept30 min group session
Concept validationRefine JTBDs and prioritise into now / next / later ahead of handoverPart of the validation readout