Article
Design process

updated on:

20 Mar

,

2025

Stage 4 of Design Thinking – Prototype: How to Create, Test & Improve Ideas

12

min to read

Table of contents

Imagine spending months designing a product, only to realize users struggle with the interface. Frustrating, right? That’s where prototyping makes all the difference. It allows designers to refine visual details, catch usability issues before launch, and ultimately build products that work.

But in reality, prototyping is more than that. As a part of design thinking, prototype helps designers visualize and test ideas quickly, identify usability problems early, and communicate concepts effectively to stakeholders and developers. Without it, teams risk investing in ideas that may not work in practice (at Eleken, with 40 UI/UX designers using design thinking daily, we know it firsthand).

In this guide, we’ll walk you through:

  • What the Prototype stage is, why it matters, and how it fits into the design process.
  • The different types of prototypes and when to use them.
  • How to create effective prototypes using tools like Figma and Protopie.
  • Best practices, common pitfalls, and real-world case studies (like how Eleken refines designs through prototyping).

By the end, you’ll have a clear, practical guide to help you prototype smarter and design better.

What is a prototype in Design Thinking?

In design thinking, a prototype is a simplified version of a product used to test its concept, user flow, design, and functionality before full development. It allows designers to validate ideas, gather feedback, and iterate quickly with minimal resources. By simulating the user experience, prototypes help refine interface logic, test usability, and map user paths early in the design process.

In design thinking, prototyping is the fourth stage that bridges ideation and testing, turning ideas into user-centered solutions.

design thinking graphic

So why is prototyping a crucial element of the Design Thinking process? One Reddit user provides a great explanation:

Prototype Reddit comment

To sum up: making prototyping a core part of the design process helps teams:

  • Visualize and test ideas quickly – Instead of explaining concepts, show stakeholders and users what your product could look like.
  • Identify usability issues early – Catch flaws before development starts, saving time and resources.
  • Communicate better – Prototypes serve as a common language for designers, developers, and stakeholders.
  • Reduce risks and guesswork – No more launching untested ideas and hoping they work. With prototypes, you can validate before investing heavily.

That’s the theory — but how does prototyping actually work in practice as a part of design thinking? 

What is an example of a prototype?

 A client came to Eleken with a vision for a Process Enablement Platform aimed at helping large enterprises manage workflows and training materials. After completing the Ideation Phase, they had a solid concept but needed a tangible solution to present to investors and test its feasibility.

The Prototyping Process:

  • From Ideation to Prototyping: After brainstorming and sketching ideas in the ideation phase, Eleken took the client's wireframes and transformed them into a high-fidelity, interactive prototype.
  • Testing and Feedback: This prototype was then tested with stakeholders and potential users, providing critical insights into how the platform would function and whether it met the users' needs.
Process Enablement Platform example

The Outcome:
The prototype allowed the client to validate their ideas, gather valuable feedback, and refine the concept before moving into full development. This step helped reduce risks and ensured that they were on the right path.

After incorporating the feedback, the team entered the next phase of the Testing stage. New insights and feedback drove further iterations, ensuring the platform continuously improved and met user needs. Prototyping remains a vital part of this ongoing, iterative process, bridging the gap between ideation and testing, and helping teams refine and perfect their solutions based on real user feedback.

Prototypes can vary greatly depending on their purpose and the project stage, ranging from simple sketches to high-fidelity models. In the next section, we’ll explore different prototyping methods and their applications in design thinking.

Types of prototypes in Design Thinking

Prototyping techniques are typically classified into two main categories: low-fidelity and high-fidelity prototyping (depending on the stage of the project). The key is to choose the right one for the problem you're solving.

Low-fidelity prototypes (Lo-Fi)

Think of low-fidelity prototypes as a rough draft for design — quick, simple, and focused on big-picture ideas. These early-stage models help you explore concepts and gather feedback fast. They’re not meant to be polished but to communicate functionality and interaction in their simplest form. Easy to create, they allow rapid iterations, letting you test ideas without committing too many resources.

