By and large our focus in recent times has been on websites and apps, but increasingly we are going to be asked to design things in physical contexts; terminals, IoT devices, lifts. We talk to Kevin Cannon about ergonomics and UX design – The meeting point of traditional UX and industrial design.
Jaime Levy joined us in the green room at From Business To Buttons. We talked about Jaime’s Hyperloop study – the personal journey that led her here and why. We talk about the importance of having mentors and heroes no matter where you are on your career path and the importance of validating the problem before diving in to designing the solution.
We don’t generally have a problem considering objects from the past. Speculating about what they are and how they might have been used. We could look at artefacts from the future in a similar manner. We talk to Leo Frishberg about presumptive design and how you can use that as a provocative design research tool.
James, Per and Danwei open the video channels for the 6th UX Podcast Listener phone-in. We’ve pulled out the highlights from the live session and made them into 2 separate episodes.
The topics covered in part 2 of this two-part episode are: The battery status API – how can we make use of that in UX? User off-boarding – how do we let users go gently? Prototyping tools – which tool is best?
Part 1 can be found here.
(Listening time: 36 minutes)
— UX Podcast (@uxpodcast) April 8, 2016
- The Battery Status API
- The Dirt Podcast: User off-boarding
- Johan’s list of prototyping tools: Adobe Xd, Adobe Photoshop (plugin Craft), Axure RP v7, Balsamiq, Fusetools, inVision, Proto io, Prott Sketch (plugin Craft) and Zurb.
- Made with AdobeXD hashtag on Twitter
My favorite takeaway from today's @uxpodcast is to work with your creative partner to determine the best prototyping tool for both parties.
— Sarah Keane (@sarah_keane) March 18, 2016
How do you build a minimum viable product? Inspired by a Twitter conversation, we talk to Russ Unger, Stephen Anderson and Jeff Gothelf about what MVP is, what it isn’t. Does it cause more confusion than add value? What are we trying to learn and validate? We get some hangups off our chests, and discuss how you and your product team can avoid some of the MVP pitfalls.