Download - Staying on target with IBM Design Thinking and Lean UX

InfoSphere Data Explorer, Big Data

UX Lead and Development Manager

Ariadna Font Llitjós, PhD

Staying on Target with IBM Design Thinking & Lean UX

@quicola #designthinking #leanux @ibmdesign

InfoSphere Data Explorer :: ©2013 IBM Corporation

Acquisition

2

Vivisimo

Company size 120

Engineering size 30

Cross-functional team size 4

Enterprise search

June 2012 (TOB - January 2013)

IBM, Big Data

430,000

40+

10

Big Data exploration &visualization

InfoSphere Data Explorer :: IBM Confidential :: ©2013 IBM Corporation

Focused vision and target

vs.

Overstimulating environment & developing market

3


IBM Design Thinking to the rescue

6


— Don Norman

“Designers [...] don't try to search for a solution until they

have determined the real problem, and even then,

instead of solving that problem, they stop to consider a

wide range of potential solutions.

Only then will they finally converge upon their proposal.

This process is called ‘design thinking.’”

7

“Rethinking Design Thinking” Core77, 19 March, 2013


— Don Norman







8



— Don Norman







9



— Don Norman







10


InfoSphere Data Explorer :: IBM Confidential :: ©2013 IBM Corporation 11

IBM Design Thinking is about creating great experiences for our users.


This is not a user experience

12

This is a user experience


PRODUCT UX UI

SERVER DATA CENTER


PRODUCT UX UI

SERVER DATA CENTER

PRODUCT UX UI

SERVER DATA CENTER


— Thomas Watson Jr.

“Good design is good business.”

16

Chief Executive Officer, 1973


IBM Design Thinking: Scaling great designKey building blocks for consistently great design outcomes

17



17

Sponsor Clients/UsersContinuous engagement with people in target roles and industry domains



17

Release HillsFocused investment, empowered teams


IBM Designcamp :: IBM Confidential :: ©2013 IBM Corporation

3 Release Hills focus and empower teamsLess micro-management and more iteration

18

Example of a Release Hill:

“A business user should be able to create and start using a process application in less than 60 seconds”

A Release Hill captures the Commander’s intent

“a framework for freedom to act”



19





19



PlaybacksRelentless focus on user value and experience throughout the development process

• Story-driven milestones led by users

• Playback Zero: Align on product vision before coding

• Interim Playbacks: Demo stories in executable code


Demo features & functionality

vs.

Demo experience as a narrative


Quotes from Playback 1

— Manuel Corniel, WW Sales Exec Big Data, Data explorer

“I’d love to have you present this to the sales teams the same way, it tells the entire story...”


Quotes from Playback 1

— Charlie Hill, CTO Design

“To me it’s like nirvana, you’re getting a non-mediated demo (directly from the user).”



23









23



Product Management

Wiki-based Release DocumentsEfficient cross-functional collaboration around peer-reviewed artifacts

Design

Engineering






personas

24


user stories & interactions

personas

24


sketches


personas

24


sketches


personas

24

visual prototypes


field testing

sketches


personas

24

visual prototypes


field testing

sketches


personas

24

visual prototypes

releaseblueprint



25



Product Management


Design

Engineering







25



Product Management


Design

Engineering





1:9

ReleaseBlueprint URL

Organizationdata

Skills ratios

Dependencies

Design team skills data

Release Hills

Lead Users

IBM DesignThinkingMetricsVisibility into objective operational data


Where were we?

26


What else changed?

29


Colocated team

vs.

Distributed team (2/10 remote devs - still more colocated than most IBM teams)

30


Non-dedicated design resources

vs.

Dedicated design resources(2 UX designers, 2 front-end devs / 3 app devs, 3 backend devs)

31


Access to end users

vs.

Sponsor clients and users

32

Dev UX PM

vs.

Dev UX PM


InfoSphere Data Explorer :: ©2013 IBM Corporation

Lean UX Principles

34

• Design Thinking

• User-centric design and development

• Cross-functional team

• Maximize learning

• Just-in-time (minimize waste)

• Validate and iterate


Things that remained the same

35

Agile & Lean practices for over 5 years

InfoSphere Data Explorer :: ©2013 IBM Corporation 36

• startup culture

• XP practices (continuous integration, peer reviews, unit tests, pair programming, ...)

• design studios (collaborative design workshops)

• Kanban

• stories

• daily standups

• demos

• retrospectives


Design and development flow

37


1. Brainstorm and scope as a team


2. Workflow and creating epics


3. Breaking epics down to stories that can be designed / implemented


4. Design, validate, implement, polish design


5. One day in the Pittsburgh Big Data lab...

Team daily standup

Designers and developers at work


6. Designer shares design and gets feedback from Dev

ARIADNA FONT | @QUICOLA @IBMDESIGN @LEANUX

7. Dev works on implementing the design


8. Dev proudly shows the implementation with the final design to designer


Key aspects

One team with shared core values

Daily high-bandwidth communication

Iterate - don’t let perfection be the enemy of good


What about outcomes?

47


Before...


Now


Responsive design (mobile friendly)


InfoSphere Data Explorer 9.0

1st Signature Product released!

55

Can’t dictategreat outcomes

PROCESS

PROCESS

Not a new way of acting, a new way of thinking

Can prepare for

great outcomes


June 2012


October 2013

We managed to bring IBM along and

leverage IBM’s channels

IBM Design Thinking

61

IBM Design Thinking&

Lean UX

62

Thanks!

63

@quicola #designthinking #leanux @ibmdesign


References

64


Engineering and coding practices

65

Download - Staying on target with IBM Design Thinking and Lean UX

Top Related