About This Course
Who this is for
Product owners, service designers, operations staff and project leads asked to improve a customer journey but who keep jumping to solutions. Teams are welcome to attend together, and they gain more when they bring one service they already know well.
What you will learn
- Plan and run three customer interviews that surface unmet needs rather than opinions
- Convert raw interview notes into an affinity map with named themes
- Write a point-of-view statement and two opening questions from that map
- Build and test a low-fidelity prototype within four hours
- Run a five-person usability test and record what actually confused them
- Decide with evidence whether to iterate, pivot or stop an idea
Course outline
Day 1
- Empathy before solutions: why teams default to features, and what a need statement looks like when it is written properly. Activity: critique two sample personas for assumptions nobody verified.
- Interview craft: open questions, tolerated silence and following the story instead of the script. Activity: paired role-play interviews with a volunteer from another team.
- Synthesis: clustering notes, naming themes and quoting the customer's own words. Activity: build an affinity wall from the day's interview notes in forty minutes.
- Framing the problem: point-of-view statements that leave room to move instead of naming the answer. Activity: draft two framing statements and have another team try to break them.
- Journey mapping: where the current experience breaks and which break matters most. Activity: map one real journey and mark the three worst moments with evidence.
Day 2
- Divergent sketching: six quick concept sketches before discussion, so the first idea does not win by default. Activity: silent sketch round followed by dot voting.
- Prototyping on paper: what a prototype must show and what it can safely fake. Activity: build a paper or slide prototype of the chosen concept in ninety minutes.
- Testing with real users: task-based sessions, neutral prompts and clear note-taking roles. Activity: run three short tests and log observations as a team.
- Deciding next steps: reading the evidence and naming the reason for the decision. Activity: ten-minute team playback with the decision and the evidence behind it.
Assessment
Each team presents its prototype, test findings and next-step decision in a playback on Day 2. Scoring covers evidence quality, prototype relevance and honesty about what did not work.
Prerequisites
Some involvement in a product, service or internal process is expected. No design software is used; all materials are paper, sticky notes and slides.
Why Take This Course
Every session includes practical exercises you can apply at work.
Courses come from accredited Malaysian training providers.
See the full price per learner before you enquire.
Every listing shows whether the course is HRD Corp claimable.
Session Schedule
| Start date | Mode | Location | Seats | Price |
|---|---|---|---|---|
| 3 Dec 2026 | In-person | Melaka | 14 | RM 1,650 |