Download - Agile UX NYC 2012

Transcript
Page 1: Agile UX NYC 2012

The missing agile principle

Giff Constable Agile UX NYC

2/25/2012

Page 2: Agile UX NYC 2012

partner @ Proof"early stage specialist"skillset generalist"

16 years of startups"co-organizer, lean startup meetup"

WHO AM I?

Page 3: Agile UX NYC 2012

Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

Agile Manifesto’s First Principle

Page 4: Agile UX NYC 2012

Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

Agile Manifesto’s First Principle

Page 5: Agile UX NYC 2012

Valuable means delivering results to both the customer and the business and finding sustainable balance between the two.

Page 6: Agile UX NYC 2012

“Think about how your customer defines and would measure success using your application, and track that.”

Matt Meeker, VC@Polaris / Founder@Meetup

Page 7: Agile UX NYC 2012

What are your Key Performance Indicators?

Page 8: Agile UX NYC 2012

Agile can fall prey to focusing on process rather than value.

Page 9: Agile UX NYC 2012

“How do we know if it’s done?”"""“How do we know if it’s good?”

Lane Halley, LUXr

should become

Page 10: Agile UX NYC 2012

A story does not end at acceptance but rather must be validated for value.

ERIC RIES’ 4th STATE OF AGILE

Page 11: Agile UX NYC 2012

what about UX?

Page 12: Agile UX NYC 2012

UX should be the stewards of value.

Page 13: Agile UX NYC 2012

I’m not satisfied with what I hear the UX community talking about.

Page 14: Agile UX NYC 2012

But hey, UX is HOT right now!

Page 15: Agile UX NYC 2012

The spotlight will be short-lived without a focus on results, without tackling the language of business and not just languages of customer and design.

Page 16: Agile UX NYC 2012
Page 17: Agile UX NYC 2012

UX CAN’T LIMIT ITSELF TO THIS

Page 18: Agile UX NYC 2012

What need?"For whom?"How do we solve need?"How do we get customers?"How do we make money?"How do we beat competition?

UX OWNS THESE QUESTIONS

Page 19: Agile UX NYC 2012

We need a mental shift

become

become

become

requirements

designs

outputs

hypotheses experiments outcomes

Page 20: Agile UX NYC 2012

Work does not end at shipment but rather must be validated for value.

Agile UX Principle

Page 21: Agile UX NYC 2012

If you focus on results, and you communicate in terms of results, you will earn that seat at the table.

My “Career Advice” Hypothesis

Page 22: Agile UX NYC 2012

where to START?

Page 23: Agile UX NYC 2012

To accomplish this, you need to think like an owner.

Page 24: Agile UX NYC 2012

Think about product and value holistically.

Page 25: Agile UX NYC 2012

NO MORE US vs THEM

Page 26: Agile UX NYC 2012

Involve everyone early and stay transparent, even if it hurts at first.

Page 27: Agile UX NYC 2012

Tap into people’s pride. Everyone wants to work on something meaningful.

Page 28: Agile UX NYC 2012

Build a culture of hypotheses, not egos.

Page 29: Agile UX NYC 2012

Mentor and get mentored across functional lines.

Page 30: Agile UX NYC 2012

Get scrappy. "Don’t wait for permission."Be persistent."And broadcast the wins.

Page 31: Agile UX NYC 2012

Don’t be afraid to measure."

OWN RESULTS.

Page 32: Agile UX NYC 2012

Ultimately, work is meaningless unless we create something valuable.

Page 33: Agile UX NYC 2012

Work should begin with the hunt for value, and not end until value has been validated.

The Principle I Try To Uphold

Page 34: Agile UX NYC 2012

[email protected]""

@GIFFCONSTABLE


Top Related