From “Hacking UX: better design for agile, lean, and waterfall teams” by Austin Govella, Oct 17, 2013 HACKING UX better design for agile, lean, and waterfall teams by Austin Govella @austingovella From “The Design Age: maximizing value in agile and lean teams” by Austin Govella, Feb 7, 2013 Zombies THE DIRECTOR’S CUT
In this presentation, learn how to hack UX Zombies to pieces using two tools: models and fidelity. You’ll be introduced to how to control the fidelity of our models, to hack UX for the right design.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
From “Hacking UX: better design for agile, lean, and waterfall teams” by Austin Govella, Oct 17, 2013
HACKING UXbetter design for agile, lean, and waterfall teamsby Austin Govella@austingovella
From “The Design Age: maximizing value in agile and lean teams” by Austin Govella, Feb 7, 2013
Zombies
THE DIRECTOR’S CUT
From “Hacking UX ZOMBIES: better design for agile, lean, and waterfall teams” by Austin Govella, Oct 17, 2013
Waterfall UX
UX Zombies
old fashioned
really, really slowobsessed with getting into
their users’ heads
From “Hacking UX ZOMBIES: better design for agile, lean, and waterfall teams” by Austin Govella, Oct 17, 2013
From “Hacking UX ZOMBIES: better design for agile, lean, and waterfall teams” by Austin Govella, Oct 17, 2013
UX Zombies
Super Lean UX
Team one, daily scrums, and a two week sprint.
We were adding functionality to let users access auto-generated data quality reports. Similar functionality (reports) existed elsewhere in the app, so the team got together, discussed the scenarios, and agreed to tweak an existing design pattern.
We sketched a few screens on the whiteboard, and we were done.
There were a couple of follow-up questions around how users would access the new screen, and we handled those with a couple of hallway conversations.
Just as your best thinker improves everything, that one person in your group who doesn’t understand user experience creates a drag on every product or service you produce. To create better experiences, you have to create better organizations. You have to improve your organ-ization’s design literacy. You have to improve the design literacy of everyone in the group.
From “Hacking UX ZOMBIES: better design for agile, lean, and waterfall teams” by Austin Govella, Oct 17, 2013
Manifesto
Organizations face common barriers to designing better experiences.
These barriers — value, focus, time, memory, talent, process, and improvement — represent the distance between you and the balanced teams your organization needs to create better experiences. Sometimes these cultural barriers are codified into your organization’s process. Sometimes they exist as hidden assumptions in your team member's minds.
From “Hacking UX ZOMBIES: better design for agile, lean, and waterfall teams” by Austin Govella, Oct 17, 2013
Manifesto
Don’t change what you do. Change how you do it.
Your design activities don’t change. Change how you work with your team. Change how you work, so your goal is always a better organization instead of a better product. Change how you accomplish the design, so that you are always improving your team’s design literacy.
From “Hacking UX ZOMBIES: better design for agile, lean, and waterfall teams” by Austin Govella, Oct 17, 2013
Understanding
Explicit Understanding
“View My Profile Page” tells your audience what that text does. It’s probably a link (even though it’s gray) , and it probably takes you to your “profile page”.
From “Hacking UX ZOMBIES: better design for agile, lean, and waterfall teams” by Austin Govella, Oct 17, 2013
Understanding
Implicit Understanding
Click the blue, post button once, and you learn it lets you post a new Tweet. At first glance, you don’t know what the blue button does, and the interface doesn’t tell you what it does, either.
From “Hacking UX ZOMBIES: better design for agile, lean, and waterfall teams” by Austin Govella, Oct 17, 2013
Annotation
Annotation Assists Fidelity
Annotation is a way of improving fidelity without improving fidelity. Parts of your model that require tacit or implicit understanding can be annotated, so your model