"product design" entries
The O’Reilly Design Podcast: Aaron Irizarry on getting and keeping a seat at the table.
Subscribe to the O’Reilly Design Podcast to explore how experience design — and experience designers — are shaping business, the Internet of Things, and other domains.
Welcome to the inaugural episode of our newly launched O’Reilly Design Podcast. In this podcast episode, I chat with Aaron Irizarry. Irizarry is the director of UX for product design at Nasdaq, co-author of “Discussing Design” with Adam Connor, and a member of the program committee for O’Reilly’s Design Conference.
Design at Nasdaq: A growing team
I first noted Nasdaq’s commitment to design when talking to Irizarry about his book and the design conference hosted by Nasdaq that Irizarry helps develop:
It’s interesting to see an organization that didn’t have a product design team as of, what — 2011, I believe. To see the need for that, bring someone in, hire them to establish a team (which is my boss, Chris), and then see just the transition and the growth within the company, and how they embraced product design. We had to work a lot, and really educate and pitch in the beginning, explain to them the value of certain aspects of the job we were doing, whether that was research, usability, testing, why we were wanting to do more design of browser and rapid prototyping, and things like that.
We believe we’re helping structure and build, and I think we still have work to do as a design-led organization. We recently did our Pro/Design conference in New York. Our opening speaker was the president of Nasdaq, and to hear her reference the design team’s research, and to be in marketing meetings, and discussing the personas that we created, and to hear the president of Nasdaq speak about these kind of artifacts and items that we feel are crucial to design and the design process, it was a mark for us like, ‘We’re really starting to make a mark here. We’re starting to show the value of what these things are,’ not just because we want design, but we believe that this approach to design is going to be really good for the product, and in the end, good for the business. Read more…
Design Sprints bring clarity to your roadmap to kickstart and obtain initial validation for product design work.
Download a free copy of “The New Design Fundamentals” ebook, a curated collection of chapters from our Design library. Note: this post is an excerpt from “Design Sprint,” by Richard Banfield, C. Todd Lombardo, and Trace Wax, which is included in the curated collection.A Design Sprint is a flexible product design framework that serves to maximize the chances of making something people want. It is an intense effort conducted by a small team, where the results will set the direction for a product or service.
The Design Sprint consists of five discrete phases:
- Understand (review background and user insights)
- Diverge (brainstorm what’s possible)
- Converge (rank solutions, pick one)
- Prototype (create a minimum viable concept)
- Test (validate with users)
A Design Sprint reduces the risk of downstream mistakes and generates vision-led goals the team can use to measure their success. For the purpose of this book, we’ll focus on digital products since our direct experience lies in that arena, though the Design Sprint has roots in gaming and architecture, and many industries have employed them successfully. Read more…
A design process paved with empathic observations will lead you, slowly and iteratively, to a better product.
Editor’s note: this post was originally published on the author’s blog, Exploring the world beyond mobile; this lightly edited version is republished here with permission.
If I’m ever asked what’s most important in UX design, I always reply “empathy.” It’s the core meta attribute, the driver that motivates everything else. Empathy encourages you to understand who uses your product, forces you to ask deeper questions, and motivates the many redesigns you go through to get a product right.
But empathy is a vague concept that isn’t strongly appreciated by others. There have been times when talking to product managers that my empathy-driven fix-it list will get a response like, “We appreciate that Scott, but we have so much to get done on the product, we don’t have time to tweak things like that right now.” Never do you feel so put in your place when someone says that your job is “tweaking.”
The paradox of empathy is that while it drives us at a very deep level, and ultimately leads us to big, important insights, it usually starts small. The empathic process typically notices simple things like ineffective error messages, observed user workarounds, or overly complicated dialog boxes. Empathy starts with very modest steps. However, these small observations are the wedge that splits the log; it’s these initial insights, if you follow them far enough, that open up your mind and lead you to great products.