Prototyping in Human-Centred Design: From Sketches to Real Solutions

A women writing on sticky notes

Why Prototyping is Crucial in HCD

Human-Centred Design (HCD) is all about creating solutions that actually work for people. After researching users and generating ideas, the next step is to bring concepts to life through prototyping.

Prototypes are tangible representations of ideas — they allow teams to test, learn, and refine before investing in final solutions. Skipping this step often leads to expensive mistakes, wasted effort, and products that fail to meet real human needs.

In this post, we’ll explore the types of prototypes, practical methods, tools, real-world examples, and tips to make prototyping effective in HCD.

What is a Prototype in HCD?

A prototype is a preliminary version of a solution designed to:

  • Visualize ideas
  • Test assumptions
  • Gather user feedback
  • Identify improvements before full-scale development

It doesn’t need to be perfect — it just needs to communicate the concept clearly enough for users to interact with it.

Key principle: Prototypes are for learning, not showing off.

Types of Prototypes

1. Low-Fidelity Prototypes (Lo-Fi)

  • Quick, cheap, and disposable
  • Examples: Paper sketches, storyboards, basic wireframes
  • Purpose: Explore ideas, validate concepts, and test usability early
  • Benefits: Fast iteration, low risk, encourages creativity

Example: A team redesigning a public transport app sketches screens on paper to test if users can navigate the route planner intuitively.

2. Medium-Fidelity Prototypes

  • More detailed than sketches, but not fully functional
  • Examples: Clickable wireframes, digital mockups
  • Purpose: Test flow, interactions, and layout
  • Benefits: Balances speed and realism, helps gather meaningful feedback

Example: A clickable prototype of a hospital check-in system allows users to simulate booking an appointment.

3. High-Fidelity Prototypes (Hi-Fi)

  • Close to the final product in look and feel
  • Examples: Interactive digital prototypes, fully functional MVPs
  • Purpose: Test final design, user experience, and interface details
  • Benefits: Provides realistic testing, helps stakeholders visualize outcomes

Example: A banking app prototype with live navigation, authentication, and transaction simulations helps detect usability issues before development.

Prototyping Methods in HCD

Sketching & Storyboarding

  • Quickly communicate ideas through visuals
  • Show user journeys and interactions
  • Useful in early ideation to test concepts

Paper Prototyping

  • Users interact with hand-drawn interfaces
  • Helps identify confusion and design flaws quickly
  • Encourages collaboration and rapid iteration

Digital Wireframes

  • Low- to medium-fidelity designs using software like Figma, Adobe XD, or Sketch
  • Allows for clickable navigation and interaction testing
  • Provides a bridge between conceptual sketches and high-fidelity prototypes

Role-Playing & Simulation

  • Act out scenarios to test services or processes
  • Especially useful for service design, healthcare, and public services
  • Reveals pain points not visible in static designs

MVP (Minimum Viable Product)

  • A stripped-down functional version of a product
  • Tests key assumptions with real users
  • Balances learning and resource investment

Tools for Prototyping

FidelityToolsUse Case
LowPaper, pen, whiteboardsSketching, storyboarding
MediumFigma, Adobe XD, InVisionClickable wireframes, digital mockups
HighAxure, Proto.io, MarvelInteractive prototypes, MVPs
Service & ProcessMiro, Mural, SmaplyJourney mapping, role-play simulations

Prototyping Best Practices

  1. Start Small and Simple
    • Lo-fi prototypes first, then iterate to hi-fi
    • Avoid over-investing before testing
  2. Test Early and Often
    • Even rough prototypes reveal valuable insights
    • Early testing reduces risk and cost
  3. Focus on Learning Goals
    • Decide what you want to learn from each prototype
    • Align testing activities with research questions
  4. Involve Users and Stakeholders
    • Invite real users to interact and provide feedback
    • Include team members from different disciplines
  5. Document Feedback and Iterations
    • Keep records of what works, what doesn’t, and why
    • Use findings to improve next iteration

Real-World Example: Healthcare App

Scenario: A hospital wants to simplify patient appointment booking.

Step 1: Lo-Fi Sketches

  • Team sketches key screens on paper
  • Users test basic navigation and identify confusing terms

Step 2: Medium-Fidelity Prototype

  • Clickable digital prototype created in Figma
  • Users navigate booking flow; feedback shows missing accessibility options

Step 3: High-Fidelity Prototype

  • Interactive app with visual design and accessibility features
  • Tested with patients; final adjustments made before development

Outcome: A patient-friendly app that reduces call centre load and improves satisfaction.

Prototyping in Service Design

Prototypes aren’t just for digital products — they’re essential for services and processes too.

Example: A government office redesigns its permit application process:

  • Paper prototypes simulate counter interactions
  • Role-playing tests new workflows
  • Feedback informs signage, online forms, and staff training

This approach ensures solutions are usable, efficient, and human-centered.

Common Mistakes in Prototyping

  • Skipping low-fidelity prototypes and going straight to hi-fi
  • Testing too late when changes are costly
  • Overcomplicating early prototypes
  • Ignoring user feedback or treating it as optional
  • Failing to iterate — a single prototype is rarely enough

Measuring Prototyping Success

A prototype is successful if it:

  • Provides actionable insights to improve design
  • Reveals user pain points early
  • Supports stakeholder alignment
  • Accelerates decision-making and reduces risk

Conclusion: From Ideas to Reality

Prototyping is the bridge between imagination and implementation in Human-Centred Design. It allows teams to test ideas, uncover hidden problems, and refine solutions in collaboration with real users.

Remember:

  • Start simple, iterate often
  • Focus on learning, not perfection
  • Involve users and stakeholders early

By mastering prototyping, you turn HCD insights into tangible solutions that truly work for people.