By the end of this topic, you should be able to...
create a primary persona or personae based on user-centred research to aid design development.
Guiding Question
How does understanding user needs directly impact the design of products and services?
The Persona — From Research to Design Tool
The persona is the intellectual pivot point of user-centred design. It is the moment when raw, fragmented research data — interview transcripts, observation notes, questionnaire statistics, demographic distributions — is synthesised into a singular, coherent, human portrait that the design team can use as a reference point throughout every stage of development.
The concept was formalised by interaction designer Alan Cooper in his landmark text The Inmates Are Running the Asylum (1999), where he argued that designing for abstract "users" was designing for nobody:
"Personas are not real people, but they represent real people throughout the design process. We use them to make design decisions without having to interview a user at every stage."— Alan Cooper, The Inmates Are Running the Asylum, 1999
The IBO Design Technology Guide (First Assessment 2025) positions persona creation at the intersection of research and design development — it is simultaneously the final act of analysis and the first act of design thinking.
What a Persona Is — and Is Not
Before constructing a persona, it is essential to understand what the tool is — and what it is not:
A Persona IS | A Persona IS NOT |
A composite portrait derived from research data across multiple users | A description of a single real user |
A design reference tool used to make decisions | A marketing demographic (age/gender category) |
Based on observed behaviours, motivations, and goals | Based on designer assumptions |
Specific and concrete — named, humanised | Vague and generic — "any young adult" |
Grounded in data — every attribute traceable to a research finding | Invented without research evidence |
A tool for resolving design conflicts by asking "what would this person need?" | A tool for justifying decisions already made |
Critical IB point: A persona constructed without research evidence is not a UCD tool — it is designer bias with a name and a face attached to it. Examiners will look for evidence that your persona attributes are traceable to your research data.
The Anatomy of a Primary Persona
A well-constructed primary persona contains several interconnected layers of information, each serving a distinct purpose in design development:
Layer 1: Identify and Demographics
Why demographics matter:Demographic data establishes the physical, cognitive, and contextual parameters within which the design must operate. A 34-year-old urban professional does not share the same physical capability, digital literacy, time constraints, or purchasing behaviour as a 72-year-old rural retiree. Every demographic variable is a potential design constraint or opportunity.
The IBO Design Technology Guide (First Assessment 2025) explicitly requires that the target population be defined by their demographics — the persona is the mechanism through which that demographic definition becomes a person rather than a category.
Layer 2: Behavioural Profile
This is the most research-critical layer of the persona — the one most likely to differ from designer assumptions and most likely to drive genuine insight.
Behavioural variables to map include:
Behavioural Variable | What It Reveals for Design |
Task frequency — how often do they perform the relevant activity? | Informs whether design prioritises learning curve or efficiency |
Skill level — novice, intermediate, expert? | Determines appropriate complexity and feedback mechanisms |
Technology adoption — early adopter or late majority? | Shapes interface conventions and instruction requirements |
Social context of use — alone, in groups, in public? | Influences privacy, shareability, and social features |
Time pressure — is this activity rushed or leisurely? | Affects acceptable interaction time and error tolerance |
Physical context — seated, standing, moving? | Determines ergonomic, environmental, and portability requirements |
Layer 3: Goals
Goals are the most design-generative layer of a persona. Cooper distinguishes between three levels of user goals, each operating at a different scale:
Design principle: A product that satisfies only end goals without addressing life goals and experience goals will be functionally adequate but emotionally unsatisfying — and users will replace it when an alternative appears that addresses all three levels.
Layer 4: Pain Points and Frustrations
Pain points are the specific moments of friction, failure, or frustration that users currently experience in the context your design is addressing. They are derived primarily from interview data and observation findings.
Pain points should be stated in the user's own language where possible — this preserves the authentic voice of the research and prevents designer reinterpretation.
IB assessment note: The direct citation of research evidence within the persona documentation is precisely what distinguishes a research-derived persona from a speculative persona. This is where Criterion A analysis marks are earned.
Layer 5: Motivations and Values
Motivations explain why users behave as they do — the underlying drivers that shape product engagement, adoption, and sustained use.
Motivation categories relevant to product design:
Motivation Category | Example | Design Response |
Achievement | Tracking progress toward a goal | Progress indicators, milestone rewards |
Social connection | Sharing outcomes with others | Sharing functions, community features |
Autonomy | Control over process and pace | Customisation options, manual overrides |
Mastery | Becoming progressively more skilled | Graduated complexity, skill-building pathways |
Security | Avoiding risk and error | Confirmations, undo functions, auto-save |
Efficiency | Minimising time and effort | Shortcuts, defaults, batch operations |
Layer 6: The Scenario Narrative
The scenario is a short narrative passage that places the persona in a realistic context of use, illustrating how their goals, behaviours, and pain points interact in a real situation. It is the most humanising element of the persona document.
Example scenario: "It is 6:45am on a Wednesday. Marcus is standing in his kitchen, half-dressed, eating breakfast while his daughter watches television. He has 45 minutes before he needs to leave for school. He picks up his tablet to finalise the resource sheet he started last night. The application requires him to log in again — he cannot remember which email address he used to register. By the time he has recovered his credentials, he has 25 minutes left. He completes the resource but cannot find the export function — the icon is unlabelled. He gives up on exporting and screenshots the page instead. He arrives at school with a blurry, uncropped image instead of a clean resource sheet."
This scenario is not creative writing — every detail is derived from research data: observation sessions revealed credential confusion; interview data identified export function difficulty; questionnaire data confirmed time pressure as the dominant constraint. The scenario makes the data human.
Layer 7: The Persona Photograph
The persona should include a representative photograph — not of a real research participant (for privacy reasons) but a stock image that visually represents the demographic profile. The visual component is not decorative — it serves a cognitive function: it gives the design team a face to consider when making decisions, activating the empathy that abstract demographic data cannot.
"The photograph transforms 'the user' from an abstraction into a person. Designers make different — and better — decisions when a face is present."— Pruitt, John, and Tamara Adlin. The Persona Lifecycle: Keeping People in Mind Throughout Product Design. Morgan Kaufmann, 2006.
The Persona Construction Process — Step by Step
The persona is not produced in one step — it is the output of a rigorous analytical process that begins with raw data and proceeds through synthesis to portrait:
Step 1: Data Consolidation
Gather all research outputs — interview transcripts, observation field notes, questionnaire response data — into a single workspace.
Step 2: Behavioural Variable Mapping
Identify the key behavioural dimensions relevant to your design context and plot each research participant against those dimensions. This reveals clusters of behaviour — groups of participants who share similar patterns.
Step 3: Identifying the Primary Persona
The primary persona represents the largest, most critical user cluster — the group whose needs are most central to the design challenge. The primary persona is the user whose needs must be fully satisfied for the design to succeed.
If satisfying another persona's needs would compromise satisfaction of the primary persona, the primary persona's needs take precedence in design decisions. This is Cooper's fundamental contribution to design methodology — establishing a hierarchy of users prevents the "design for everyone" trap that produces products that satisfy nobody.
"Designing for the broadest possible audience almost guarantees you will satisfy no single user. The primary persona forces precision."— Cooper, Alan. The Inmates Are Running the Asylum. SAMS, 1999.
Step 4: Thematic Extraction per Cluster
For the identified primary persona cluster, extract:
The shared behavioural patterns across cluster members
The shared goals — what all cluster members were trying to achieve
The shared pain points — where all cluster members encountered friction
The range of demographic attributes within the cluster — construct a composite
Step 5: Personal Portrait Construction
Assemble the extracted attributes into the persona document using the layers described above. Every attribute must be traceable to a specific research finding.
Step 6: Scenario Writing
Write the scenario narrative using the consolidated data. The scenario should:
Take place in the realistic context of use identified by field research or observation
Demonstrate the primary end goal in action
Include at least one current pain point
Establish the emotional register — how does the persona feel during this experience?
Step 7: Design Implication Extraction
For each pain point, goal, and behavioural attribute in the persona, extract a corresponding design implication.
This step is where the persona earns its value as a design development tool — it converts human data into actionable design parameters.
Primary vs. Secondary Personas
The IBO Design Technology Guide (First Assessment 2025) refers to a primary persona — it is important to understand this in relation to other persona types:
Persona Type | Description | Design Role |
Primary | The most critical user — whose needs must be fully satisfied | All core design decisions must satisfy this persona |
Secondary | A real but less central user — whose primary needs are met by the primary persona design, with minor adjustments | Considered after primary persona needs are met |
Supplemental | Users whose needs are already satisfied by decisions made for primary and secondary | Checked for exclusion, not designed for specifically |
Negative / Anti-persona | A user the product is explicitly NOT designed for | Prevents scope creep and feature bloat |
IB note: For most IA projects, a single well-researched primary persona is more valuable than three superficial personas. Depth of research evidence and clarity of design application are what generate marks — not quantity of personas.
How Personas Aid Design Development
The persona is not a research deliverable to be submitted and forgotten. Its value lies entirely in how it is used throughout the design process:
Resolving Design Decisions
When two design options are under consideration, the persona provides the deciding framework:
"Option A has a larger button target area but requires an extra screen tap to reach the core function. Option B has a smaller target but reduces the pathway to one tap. Marcus is frequently using this product while standing, in a hurry, in morning light. Option B serves Marcus."
Scoping Features
The persona prevents feature creep — the tendency to add features because they are technically possible rather than because users need them:
"This feature would be used by power users only — it does not appear anywhere in Marcus's scenario. Including it would add interface complexity that directly conflicts with his experience goal of feeling confident and unconfused. We do not include it in the primary design."
Communicating User Needs to Stakeholders
The persona translates abstract research data into a form that non-researchers (clients, manufacturers, teachers, evaluators) can engage with emotionally and practically.
Evaluating Prototypes and Iterations
During testing phases, the persona provides the evaluation benchmark:
"Does this prototype allow Marcus to complete his core task in under 3 minutes while standing? Does he encounter the pain points we identified in our research, or have they been addressed?"
Writing Design Specifications
Persona attributes translate directly into measurable design specifications
Real-World Examples — Persona-Driven Design
Real-World Example — IBM Design ThinkingIBM restructured their entire product design methodology around persona-driven development from 2013 onwards. Their Enterprise Design Thinking framework mandates that every product team maintain active personas — composite characters built from field research with enterprise customers — and that every significant design decision be presented in relation to "the Hill" — a statement of what the persona achieves, not what the product does. The shift from feature-specification to persona-goal-specification is credited with reducing IBM's development cycle time and improving user adoption rates across their software portfolio.
Real-World Example — Airbnb When Airbnb rebuilt their product experience in 2014, they developed a primary persona they internally called "The Nervous First-Time Guest" — a composite derived from interviews and observation with new users who abandoned the booking process before completion. The persona revealed that the anxiety was not about price or availability but about trust — specifically, uncertainty about whether the host and the listing photographs were authentic. Every subsequent design decision — from the verification badge system to the introduction of professional photography services for hosts — was evaluated against this persona's core anxiety. The persona was not demographic ("aged 25–35, urban") — it was behavioural and motivational at its core.
Real-World Example — Microsoft Inclusive Design Microsoft's Inclusive Design methodology, applied to the development of Windows 10 and the Surface product line, used personas built around "exclusion mapping" — identifying the moments when a design excluded a particular user characteristic. Their persona spectrum tool extended the primary persona concept to show how a design decision that excluded a user with a permanent disability also excluded users with temporary and situational limitations. A persona for a user with one arm permanently also represented a user with a broken arm temporarily and a user carrying a child situationally — all had the same one-handed interaction requirement.
Constructing Your Persona
The following structure represents a minimum viable persona for IB Design Technology IA purposes. Each section should explicitly reference the research data that generated it.
Template coming soon...
What Does "Good" Look Like?
A high-achieving persona document at IB Design Technology level demonstrates:
Every significant persona attribute is explicitly linked to a named research source
The scenario is recognisably human — specific, contextual, emotionally real
Design implications are extracted and stated as actionable requirements
The persona is referenced in subsequent design decisions throughout the portfolio
The persona reflects a genuine insight that differs from initial designer assumptions — evidence that the research actually changed the design direction
The ultimate test of a persona: Could a different designer, given only this persona document and no other brief, make the same design decisions you made? If yes, the persona is functioning as a genuine design tool. If no, it is decorative documentation.
Key Takeaway
A persona is an act of synthesis — the moment when data becomes empathy, and empathy becomes design direction. It is the bridge between the world of the user and the world of the designer, constructed from evidence and sustained throughout the design process as the primary reference point for every decision.
The IBO Design Technology Guide (First Assessment 2025) requires the persona to aid design development — this is the active, ongoing obligation of the persona beyond its initial construction. A persona that is created, submitted, and never referenced again has failed its purpose entirely.
The most powerful question a designer can ask at any stage of development is:
"Does this design decision serve my primary persona's goals, address their pain points, and respect their behavioural context?"
If that question shapes your decisions consistently throughout your portfolio, your persona is functioning exactly as it should.
Sources
Cooper, Alan. The Inmates Are Running the Asylum: Why High-Tech Products Drive Us Crazy and How to Restore the Sanity. SAMS, 1999.
Cooper, Alan, Robert Reimann, David Cronin, and Christopher Noessel. About Face: The Essentials of Interaction Design. 4th ed., Wiley, 2014.
International Baccalaureate Organization. Design Technology Guide. International Baccalaureate Organization, 2023. First Assessment 2025.
Kumar, Vijay. 101 Design Methods: A Structured Approach for Driving Innovation in Your Organization. John Wiley and Sons, 2013.
Martin, Bella, and Bruce Hanington. Universal Methods of Design: 100 Ways to Research Complex Problems, Develop Innovative Ideas, and Design Effective Solutions. Rockport Publishers, 2012.
Microsoft Design. Inclusive Design Toolkit. Microsoft Corporation, 2016.
microsoft.com/design/inclusive.
Norman, Donald A. The Design of Everyday Things. Rev. ed., Basic Books, 2013.
Pruitt, John, and Tamara Adlin. The Persona Lifecycle: Keeping People in Mind Throughout Product Design. Morgan Kaufmann, 2006.
Revella, Adele. Buyer Personas: How to Gain Insight into Your Customer's Expectations, Align Your Marketing Strategies, and Win More Business. Wiley, 2015.
Young, Indi. Mental Models: Aligning Design Strategy with Human Behavior. Rosenfeld Media, 2008.
Linking Questions
To what extent does UCD rely on a strong foundation of ergonomics? (A1.1)
How important is a good understanding of user-centred research methods to ensure effective UCD? (A2.1)
To what extent can the UCD process be influenced by the quality of modelling and prototyping of potential design solutions? (B2.2)
To what extent should a UCD process focus on ensuring inclusive design? (C1.2)
What influence can product analysis and evaluation have on the effectiveness of UCD? (C3.1).