Rob Pearson (Amido) explains how the team used lean, collaborative UX to make The Source, a new digital product for Macmillan Cancer Support. The case study walks through stakeholder interviews and workshops, lo-fi wireframes, guerrilla and paper-prototype testing, iterative prototyping, and usability testing — framing UX as an approach to gathering evidence around design decisions, not an expert-only discipline. Source: UX Brighton UX Camp Brighton 2016 Redux (https://uxbri.org/uxcb16redux/) and the matching Product Tank Brighton deck (https://www.slideshare.net/slideshow/product-tank-macmillan-source-talk-12/50627168).
People
Rob Pearson
Methods
User InterviewsUser interviews explore people’s circumstances, experiences and needs through a guided conversation. Use them when you need to understand a problem in depth or learn how a service fits into someone’s life. Recruit current or likely users, prepare open questions and possible follow-ups, and ask for concrete examples rather than idealised accounts. Start with consent, listen carefully, and allow useful unexpected topics to emerge. A discussion guide keeps the research focused without turning it into a rigid questionnaire. Interviews can accompany usability tests when you also need to observe people using a service.
Workshop FacilitationWorkshop facilitation guides a group towards a shared outcome without imposing the facilitator’s preferred answer. Define the purpose, prepare activities and materials, and create opportunities for everyone to contribute. Combine individual thinking with discussion when helpful, listen for different perspectives and adjust the plan to the group’s needs. Record decisions and clarify who will take the next steps. Use facilitation when a team must explore a problem, generate ideas or agree actions together; successful participation matters as much as the visible workshop outputs.
WireframingLow-to-mid fidelity layouts that show structure, hierarchy and key interactions without final visual polish — used to explore and agree interaction before visual design.
PrototypingBuilding disposable stand-ins for a product — from paper and clickable wireframes to coded spikes — so teams can try interactions before committing to build. Used to explore options, align stakeholders, and run usability tests on something people can click or walk through. Fidelity should match the question: low for flow and structure, higher when timing, motion or real content matter.
Usability TestingUsability testing reveals where people struggle while attempting realistic tasks with a prototype or service. In a moderated session, a researcher observes the participant and may ask them to explain their thinking. Use it to investigate confusing language, layouts or interactions and identify improvements. Agree research questions, recruit likely users and prepare believable tasks that do not reveal the solution. Explain that the service is being tested, then mostly watch and listen rather than guiding participants. Record observations and follow up on unclear behaviour. Plan accessible sessions, including participants’ own assistive technology when appropriate.