part two · person & moment
Person & Moment
Naming who has the problem and when it happens.
The chain is built on two named things — a person and a moment. Both are specific. Both are the team's first commitment to honesty.
The person
Not the user. Never the user. A named individual.
- Dina, 34, secondary-school teacher in Tel Aviv, fluent in Hebrew and English, six classes a week.
- Miri, customer service lead at a regional water utility, twelve direct reports, in the role for nine years.
- Avi, a field service technician with four jobs a day across Beersheba and Ashdod, never in the office.
The name is not decoration. The name is the constraint. We are building this for Dina leads to a different decision than we are building this for teachers. The first names a real person whose life can be changed. The second names a market — and a market cannot be observed.
The corpus rule: every brief begins with a named person whose life will change. If the team cannot name the person, the team has not done Discovery. Substituting a persona — Teacher Tina, age 30–45, time-pressured — is not the same. A persona is an aggregate. The chain is built around an individual.
Aggregating without losing the person
Personas have a place. They are a useful summary across many named people. But they are downstream of named people, not upstream. The corpus pattern:
- Observe several named people doing the same activity.
- Write each of their stories in their own words.
- Surface the patterns across the named stories.
- Build the persona, with a footnote pointing back at the named people.
A persona that does not point back at named people will drift. Six months later, the persona has different concerns than the people had when it was first written, and no one can tell why.
The moment
The specific point in the activity where the friction or failure occurs. Not the average experience — the actual one, with timing.
- Dina's moment: Sunday morning, 7:15am, the first cup of coffee, opening the LMS to plan the week. The system loads, three notifications appear, none of them are about the lesson she is preparing.
- Miri's moment: Monday 11:00am, on a call with an angry customer, trying to find the previous case notes while keeping the customer talking, in three different systems.
- Avi's moment: 7:45am, in the van, twenty minutes from the first job, looking at the work order on his phone, missing the part the customer described.
The moment makes the brief writable. Dina struggles with planning is unwritable. Sunday morning, 7:15am, opening the LMS, the first thing she sees is not what she came in for is writable. The Discovery moment is what the brief's prediction is anchored to.
The pattern of moments
Most activities have several friction points. The first Discovery pass surfaces the most painful one — the one the person remembers without being asked. The second pass surfaces the others — the ones they have stopped noticing.
The corpus pattern: pick one moment to anchor the brief, and list the others in the assumption space. The brief is about the chosen moment. The future cycles will return to the others.
How person and moment relate to scope
The person sets the constraint on who. The moment sets the constraint on when. Together they bound what.
A feature that improves Dina's Sunday morning planning is a different feature than one that improves Dina's mid-week emergency lesson swap. The first lives inside one cycle. The second lives inside another. Trying to do both at once produces a feature that does neither well.
Multiple people, multiple moments
Real activities involve more than one person. The grading flow has Gal (the grader) but also the student, the head of department, and the IT admin. Each is a person. Each has moments.
The corpus pattern: the brief names one primary person and one primary moment and lists the secondary persons and moments at the foot. Scope is set against the primary. The secondary persons are remembered, not centred. They become the centre of their own future briefs.