User Context Modelling

Purpose

Map the situational, temporal, environmental, social, and emotional conditions under which a validated need manifests with varying intensity. Identify critical design contexts — the 1–3 high-intensity scenarios where the future innovation must perform flawlessly — and derive design parameters for A2 ideation and A6–A7 validation testing.

When to use

A1.4 Step~3 (User Context Modelling), after reviewing A1.2 journey maps and empathy maps. Extends A1.2's pain-point identification into systematic contextual analysis.

Output

User Context Model: 3–5 context scenarios (tabular), context dimensions matrix, critical design context designation with justification, design parameters for A2 ideation.

Inputs

• A1.2 journey maps and empathy maps
• A1.3 Problem Definition Brief (contextual boundaries)
• User interview access (4–6 need experiencers)

Procedure

1. Review A1.2 evidence. Identify where on the user journey the need spikes in intensity. Note emotional and social contexts from empathy maps.
2. Map context dimensions. Systematically explore need manifestation across seven dimensions: itemize
3. Temporal: when does need peak? (time of day/week/ month/year, deadline-driven spikes)
4. Situational: what triggers or amplifies need? (stress, complexity, uncertainty, visibility)
5. Environmental: where does need manifest? (physical constraints: connectivity, noise, privacy)
6. Social: who is present? (solo, team, manager, customer-facing; social pressures)
7. Expertise: does intensity vary by user skill level?
8. Emotional: what emotional states accompany need? (cognitive load, decision fatigue)
9. Informational: what data/resources are available or missing in this context? itemize
10. Conduct context interviews (4–6 users). Semi-structured interviews: “Tell me about the last 3 times you experienced [need]. For each: When? Where? Who else? What made it especially painful? How did you cope?” Then: “Think of the worst-case scenario — maximum pain. What made it worst?”
11. Construct context scenarios (3–5). For each identified scenario: name, temporal/environmental/ social description, need intensity rating (Low/Medium/High/ Critical), amplifying factors, current coping mechanisms and their limitations.
12. Designate critical design context(s). Select 1–3 scenarios where the innovation MUST work. Selection criteria: highest intensity, highest frequency among critical moments, or highest strategic importance. Apply downward adaptability principle: design for the hardest context; simplify for easier ones.
13. Derive design parameters. From the critical design context, extract specific design requirements (e.g., “must function with 70–80% data completeness,” “must complete core task in <5 minutes,” “must support interrupted workflow”).

Quality criteria

• ≥5 of 7 context dimensions explored
• Context scenarios grounded in user interviews (not hypothesised)
• Critical design context selection uses intensity logic, not volume logic
• Design parameters are specific and testable (not generic “make it fast”)

Common errors

• Volume = criticality — selecting the most frequent scenario rather than the most intense
• Generic context — “user at their desk” contains no actionable design intelligence
• Hypothesised contexts — assuming contexts without interview evidence
• Too many critical contexts — designating 4–5 as “critical” dilutes focus; limit to 1–3

Theoretical basis

Jobs-to-be-Done Theory (Christensen et al., 2016; Ulwick, 2005). JTBD emphasises that context (when, where, why the job arises) is as important as the functional job itself.