70
Redesign Must Die Louis Rosenfeld • Rosenfeld Media Orlando, Florida • 18 February 2014

Redesign Must Die (updated Feb 2014)

Embed Size (px)

DESCRIPTION

A radically updated version of a talk I initially gave in 2009 or thereabouts. Presented at InControl, Orlando, FL, USA, Feb 18, 2014.

Citation preview

Page 1: Redesign Must Die (updated Feb 2014)

Redesign Must Die

Louis Rosenfeld •  Rosenfeld Media

Orlando, Florida •  18 February 2014

Page 2: Redesign Must Die (updated Feb 2014)

1998: Ann Arbor, Michigan

Page 3: Redesign Must Die (updated Feb 2014)

Before the redesign

Page 4: Redesign Must Die (updated Feb 2014)

Before the redesign

Page 5: Redesign Must Die (updated Feb 2014)

Before the redesign

Page 6: Redesign Must Die (updated Feb 2014)

Before the redesign

Page 7: Redesign Must Die (updated Feb 2014)

A Ribbon Cutting

Page 8: Redesign Must Die (updated Feb 2014)

After the redesign

Page 9: Redesign Must Die (updated Feb 2014)

After the redesign

Page 10: Redesign Must Die (updated Feb 2014)

After the redesign

Page 11: Redesign Must Die (updated Feb 2014)

After the redesign

Page 12: Redesign Must Die (updated Feb 2014)

1998

Page 13: Redesign Must Die (updated Feb 2014)

1998 2000

Page 14: Redesign Must Die (updated Feb 2014)

1998 2000

2003

Page 15: Redesign Must Die (updated Feb 2014)

1998 2000

2003 2005

Page 16: Redesign Must Die (updated Feb 2014)

1998 2000

2003 2005

2007

Page 17: Redesign Must Die (updated Feb 2014)

1998 2000

2003 2005

2007 2010

Page 18: Redesign Must Die (updated Feb 2014)

And now

Page 19: Redesign Must Die (updated Feb 2014)

And now

Page 20: Redesign Must Die (updated Feb 2014)

And now

Page 21: Redesign Must Die (updated Feb 2014)

And now

Page 22: Redesign Must Die (updated Feb 2014)

“Insanity is doing the same thing over and over again but expecting different results.”

Page 23: Redesign Must Die (updated Feb 2014)

“Insanity is doing the same thing over and over again but expecting different results.”

individualvanity

Page 24: Redesign Must Die (updated Feb 2014)

“Insanity is doing the same thing over and over again but expecting different results.”

& organizational stupidity

individualvanity

Page 25: Redesign Must Die (updated Feb 2014)

Who’s to blame?

Who’s to blame?

Page 26: Redesign Must Die (updated Feb 2014)

Attempting the impossible “boil the ocean” in no time at great cost

Believing the unbelievable unwarranted claims from agencies and software vendors

Becoming irresponsible unwarranted declarations of victory at the expense of our teams and users

Misdiagnostics

Page 27: Redesign Must Die (updated Feb 2014)

1993: Ann Arbor, Michigan

Page 28: Redesign Must Die (updated Feb 2014)

Entity consisting of many diverse and autonomous components or parts (called agents) which are interrelated, interdependent, linked through many (dense) interconnections, and behave as a unified whole in learning from experience and in adjusting (not just reacting) to changes in the environment.

Complex Adaptive Systems

Page 29: Redesign Must Die (updated Feb 2014)

Examples of CAS

Page 30: Redesign Must Die (updated Feb 2014)

Examples of CAS

Page 31: Redesign Must Die (updated Feb 2014)

Examples of CAS

Page 32: Redesign Must Die (updated Feb 2014)

Your site is a moving target built on moving targets

Page 33: Redesign Must Die (updated Feb 2014)

Your site is a moving target built on moving targets

Control this?

Page 34: Redesign Must Die (updated Feb 2014)

So who’s to blame?

Page 35: Redesign Must Die (updated Feb 2014)

So who’s to blame?

No one and everyone

Page 36: Redesign Must Die (updated Feb 2014)

How to stop playing God in 5 easy steps

1. Swap control for prioritization

2. Embrace evolution over revolution

3. Emphasize process over projects

4. Use anchors to counterbalance reaction

5. Sneak in governance at the grass roots

Page 37: Redesign Must Die (updated Feb 2014)

1. Swap controlfor prioritization

Page 38: Redesign Must Die (updated Feb 2014)

A little goes a long wayA handful of queries/tasks/ways to navigate/features/ documents meet the needs of your most important audiences

Page 39: Redesign Must Die (updated Feb 2014)

A little goes a long wayA handful of queries/tasks/ways to navigate/features/ documents meet the needs of your most important audiences