Examples:

  • Sketches: Simple, hand-drawn visuals used to quickly explore and share early product ideas with teammates for feedback and discussion.
  • Paper Prototypes: Tangible, hand-drawn models that simulate user interactions. They can be physical (using cut-out elements) or digital (with clickable interactions to test user flows).
Low-fidelity prototype example
  • Wireframe-based Prototypes: Low-fidelity digital representations used to simulate user interactions. These prototypes are built from basic wireframes, which focus on structure rather than aesthetic detail. They typically consist of simple shapes, lines, and placeholder text, aiming to test the flow and layout of the design before refining the visual elements.
Wireframe-based Prototype

Understanding when to use low-fidelity prototypes is crucial for maximizing efficiency in the design process.

Best for: Early ideation, quick feedback, brainstorming, and testing concepts with minimal time or resource investment.

Limitations: Lacks detail and interactivity, making it unsuitable for usability testing or final presentations.

High-fidelity prototypes (Hi-Fi)

High-fidelity prototypes are closer to the final product, offering a more refined and interactive experience. These detailed models simulate the actual design, whether for physical or digital products. They help stakeholders visualize the end result and provide insights into how users might interact with the finished product.

Examples:

  • Interactive Mockups. Digital prototypes with clickable elements and basic functionality, simulating the user experience more realistically.
  • Coded Prototypes Fully functional prototypes built with actual code (HTML, CSS, JavaScript) to replicate real user interactions and behaviors.
High-fidelity prototype example

High-fidelity prototypes offer a more detailed and interactive experience, but benefits and challenges come with this added complexity. 

Best for: Refining details, usability testing, developer handoff, and stakeholder presentations where a realistic representation is needed.

Limitations: Requires more time and resources, making it less efficient for early-stage exploration.

To clarify, here’s a comparison table outlining the differences between low-fidelity and high-fidelity prototypes.

High-fidelity vs low-fidelity prototype comparison table

The goal is to use just enough fidelity to gather the insights you need at each stage. Now that you understand the different types of prototypes, let’s dive into the practical side. In the next section, we’ll walk through a step-by-step guide on building a prototype, from defining goals to testing and iterating.

How to prototype in design thinking: step-by-step guide

Prototyping is a crucial phase in the design thinking process. It allows you to bring your ideas to life, test them quickly, and refine them based on real user feedback. By creating prototypes, you can explore design concepts, validate assumptions, and make informed decisions before developing a final product.

1. Define goals

Before diving into the prototyping process, it’s important to define what you want to achieve. Whether you’re testing user interactions, validating a concept, or refining a feature, setting clear objectives will guide your work throughout the process.  Prototypes aren’t just for testing — they help align teams, clarify developer handoffs, and reduce lengthy documentation.

Examples of prototyping goals:

  • User testing: "Does this navigation flow make sense?"
  • Stakeholder buy-in: "Can we secure approval from leadership?"
  • Developer handoff: "Does this demonstrate how the dropdown menu should function?"

2. Choose your tool

The tool you choose for prototyping should align with your goals, resources, and stage in the design process. Consider these factors when selecting a tool:

  • Speed vs. Fidelity: For early-stage concepts, low-fidelity prototypes (like pen and paper) can quickly gather feedback. For more detailed interactions, higher-fidelity tools are needed.

  • Collaboration Needs: If working with a team or stakeholders, tools like Figma allow easy sharing and real-time collaboration.

  • User Interactions: Simple flow testing can use low-fidelity methods, but interactive behaviors (animations, transitions) require higher-fidelity tools.

  • Learning Curve: Simple tools like wireframes are quick to learn, while advanced tools like Axure offer more complexity but require more time to master.

Sometimes, a quick sketch is all you need to test an idea. Choose the tool that fits your stage and goals.

3. Build the prototype

When creating your prototype, zero in on the key interactions and user flows that truly need testing. Don’t get caught up in perfection — your goal is to create something quick, rough, and testable, not a polished masterpiece. The quicker you can test, the faster you’ll learn.

Common Pitfalls to Avoid

Mistake: Trying to make it pixel-perfect before testing.
Fix: Your first prototype should be messy. If it's too polished, you're overthinking it.

