agile ux - lightweight deliverables for when you need ux governance

Post on 19-Nov-2014

1.301 Views

Category:

Technology

7 Downloads

Preview:

Click to see full reader

DESCRIPTION

Despite our best intentions you may find persistent governance problems on your team. UX professionals are, after all, in high-demand and we often find ourselves in teams of one. Starting with a loose case-study/post-mortem of my work and my recommendations, this session invites us all to consider the little things we can do to make sure everyone on your team is thinking about UX.

TRANSCRIPT

WHEN YOU NEED UX GOVERNANCE

Stephen Nguyen

stephen.nguyen.b@gmail.com

www.linkedin.com/in/stephennguyenuxUXCAMP DC – January 4, 2014

CORPORATE USABILITY MATURITY http://www.nngroup.com/articles/usability-maturity-stages-1-4/

STAGES 1-41. Hostility Toward Usability2. Developer-Centered Usability3. Skunkworks Usability4. Dedicated Usability Budget

CORPORATE USABILITY MATURITY http://www.nngroup.com/articles/usability-maturity-stages-1-4/

STAGES 1-41. Hostility Toward Usability2. Developer-Centered Usability3. Skunkworks Usability4. Dedicated Usability Budget

CURRENTLY

CURRENTLY

+

CURRENTLY

+ =

CURRENTLY (disclaimer)

+ =

AGILE! (woo!)

What we want:• Individuals over processes and tools• Working software over comprehensive documentation

AGILE! (woo!)

What we want:• Individuals over processes and tools• Working software over comprehensive documentation

But what we often get…

AGILE! (woo!)

AGILE! (woo!)http://dilbert.com/strips/comic/2007-02-02/

AGILE! (woo!)

1. Customer satisfaction by rapid delivery of useful software2. Welcome changing requirements, even late in development3. Working software is delivered frequently (weeks rather than months)4. Working software is the principal measure of progress5. Sustainable development, able to maintain a constant pace6. Close, daily cooperation between business people and developers7. Face-to-face conversation is the best form of communication (co-location)8. Projects are built around motivated individuals, who should be trusted9. Continuous attention to technical excellence and good design10. Simplicity—the art of maximizing the amount of work not done—is essential11. Self-organizing teams12. Regular adaptation to changing circumstances

AGILE! (woo!)

6. Close, daily cooperation between business people and developers7. Face-to-face conversation is the best form of communication (co-location)8. Projects are built around motivated individuals, who should be trusted9. Continuous attention to technical excellence and good design

AGILE! (woo!)

6. Close, daily cooperation between business people and developers7. Face-to-face conversation is the best form of communication (co-location)8. Projects are built around motivated individuals, who should be trusted9. Continuous attention to technical excellence and good designHow can you make sure the user is represented in all these conversations?

ENFORCE A COMMON LANGUAGE

Page vs. Sheet

Report

(Subject 1) Page

(Subject 2) Page

(Subject 2) PageSheet 1

(Subject 2) PageSheet 2

(Subject 2) PageSheet 3

ENFORCE A COMMON LANGUAGE

Window vs. Menu; Dialogue vs. Dialog

MAKE SURE IT’S MAINTAINABLE

• Developer classes/methods/resources

Exams > Loaded Exams > My ExamseditExamProfile > editExamDetails

edit_exams_active.png

OBVIOUS SOLUTIONS

• Personas• Scenarios• Models/Maps• Style Guides

(LESS) OBVIOUS SOLUTIONS

• Pattern Libraries (Collaborative and Functional)

(LESS) OBVIOUS SOLUTIONS

• Pattern Libraries (Collaborative and Functional)

(LESS) OBVIOUS SOLUTIONS

• Pattern Libraries (Collaborative and Functional)• Glossaries

(LESS) OBVIOUS SOLUTIONS

• Pattern Libraries (Collaborative and Functional)• Glossaries• Team Wiki

(LESS) OBVIOUS SOLUTIONS

• Pattern Libraries (Collaborative and Functional)• Glossaries• Team Wiki• Usability Testing Videos

(LESS) OBVIOUS SOLUTIONS

• Pattern Libraries (Collaborative and Functional)• Glossaries• Team Wiki• Usability Testing Videos• Other Information Radiators

“DEVELOPERS DON’T CARE ABOUT THAT STUFF”Information Radiators:• Are large and easily visible to the casual, interested observer

(Developers don’t care)• Are understood at a glance• Change periodically, so that it is worth visiting• Are easily kept up to date

“DEVELOPERS DON’T CARE ABOUT THAT STUFF”Information Radiators:• Are large and easily visible to the casual, interested observer

(Developers don’t care)• Are understood at a glance• Change periodically, so that it is worth visiting• Are easily kept up to date

You need to become a living, breathing, walking, talking information radiator.

(LESS) OBVIOUS SOLUTIONS

• Pattern Libraries (Collaborative and Functional)• Glossaries• Team Wiki• Usability Testing Videos• Other Information Radiators

(LESS) OBVIOUS SOLUTIONS

• Pattern Libraries (Collaborative and Functional)• Glossaries• Team Wiki• Usability Testing Videos• Other Information Radiators• Meetings!

KEEP IN MIND

• You have limited social/project capital – use it wisely

KEEP IN MIND

• You have limited social/project capital – use it wisely• Never let anything die on the vine – don’t start

something you know you can’t finish

KEEP IN MIND

• You have limited social/project capital – use it wisely• Never let anything die on the vine – don’t start

something you know you can’t finish• You must always champion UX wherever possible.

top related