Noah Iliinsky is the co-editor of Beautiful Visualizations. He examines complex data and the ways to effectively communicate it visually to audiences. In this podcast, Noah joins Jared Spool for a discussion about how to interpret information visually in a way that is most effective for users to process the information and be successful in their tasks.
adactio / collective / tags / uie
Tagged with “uie”
(4)
-
Noah Iliinsky – The Steps to Beautiful Visualizations » UIE Brain Sparks
Tagged with noah iliinsky visualizations uie
-
Noah Iliinsky – Beautiful Visualization: Letting Data Tell the Story » UIE Brain Sparks
Tagged with noah iliinsky beautiful visualizations data uie
-
Jared Spool: Revealing Design Treasures from the Amazon
The audio was recorded at An Event Apart Seattle 2009. The session description was as follows:
On its surface, Amazon.com just seems like a large e-commerce site, albeit a successful one. Its design isn’t flashy, nor is it much to write home about. But deep within its pages are hidden secrets — secrets that every designer should know about.
If one looks closely at what the team at Amazon has built, it’s filled with innovative functionality and clever designs, all of which creates a delightful experience for its users and directly produces regular profits for its shareholders. But not all is perfect. Some design changes in the last few years have not been the success that the team had hoped for. Amazon’s exceptional qualities and imperfections are critical knowledge for any designer that wants to dig deep into what makes the site tick.
In this entertaining presentation, Jared will share some of UIE’s latest research into the hidden treasures of (the) Amazon. You’ll learn:
- The simple Yes/No question that increased revenues by more than $1 billion
- The elegant subtlety of Amazon’s security system
- Why Amazon’s business model is more than meets the eye (and why designers need to care) The wins and losses that Amazon has had with social media functionality
-
SpoolCast: Achieving Pattern and Component Reuse with Nathan Curtis
In our discussion, Nathan and I first defined design pattern libraries and component libraries. A pattern library is a repository for ideas and solutions to design interaction problems. Component libraries are comprised of actual functioning parts with real code. An example would be a log-in process. Your pattern would define the experience of logging into your application, from the interaction, and often visual standpoint. Your component would be the chunk of code that represents the set of fields and controls that can be replicated across your organization’s web properties, so that you can easily create a consistent experience for your users, no matter where they may enter your system.