Alonso Loera

Experience Designer

II. The versatility of pen and paper


A lean UX approach is a powerful and collaborative tool within product design that aims to solve problems for users. It is crucial that a UX designer or team be flexible in its approach, and focused on solving a problem or problems rather than creating the next awesome product or feature. This allows for continual testing both before and after a product launch to improve the usability for its users. On the other end, namely in enterprise, redesigns of existing products or services is less flexible in offering creative solutions, but lean UX still offers benefits in gaining a better understanding of the behaviors of the users and offering genuine opportunities to improve the customer experience for any organization. From user discovery, we have a set of assumptions taken from user feedback that afford us the blueprint to solving identifiable problems, and user scenarios & flows can be iterated.
Flow diagram for one specific user
Flow diagram for multiple users


Good user centered design is invisible to the audience. As UX designers, we are not tasked to merely offer answers by our own logic. We are meant to identify usability problems, user behaviors and available solutions provided by the intended audience themselves. Usability data offers a vast amount of valuable knowledge for anyone creating a product or service, and helps with both core features for MVPs or expanding features for an existing product. When introducing concepts, sketching of the interface is invaluable to attaining that knowledge.
What began as identification of all elements of user feedback and overall knowledge of the users eventually segued into usability and feature identification. For Quipley, we identified the core features of the current desktop experience, translated these features for mobile devices, and began with an MVP approach to the interface. From core features to additional feature sets, we were able to craft a possible universe for Quigley's mobile experience.
User Scenarios
Wireframing bonus feature sets

Let's View Step III