Page 40: Redesign Must Die (updated Feb 2014)

A little goes a long wayA handful of queries/tasks/ways to navigate/features/ documents meet the needs of your most important audiences

Page 41: Redesign Must Die (updated Feb 2014)

A little goes a long wayA handful of queries/tasks/ways to navigate/features/ documents meet the needs of your most important audiences

Page 42: Redesign Must Die (updated Feb 2014)

A little goes a long wayA handful of queries/tasks/ways to navigate/features/ documents meet the needs of your most important audiences

Page 43: Redesign Must Die (updated Feb 2014)

(and the tail is quite long)

Page 44: Redesign Must Die (updated Feb 2014)

(and the tail is quite long)

Page 45: Redesign Must Die (updated Feb 2014)

(and the tail is quite long)

Page 46: Redesign Must Die (updated Feb 2014)

(and the tail is quite long)

Page 47: Redesign Must Die (updated Feb 2014)

(and the tail is quite long)

Page 48: Redesign Must Die (updated Feb 2014)

Zipf in text

Page 49: Redesign Must Die (updated Feb 2014)

Zipf is The Truth

Not just search queries, but...

• Documents

• Features

• Audience segments

• and more...

Page 50: Redesign Must Die (updated Feb 2014)

George Zipf, your portfolio manager

layer information architecture

usability content strategy

0

1

2

3

4

indexed by search engine

leave it alone leave it alone

tagged by users squeaky wheel issues addressed

refresh annually

tagged by experts (non-topical tags)

test with a service (e.g., UserTesting.com)

refresh monthly

tagged by experts (topical tags)

“traditional” lab-based user testing

titled according to guidelines

deep links to support contextual navigation

A/B testing structured according to schema

Each layer iscumulative

Page 51: Redesign Must Die (updated Feb 2014)

Prioritize each step...

...into a report card...

...then rinseand repeat

More here:http://tinyurl.com/84yxpoo

Page 52: Redesign Must Die (updated Feb 2014)

2. Embrace evolution over revolution

Page 53: Redesign Must Die (updated Feb 2014)

What do they want and when do they want it?

Page 54: Redesign Must Die (updated Feb 2014)

Closer look

Page 55: Redesign Must Die (updated Feb 2014)

IRS before taxes due

Page 56: Redesign Must Die (updated Feb 2014)

IRS before taxes due

Page 57: Redesign Must Die (updated Feb 2014)

IRS after taxes due

Page 58: Redesign Must Die (updated Feb 2014)

3. Emphasizeprocess over projects

Page 59: Redesign Must Die (updated Feb 2014)

Keeping design and research “regular”...

Example: the rolling content inventory

Page 60: Redesign Must Die (updated Feb 2014)

Moving from process to cadence

Page 61: Redesign Must Die (updated Feb 2014)

Cadence in text

WeeklyWeeklyWeekly

Call center data trend analysis 2 – 4 hours behavioral/quantitative

Task analysis 4 – 6 hours behavioral/quantitative

QuarterlyQuarterlyQuarterly

Exploratory analysis of site analytics data 8 – 10 hours behavioral/qualitative

User survey 16 – 24 hours attitudinal/quantitative

AnnuallyAnnuallyAnnually

Net Promoter Score study 3 – 4 days attitudinal/quantitative

Field study 4 – 5 days behavioral/qualitative

Page 62: Redesign Must Die (updated Feb 2014)

4. Use anchors to counterbalance reaction

Page 63: Redesign Must Die (updated Feb 2014)

pace layering

Page 64: Redesign Must Die (updated Feb 2014)

Anchors are familiar beasts

• Charter statement

• Mission statement

• Vision statement

• Values statement

http://www.gogamestorm.com/

Page 65: Redesign Must Die (updated Feb 2014)

Ultimately you’re flying the airplane while fixing it5. Sneak in governance at the grass roots

Page 66: Redesign Must Die (updated Feb 2014)

Ultimately you’re flying the airplane while fixing it5. Sneak in governance at the grass roots

Page 67: Redesign Must Die (updated Feb 2014)

Buy candy for strangers

Page 68: Redesign Must Die (updated Feb 2014)

Develop a pidgin

Dave Gray’s boundary matrix: http://bit.ly/gWoZQm

KPI

goals

segments

personas

Page 69: Redesign Must Die (updated Feb 2014)

It ain’t easy, but...

1. Swap control for prioritization

2. Embrace evolution over revolution

3. Emphasize process over projects

4. Use anchors to counterbalance reaction

5. Sneak in governance at the grass roots

Page 70: Redesign Must Die (updated Feb 2014)

Say hello

Lou Rosenfeld

Rosenfeld Media 

www.louisrosenfeld.com • @louisrosenfeldwww.rosenfeldmedia.com • @rosenfeldmedia