Flag

We stand with Ukraine and our team members from Ukraine. Here are ways you can help

Get exclusive access to thought-provoking articles, bonus podcast content, and cutting-edge whitepapers. Become a member of the UX Magazine community today!

Home ›› Agile and Iterative Process ›› How Prototyping is Replacing Documentation

How Prototyping is Replacing Documentation

by Ian Schoen
3 min read
Share this post on
Tweet
Share
Post
Share
Email
Print

Save

Prototypes are powerful tools for explaining design decisions to clients and can communicate ideas more effectively that documentation.

Working at a design consultancy, documentation is often the primary deliverable we hand off to clients. When dealing with complex interactions, it’s not uncommon for documents to be over 100 pages long. Drafting these types of deliverables takes serious care, attention to detail, and significant time working at high fidelity in programs like Illustrator and Photoshop.

The big concern is that when designers ship their work to clients, the final documentation doesn’t become the final product regardless of how well it’s crafted.

“Documentation could be overlooked, ignored, or simply out of date by the time it comes to actually implement a feature if we’re working with a very agile development team.”

This is something Jason Frasier, design director at DesignMap, said when he stopped by Tradecraft last year to share his perspectives on prototyping. He discussed how it’s replacing documentation as a UX deliverable, and how we can utilize prototyping in our design process.

Documentation is inflexible. Often, the effort involved keeping things consistent when changes are made can be more challenging than creating the design itself. In all, documentation can’t always meet the evolving needs of a client when they prepare to ship their product and that is problematic.

Prototypes are Powerful

“People don’t read products, they interact with them.”

Creating a prototype as a final deliverable allows for greater interaction with the product and a deeper-level understanding of how the product is experienced. It can also easily be adopted for usability testing and iterated on quickly and efficiently to push out new versions.

Prototyping is also an impactful way to present to your client. People know how to interact with products. Demonstrating interactions with a prototype helps to spark well-informed discussions with clients and can lead to better design more quickly.

Demonstrating interactions with a prototype helps to spark well-informed discussions with clients

When discussing prototyping, it’s important to understand the methods and know when to use them. Jason went over five prototyping techniques that he thought were important to utilize at different parts of the design process.

How to Utilize Prototypes

Here’s Jason’s breakdown of how to use prototypes as you move through the design process.

Paper Prototype
  • Creating rough, hand-drawn sketches of UIs to put in front of users for testing.
  • When to Use: When you want to validate basic design ideas and understand rough interactions before going forward at a higher fidelity.
  • Presentation: Paper cutouts
Vision Prototype
  • Creating a presentation that quickly runs through an interaction at high fidelity.
  • When to use: When you want to wow your client. When it’s more about the polish than the actual experience. If you need to sell an idea.
  • Presentation: Keynote
Click-Through Prototype
  • Creating a set of static wireframe slides and discussing slide interactions.
  • When to use: When working with developers and project managers to demonstrate a linear flow through an experience quickly and efficiently.
  • Presentation: Invision, PDF
Wireframe Prototype
  • Creating a clickable wireframe prototype that can be put in front of users.
  • When to use: When conducting user testing or demonstrating interactions to clients at a higher fidelity.
  • Presentation: InVision
High Fidelity Prototype
  • Creating a prototype that closely resembles the real product.
  • When to use: When your product is nearly ready to ship.
  • Presentation: Web browser, mobile device, InVision.

Conclusion

If you’re a UX designer, knowing how and when to prototype is already a requisite skill. Now, teams are transitioning from documentation to prototypes as final deliverables. Prototyping can make your design process more agile, allow you to express complex interactions elegantly, and present your work to your client in a more dynamic and iterative way. Avoid 100+ page documents and start prototyping.

 

Image of crumpled paper spilling out of wastebasket courtesy Shutterstock.

post authorIan Schoen

Ian Schoen
Ian is inspired to create products that bring people together in new and meaningful ways. He spent the last two years working in Malaysia and Japan through the Fulbright Program and TEDxTokyo and is now back in San Francisco designing experiences at Salesforce.

Tweet
Share
Post
Share
Email
Print

Related Articles

Another lesson from studying UX with Laura Klein.

Article by Paivi Salminen
The Agile Trap Designers Fall into: Feeding the Beast
  • Agile teams are fast, but designers get stuck in an infinite loop of visual work: redesigning the same components over and over instead of solving real UX problems.
  • Design systems break that cycle, defining the building blocks once, freeing designers to focus on how the product works, not how it looks.
  • When the basics are in place, teams can start working together sooner, prototype faster, and release incremental features without the interface falling apart.
Share:The Agile Trap Designers Fall into: Feeding the Beast
4 min read

Real engagement is about designing experiences that people want to have. Here are some things that games do well that most apps don’t.

Article by Montgomery Singman
Gamification 2.0. Beyond Points and Badges: Designing for Players, Not Metrics. Conclusion
  • Most apps use gamification as a manipulation layer to drive metrics, but people engage with things that are truly worthy of their time, not points or streak guilt.
  • Apps that people stick with do this by designing for intrinsic motivation, making the experience itself rewarding.
  • The true measure of success is whether users feel more capable, accomplished, and enriched for having used your app.
Share:Gamification 2.0. Beyond Points and Badges: Designing for Players, Not Metrics. Conclusion
8 min read

For researchers, AI tools are making the move from advising to building easier than ever. But the real obstacle was never technical. Meet the researchers who allowed themselves to create — and what the cost was.

Article by James Lang
The New Makers
  • The article says that becoming a maker as a researcher is less about learning new tools or skills and more about giving yourself a new identity, and that without fixing the internal permission structures that define your swim lane, even the most democratized AI tools won’t turn a researcher into a maker — you don’t have a founder; you have a frustrated advisor with a prototype.
Share:The New Makers
20 min read

Join the UX Magazine community!

Stay informed with exclusive content on the intersection of UX, AI agents, and agentic automation—essential reading for future-focused professionals.

Hello!

You're officially a member of the UX Magazine Community.
We're excited to have you with us!

Thank you!

To begin viewing member content, please verify your email.

Get Paid to Test AI Products

Earn an average of $100 per test by reviewing AI-first product experiences and sharing your feedback.

    Tell us about you. Enroll in the course.

      This website uses cookies to ensure you get the best experience on our website. Check our privacy policy and