FBTE34511 Chap.4 Human-Centred Design and User Value
Human-Centred Design and User Value
Human-Centred Design and User Value places people's experiences, motivations, cultural context and constraints at the centre of problem solving. The chapter separates an evidenced need from a preferred feature, treats personas as hypotheses and uses low-cost prototypes to test the uncertain mechanism.
Observation, framing, prototyping, testing and refinement form a loop because user evidence can reopen the problem rather than merely polish a selected product. Accessibility and dignity both matter: a system may be technically usable while still being stigmatising, burdensome or dependent on unwanted assistance.
What this chapter covers
- 01
Human-centred design
- 02
User evidence
- 03
Needs and features
- 04
Persona hypotheses
- 05
Accessible design
- 06
Prototyping
- 07
Iteration
Worked example · free
Test a refill service with operating users
- 1Observe the task with cleaners and supervisors in context.
- 1Define safe identification and dosing as the need.
- 1Prototype tactile and symbol cues without relying on phones.
- 1Record errors and change the connector design.
Key terms
- Persona
- A research-based representation used to organise current evidence about a user group.
- Prototype
- A limited representation built to test a particular assumption, interaction or mechanism.
- Design dignity
- The quality of enabling use without stigma, avoidable dependence or loss of respect.
Human-Centred Design and User Value FAQ
How do I avoid inventing a persona?
Cite evidence behind important characteristics, label assumptions and state who the profile does not represent. Treat the persona as a hypothesis to validate with real users rather than as a source of facts.
What should an early prototype test?
Test the assumption most likely to make the concept fail. Use the lightest form that can expose behaviour or understanding, such as a sketch, role-play, material mock-up or clickable sequence.
Is asking users what they like enough?
No. Preference can be useful, but task observation reveals errors, hesitation, workarounds and exclusion. Ask participants to do something with the prototype and record what happens before asking for interpretation or preference.
What should an adversarial walkthrough include?
Ask a participant or teammate to pursue the least convenient legitimate route: use a non-phone option, challenge an incorrect record, withdraw consent or recover from a failed hand-off. Observe where the service relies on goodwill, hidden labour, specialist knowledge or an inaccessible fallback. Translate each breakdown into a requirement, owner and next test.
The exercise does not prove universal performance, but it exposes fragile assumptions before they become expensive to reverse and supplies concrete evidence for inclusion, governance and pilot design.
Assessment move
For each idea, write the user, context, task and current barrier. Separate the need from the selected feature, then cite the evidence supporting it. Build the smallest prototype that tests the largest uncertainty and decide what behaviour or error would count as contrary evidence. Include participants who represent meaningful variation in access, language, experience or physical interaction.
Record what was tried, what happened, what surprised the team and what changed. In the report, connect the user finding to technology, circularity or implementation criteria so human-centred design shapes the recommendation rather than appearing as a standalone empathy section. Begin with a research sheet that separates what people say, what they do and what the environment makes possible.
An interview can reveal goals and meanings, while observation may expose workarounds, interruptions or physical constraints that the participant no longer notices. Avoid turning one striking quote into a universal need. Look for repeated patterns and important differences, then state the limits of the sample. Build personas only after this review.
Every characteristic should either trace to evidence or be labelled for validation. Remove decorative biography that does not affect a design decision. Convert each need into a capability statement without naming the preferred feature. For example, a person may need to verify status without fine visual discrimination; speech, tactile cues and assisted service are alternatives to compare.
Choose the prototype around the largest uncertainty. A paper journey tests sequence, a role-play tests responsibilities, a material model tests physical interaction and a clickable screen tests interpretation. Give participants a task and observe completion, errors, hesitation and requests for help. Ask follow-up questions after behaviour is recorded.
Plan variation deliberately by considering access, language, experience, dexterity, trust and technology availability. State whose experience is still missing. After each test, keep a short decision log: evidence, interpretation, change and unresolved question. Use that log in the roadmap to define the next pilot gate. When writing, connect the user evidence to appraisal criteria and circular routes.
If a non-phone pathway, repair instruction or data-minimisation rule exists because of research, make that causal connection explicit. The reader should see how human evidence changed the proposal, not merely that the team practised empathy.
Working through Human-Centred Design and User Value in FBTE34511? Sia is AskSia’s AI Management tutor — ask any FBTE34511 Human-Centred Design and User Value question and get a clear, step-by-step explanation grounded in how FBTE34511 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.