Work Different

People forget what they just did — so this is an issue when we test.

“mute” on mic — it is a mute button! People are expecting a power button

Jacob Nielson

Honeycomb: value at center

Usable, useful, desirable, accessible, credible, findable /valuable

Heuristic evaluations can be complete

(There is a book on web form design!?)

He thinks eye tracking a bit like phrenology ( figuring out if you right for a job based on head shape), but good thing is that found out recruiters spend seconds on your resume, not self-reported 5 minutes

Great slide on The Ladders method – plan every Friday

Looking for boulders not pebbles in usability testing that can get into sprint fast

Product Design Guild guy on testing beer prototyping, by second beer you will see how they really interact with your product

Cash get people in the door. Gift cards cause bias.

Can present with wireframes and say what are you looking at and what would you do next.

Make sure in testing you make clear to test subject we are testing product NOT user. If there are products is because designed poorly.

Ask good questions, that get at what is in user’s head. Open-ended questions, that invite them to think.

[Keeps mentioning book titles super-fast, I can’t catch titles. 😉 ]

No recruiter reads that resume summary at top. Look for education.

Do an affinity grouping by key findings.

New idea to get devs and design working together.

Talking about pain of visual designers in Agile world. Prototype to iteration.
Talks about difficulty of iterating the look and feel.

The Art of Maximizing Work Not Done — in daily work hard to figure out and get it to where user understands.

Talked about typical issues of teams sharing files. And naming convention issues.

What to do to fix these problems. We need continuous deployment of design. Actually rapid actually useful prototyping. Maybe we can do prototypes instead of mockups.

Designer developer collaboration.

Easy discovery, not ten people asking for same file. Shared vocabulary for file naming.

Atomic

Assets
To
Markup
Iterative
Collaboration

Design strategy cake:

Brand guideline
Component library
Pattern library

Patterns-set of styles
Component chunk of page design

Shows a search in four states. A re-usable component throughout site.

Define component vs pattern for your project.

Design components first then continue with pages.

Hardcore old school print designers know papers, know inks, know fonts. By same token, we creating UX must be literate in code.

Literacy!= Fluency — it is just being able to know enough of a language to have a decent conversation

Believes in a few years we won’t hire designers that can’t code. (Makes me think of LukeW who says in future we won’t have time for wireframes.)

Making is good for projects. Small details of color and font are important to the user. If you can just fix it yourself it is much faster.

Instead of telling someone else how to paint, you get to hold the brush.

Caveat is can step on toes. Use humility. Establish the spots okay to do.

TDD and Story writing using Cucumber.. Getting right syntax. Helped his UX/UI practice be because used ubiquitous language, as devs

Ask devs to have basic tools ( like in rails bundled, rake, etc)

So can do small changes, GIT allows you to save, like in a vid game.

Can contribute to production and they can role it back.

Learned Rspec and Capybara test programs
Know about breakages quickly from these

JQuery helps you write sonnets or paint inside the lines

Uses personas a lot, within cucumber

Testers will use Homer Simpson as the persona if you don’t supply!

“it is critically important to do things not just read about them” (or just attend classes and conferences haha).