Mistake: Prototyping everything instead of key interactions.
Fix: Focus on the critical decision points and problem areas, not recreating the entire app.

4. Test and iterate

Once your prototype is ready, put it in front of real users. Observe how they interact with it, gather feedback, and use their input to refine your design. Keep in mind that prototyping is an iterative process—testing and improving should be ongoing. 

  • Before Testing: Define your success metrics. Ask yourself: What will make this prototype successful?
  • During Testing: Assign users a specific task to complete and observe where they hesitate or get confused.
  • After Testing: Prioritize feedback, focusing first on the most critical usability issues that need addressing.

A prototype is only valuable when tested and refined with real user insights. Skipping this step could result in a product that misses the mark.

Tools for prototyping

When selecting prototyping tools, it’s important to consider your team’s specific needs, skill level, and the complexity of the prototype. Each tool serves a unique purpose, so it’s important to choose the right one to streamline your workflow and enhance collaboration with stakeholders.

Figma

Best For: Quick prototypes and team collaboration

Figma is perfect for creating simple user flows and wireframes, making it a go-to for teams that need real-time collaboration. It's easy to use and speeds up the design process, though it may have limitations in handling advanced interactions.

Figma’s real-time collaboration features make it a great tool for rapid prototyping, even in the most dynamic settings. As one designer shared in a Reddit comment:

Reddit comment about Figma prototypes

This highlights how Figma excels in quick iterations and real-time collaboration, making it ideal for fast-paced design sessions.

Strengths:

  • Easy to use
  • Collaborative and real-time features
  • Great for simple prototypes and wireframes

Limitations:

  • Limited advanced interactivity compared to some tools

Pricing:

  • Free version available, Pro from $15/month
Figma prototype example

ProtoPie

Best For: Mobile apps, real user input, and complex interactions.

If interactivity is your priority, ProtoPie is a great option. It allows for advanced interactions, real user inputs, and sensor-based features — all without requiring any coding. This makes it ideal for prototypes that go beyond simple click-through flows and require a more dynamic experience.

Strengths:

  • No coding required
  • Supports advanced interactions and real-user inputs
  • Ideal for mobile app prototypes

Limitations:

  • Learning curve can be steep
  • Limited to more interactive prototypes

Pricing:

  • Free version available, paid plan starts from $25/month
ProtoPie prototype example

Axure

Best For: Business-level projects requiring advanced interactivity.

Axure is a powerful tool for high-fidelity prototypes with conditional logic and dynamic content. While it’s great for complex, business-level projects, it’s better suited for experienced designers due to its steep learning curve.

Strengths

  • Advanced logic and dynamic content
  • Suitable for business-level prototypes
  • Great for highly detailed, interactive designs

Limitations

  • Steep learning curve
  • More suited for experienced designers

Pricing

  • Free trial, from $29/month
Axure prototype example

Framer

Best For: High-quality UI prototypes and interactive designs.

Framer is ideal for creating polished, high-fidelity designs and interactive UI elements with motion. It’s great for teams focused on animations and smooth transitions, but some basic coding knowledge may be needed.

Strengths

  • Ideal for animations and UI interactions
  • Great for polished, high-fidelity designs
  • Strong for interactive UI elements

Limitations

  • Requires some coding knowledge
  • Better for high-fidelity UI design than simple flows

Pricing

  • Free, Pro from $5/month

Framer prototype example

To help you compare these tools at a glance, here's a quick overview of their strengths, limitations, and pricing:

Prototype tools comparison table

Now that you’ve got a handle on the tools available, let’s explore how you can take your prototyping process to the next level by integrating AI to make your designs smarter, more intuitive, and more efficient.

Integrating AI in prototyping

Integrating AI into the prototyping phase is revolutionizing design workflows. Here’s how AI-powered tools can help streamline the process:

  • AI-Powered Wireframing
    AI tools like Uizard and Figma AI can instantly generate wireframes from simple prompts, simplifying the early stages of the design process. Instead of manually creating each component, you can quickly set up a framework, saving valuable time and resources.

