You’ve spent many hours conducting up-front research with your target users to understand their goals. You’ve solicited feedback from internal, subject-matter experts who are familiar with the business problem you’re collectively trying to solve. Finally, you’ve created design deliverables that represent what you believe are the most effective, efficient workflows for solving users’ problems. Now, you just have to get the product team and business stakeholders to buy into your solution.
Maybe you’re new to your product team and don’t feel that you have much influence capital. Perhaps you’re dealing with a product team that has never engaged the efforts of a UX designer in any official capacity—until now.
As someone who has often collaborated with multiple product teams at the same time—each of which might be in a different location, in a different phase of their product-delivery lifecycle, and using a different software-development methodology—I’ve concluded that there is no one method of delivering design work that guarantees its unquestioned adoption. Read More
In Part I of this series, I discussed two different approaches to wireframing:
separated code approach—in which the artifact you create to communicate your design is separate from the production code
integrated code approach—in which you use the same artifact for design and production code—creating code directly from wireframes
I examined the pros and cons of each of these approaches, as well as their impacts on the design process. In Part II, I’ll first explore what it would be like to instead go from code to wireframes. Then, for those of you who want to try employing a process flow that progresses from wireframes to code, I’ll discuss what types of prototyping tools would be best for your projects and how their use would impact your product development process. Read More
A prototype is a primitive representation or version of a product that a design team or front-end-development team typically creates during the design process. The goal of a prototype is to test the flow of a design solution and gather feedback on it—from both internal and external parties—before constructing the final product. The state of a prototype is fluid as the team revises the design iteratively based on user feedback.
Why Are Prototypes Important?
Tom and David Kelley of the design company IDEO have perfectly summed up the importance of prototyping by saying:
“If a picture is worth 1,000 words, a prototype is worth 1,000 meetings.” Read More