practical ux: a future friendly approach to communicating your ideas

Download Practical UX: A Future Friendly Approach to Communicating Your Ideas

Post on 17-Aug-2014




0 download

Embed Size (px)


Much of the conventional design process and documentation we rely on is ineffective when it comes to communicating how we want our designs to translate across a wide range of devices and screen sizes. This talk is all about producing effective, efficient deliverables for an increasingly mobile-accessed Web, and practical design methods you can put into use right away. But there's a catch: shaking up convention doesn't always come easy. How do you move away from assembly line design processes and an over-reliance on static deliverables? How do you overcome your stakeholders' general misconceptions about mobile use cases? If you've got a chance in hell of getting away with it all, you'll need a few tricks up your sleeve. This session will cover collaborative sketching methods perfect for breaking mental models and building design consensus. We'll investigate the seeming demise of Photoshop, and you'll hear a whole lotta talk about prototypes—including when and why to use them, and how to pick the best prototyping tool for your project. For designers and developers alike, you'll leave with a toolbox of tricks that can help you pitch your future friendly ideas.


  • User Research Stakeholder Interviews Personas & Scenarios Card sorting enormous Sitemap Lotsa Wireframes Task flows design compS Prototypes Device testing usability testing+
  • The Deliverables Business
  • But WILL the People know to tap it?
  • Makers wanna make... not document
  • How much of the UX process is expendable?
  • Future Friendly
  • -there is a- Dissonance of Vision Future Friendly vs. BOSS Phone
  • -Dan Willis ...the people farthest from understanding the technology are often the ones making the strategic decisions. Dan Willis
  • Its up to those with the best understanding of the technology to lead the way.
  • Crossing the Chasm
  • The biggest challenges, in my experience, are to do with people. Specically, the way that people work together. Jeremy Keith Jeremy Keith
  • Arm yourself with better communication tools
  • The purpose of a design artifact, whether a wireframe, prototype or sketch, is to illustrate our thinking. Robert Hoekman
  • The purpose of a design artifact can also be to transform our thinking
  • Create Props NOT Paperwork
  • Assumptions | Shared understanding Silo mentality | Convergent experience Page driven design | Design systems
  • Prototyping the Experience
  • Participatory Sketching Getting stubborn ideas out of peoples heads and onto paper.
  • Comics & Storyboards Great for getting to people focus on goals and scenarios instead of features and screens.
  • Role Playing / Bodystorming Performing the experience
  • Journey Maps / Service Blueprints Outlining the various points where users interact with a product or service, across channels. Can weave together personas, scenarios, and tasks.
  • User Journey map became more than just a journey with touchpoints, emotions, takeaways, etc... Jeremy Keith
  • It also became a representation of the Information Architecture and the content plan, with our Personas (needs, goals, scenarios) serving as the starting point for everything sort of like the glue that ties it all together. Jeremy Keith Rian Van Der Merwe
  • Find gaps in the experience.
  • Paper Prototypes Quickly ideate and validate ideas.
  • KJ Method An ecient way to arrive at consensus when dealing with large or divided groups.
  • The Page Description Diagram
  • Page Tables / Content Outlines
  • Design Systems Breed Modular Markup & CSS
  • Wireframes*. Component Audits and Content Reference Wireframes
  • HTML Prototypes (or mobile app prototypes)
  • Style Prototypes & Guides
  • Facilitation.
  • Design Studio Design Mini Brief + Structured Rules for Critique
  • Totally arbitrary re-prioritization of objectives incoming!
  • Pace The Conversation Focus on one thing at a time
  • Project paralysis...
  • UX is a result... not a document.
  • PREPARING for whats to come
  • You are ALL architects of the user experience.
  • THANKS! Dennis Kardys @dkardys


View more >