IDEA9105 Chap.2 User Research, Personas and Early Sketching

User Research, Personas and Early Sketching

Research begins with a decision the team cannot responsibly make from assumptions alone. Questions about goals, workarounds, context and breakdowns invite evidence. Questions that ask whether users like a planned feature often convert a solution into the premise and collect polite confirmation.

Observation reveals behaviour and environment; interviews reveal accounts, meaning and memory; artefact analysis reveals traces of work. Combining methods can expose gaps between what people say and what conditions let them do. A health-app team asks whether reminders would help and receives broad agreement. Observing routines reveals that users already silence notifications during shift work.

The design problem is timing and control, not reminder absence. Write the pending design choice beside each research question. If no possible answer would change the choice, the question is ceremonial rather than useful. Interface evidence becomes actionable when research question is tied to a user goal, a context and an observable interaction.

Convert observation into a design requirement that can be inspected in a wireframe or prototype. Then define the success and failure states for feature bias, including the recovery path. A polished screen is not enough if the transition, feedback or accessibility behaviour remains implicit. Write a state inventory for research question: entry condition, available action, system response, next state and recovery route.

Connect observation to the cue a user can perceive rather than an intention known only to the designer. Digital communities develop norms, roles, histories and platform-specific ways of participating. Online ethnography examines interaction over time rather than treating posts as free-standing opinions.

Ethical attention includes visibility, consent, vulnerability, quotation searchability and the researcher's effect on the setting. Ranking, moderation, interface defaults and affordances influence what is visible. Silence may mean absence, exclusion, private migration or observation without posting. Interpretation should preserve those alternatives.

A forum appears to reject a feature because critical posts dominate the top of a thread. Sorting by time reveals early supportive discussion buried after an algorithmic popularity shift. Platform ordering changes the apparent consensus. Record how material was encountered, what the platform made visible and which participants remain unseen.

Paraphrase responsibly and avoid collecting identifiable detail beyond the research purpose. A designer can test online ethnography by turning the assumption into a task with a clear start state and completion signal. Observe where a participant hesitates around platform trace, what they expect next and which cue changes their interpretation. For research ethics, record behaviour separately from the participant's explanation.

The resulting evidence should identify a design decision, not merely produce a list of comments. Turn the assumption about online ethnography into a task protocol. Give the participant realistic information, avoid coaching the route through platform trace, and decide in advance which behaviour would support or challenge the design. Note hesitation, backtracking and incorrect expectation with the state in which they occur.

A persona is a design model representing a meaningful pattern in research, not an invented biography. Include characteristics that change tasks, information needs, constraints or interaction. Decorative demographics and vivid but unsupported stories can harden assumptions instead of challenging them. Two personas are useful when their needs produce different priorities or flows.

If every persona leads to the same interface, the distinction may be irrelevant. Conversely, one average persona can erase accessibility and contextual constraints. Research shows one group manages care collaboratively while another acts alone under time pressure. Those patterns justify different sharing and confirmation needs; favourite colours and fictional job titles do not.

Attach each major persona claim to an observation cluster. During critique, ask what new evidence would split, merge or retire the persona rather than treating it as a permanent user truth. Represent persona at the lowest fidelity that can answer the current question. Layout sketches expose hierarchy and flow; interactive prototypes expose state, timing and feedback.

When evaluating evidence cluster, keep content realistic enough for users to make meaningful choices. Track segmentation across normal, empty, loading and error conditions so that the design demonstrates a complete interaction rather than one ideal route. Use fidelity as an experimental choice for persona.

A sketch can compare hierarchy and navigation cheaply, while a linked prototype is needed to inspect timing, feedback and state transition around evidence cluster. Sketches externalise ideas quickly enough to compare, combine and discard them. Low visual finish signals that change is welcome and directs critique toward concept, task flow and hierarchy. The value lies in breadth and conversation, not drawing ability.

Changing icon style across several sketches is not meaningful divergence if the task structure stays fixed. Generate alternatives that change sequence, grouping, disclosure or control, then state the assumption each one tests. A team draws several polished versions of one appointment screen. A rough alternative that begins with reason for visit exposes a different triage logic and generates a more useful comparison.

Time-box individual sketches before group discussion so one loud proposal does not anchor everyone. Annotate the user action and expected system response on each frame. Accessibility belongs inside the interface model. Ask whether sketch remains perceivable and operable with different input, vision and reading conditions.

Apply divergence through contrast, hierarchy, labelling and focus order, then inspect whether design assumption communicates status without relying on colour alone. These checks often reveal general usability defects because explicit structure benefits more than one access need. Audit sketch through keyboard order, focus visibility, readable hierarchy, labels and non-colour feedback.

Ask whether divergence remains understandable at magnification and whether controls expose name, role, state and error recovery. Accessibility evaluation combines standards, inspection and use by people with relevant access needs.

What this chapter covers

• 01

  A research question protects observation from feature bias

• 02

  Online ethnography reads practice in its digital setting

• 03

  A persona synthesises patterns rather than stereotypes

• 04

  Sketching keeps alternatives cheap

Worked application: A research question protects observation from feature bias

Key terms

Bias-resistant research question

A research question protects observation from feature bias — Research begins with a decision the team cannot responsibly make from assumptions alone. Questions about goals, workarounds, context and breakdowns invite evidence. Questions that ask whether users like a planned feature often convert a solution into the premise and collect polite confirmation. Write the pending design choice beside each research question. If no possible answer would change the choice, the question is ceremonial rather than useful.

Online ethnography

Online ethnography reads practice in its digital setting — Digital communities develop norms, roles, histories and platform-specific ways of participating. Online ethnography examines interaction over time rather than treating posts as free-standing opinions. Ethical attention includes visibility, consent, vulnerability, quotation searchability and the researcher's effect on the setting. Record how material was encountered, what the platform made visible and which participants remain unseen. Paraphrase responsibly and avoid collecting identifiable detail beyond the research purpose.

Evidence-based persona

A persona synthesises patterns rather than stereotypes — A persona is a design model representing a meaningful pattern in research, not an invented biography. Include characteristics that change tasks, information needs, constraints or interaction. Decorative demographics and vivid but unsupported stories can harden assumptions instead of challenging them. Attach each major persona claim to an observation cluster. During critique, ask what new evidence would split, merge or retire the persona rather than treating it as a permanent user truth.

User Research, Personas and Early Sketching FAQ

Assessment move

Maintain a decision trail for User Research, Personas and Early Sketching. Connect each user observation to a requirement, interface state, prototype change and next test. Begin with research question and reconstruct the reasoning without looking at the worked response. Then change one condition in the example and decide whether observation still explains the outcome.

Use the chapter questions to compare direct observation with inference, and write the strongest rival account in full. Before closing the chapter, return to design assumption and state the precise boundary it places on transfer. Check that every conclusion names an observable consequence and that uncertainty is attached to the step it affects.

A final retrieval pass should be fast enough to reproduce the method from headings and diagrams while leaving the detailed prose for checking nuance.

IDEA9106 Design Programming · DESN1001 Design Process · INFO5990 Professional Practice