With Uizard, you can scan a hand-drawn sketch, and it will instantly generate a digital UI design, accelerating the design process:

Uizard hand-drawn sketch example
  • AI-Based Heatmaps
    Tools like Hotjar AI and CrazyEgg AI predict where users are most likely to click or interact with your design. By visualizing user behavior in advance, you can make informed decisions about layout and content placement, optimizing the design for better engagement.

Here’s how Hotjar AI generates reports with design suggestions:

Hotjar AI-Based Heatmap
  • Automated Usability Testing
    Platforms like Useberry and Maze AI identify potential usability issues without the need for extensive manual testing. These tools analyze user flows and behavior to highlight areas where users may struggle, allowing you to address major issues before you start iterative testing with real users.
  • AI-Generated Variants
    Tools like ABtesting.ai suggest multiple UI variations based on A/B testing principles. By simulating different user personas and analyzing their behavioral data, AI generates insights on which design elements work best for various target audiences, reducing the need to manually prototype for every edge case.
ABtesting.ai UI variation example
  • Design-to-Code Automation
    AI tools like Figma Dev Mode and Locofy automatically convert your designs into functional code. This allows developers to skip the hand-off stage, significantly accelerating the transition from design to development and reducing errors that might occur during manual coding.
Figma Dev Mode example

When NOT to prototype

 While creating UI/UX design for SaaS products, we've learned that prototyping isn't always necessary, especially when the task at hand is relatively simple. In certain situations, skipping prototyping can save time and resources while still ensuring effective communication.

Simple UI Changes or Minor Tweaks
If you're making minor adjustments, like tweaking button placements or changing colors, prototyping may not be necessary. 

When the design is already validated

If user research, surveys, or previous usability testing have already validated your design, prototyping might be redundant. You can proceed directly to development or quality assurance testing.

Low-impact features

For features that don’t significantly impact the user experience, prototyping may not be necessary. If the feature is simple or doesn’t require extensive user feedback, you can skip it.

Tight timelines or limited resources

When faced with tight deadlines or limited resources, prototyping may not be feasible. In these cases, focus on creating other design tools, such as user flow diagrams, journey maps, or personas, to clarify the user experience before development.

In cases where a prototype isn’t necessary, there are alternative methods to map out and communicate design ideas effectively:

  • Annotated Wireframes: These are simple sketches with notes that explain the layout and functionality of a page, offering a quick way to communicate design ideas without a full prototype. At Eleken, we use annotated wireframes to ensure better understanding and clarity in our design process.
Annotated Wireframe example
  • User Flow Diagrams: These diagrams show the path users take to complete tasks, helping designers visualize the user journey and identify potential issues without the need for an interactive prototype.

User Flow Diagrams

Both methods are great for projects where prototyping isn’t required but clear communication and structure are still essential.

Conclusion: prototyping in Design Thinking

Prototyping is an essential part of Design Thinking, allowing designers to validate ideas, test interactions, and refine concepts before development. It’s an iterative process that helps avoid costly mistakes and ensures the final product meets user needs.

Key Takeaways:

  • Prototypes help visualize and communicate ideas early on.
  • Low-fidelity prototypes are ideal for quick testing and feedback.
  • High-fidelity prototypes provide more realistic user interactions.
  • Prototyping is an ongoing cycle of testing, learning, and improving.
  • In some cases, simple tools like wireframes or user flow diagrams can replace full prototypes.

Just like prototyping, Design Thinking itself is an evolving journey that requires constant learning and exploration. As you refine your design approach, diving into the foundational principles of Design Thinking can further deepen your understanding and enhance your skills. 

If you’re eager to continue your learning journey and uncover the best books to expand your knowledge, we’ve got you covered. Head over to our next article on Design Thinking Books to discover the top resources that will help you think smarter, create better, and stay inspired on your design journey.

Share
written by:
image
Sophia Andrus

Content writer with a diverse background in translation, customer support, and digital content. At Eleken, she combines her expertise to create clear, user-friendly copy that translates complex UI/UX design principles into accessible insights for a better digital experience.

imageimage
reviewed by:
image

imageimage
Top Stories