Be the first to like this
We know that many approaches help us create products for people. Whether you’re working on an enterprise-wide site redesign or improving a departmental intranet or creating a new app for your startup, identifying purpose, effort, & consistency require clear communication.
Wireframing has held sway over UXers for the past 20 years. From its metaphoric origins in filmmaking to its pinnacle in countless UX books, wireframing stood as a key approach in defining both structure & interaction. In recent years, however, wireframing has come under attack. UX thinkers propose replacing wireframes with sketches and prototypes; yet we need to understand that bridge between idea and specification.
Within this session, we’ll look at where wireframes originated, how we can use sketching to understand direction, and where prototyping helps communicate structure, purpose, and approach more effectively. Yet while some people want to evolve their product through prototyping, they miss a valuable opportunity: Solving design problems through prototypes. We’ll look at both, but I’ll make the argument that throwaway is often a better design tool.
What You’ll Learn:
The benefits of prototyping, both throwaway and evolutionary
Why throw away prototypes?
A case study showing a redesign process as an archetypal and practical approach