Advancing UX in Your Organization (TorCHI Talk - December 12, 2013)

Advancing UX in Your Organization

Kimberley Peter User Experience Design Lead IBM Rational Software Toronto, Ontario [email protected] @kpeter

Adam Archer Technical Lead, JazzHub IBM Rational Software Toronto, Ontario [email protected] @agarcher

IBM Rational . TorCHI - December 12, 2013 . Advancing UX in Your Organization, Kim Peter and Adam Archer ©2013!

Topic Duration

Introductions + overview 10 min

Topic 1 : Motivation 15 min

Activity 1 15 min

Topic 2 : Context 15 min

Activity 2 20 min

Topic 3 : Solutions 15 min

Conclusion 5 min

Discussion + wrap! 15 min

IBM Rational . TorCHI - December 12, 2013 . Advancing UX in Your Organization, Kim Peter and Adam Archer ©2013! 2!

Our plan in detail


Introductions + Overview

3!

About ‘us’


Kimberley Peter Designer

Adam Archer Software Engineer

Our plan today …


Motivation Consider cause or

motivation for change in your context

5!

Our plan today …




6!

Context Visualize context for prospective areas to

affect change

Our plan today …




7!


affect change

Solutions Identify potential

solutions for change to try out in your

context

A few disclaimers


Not a prescription 1

A few disclaimers


Not representing process or

methods in general at IBM

Not a prescription 2 1

A few disclaimers


Not a replay of existing sources

Not representing process or

methods in general at IBM

Not a prescription 2 1 3


Topics

11!

Topic #1




12!

Pattern of practice (for change)


PRACTICE SHARE EXPERIMENT

13!



Do it. Don’t sell it. – Jeff Patton

Begin anywhere.– John Cage


14!





Share the value.

Promote practices.

Think ‘us’. – John Wiegand


15!





Share the value.

Promote practices.

Think ‘us’.– John Wiegand

Adapt to context.

Hone your skills.

Fake it ‘til youbecome it.– Ann Cuddy


16!





Share the value.

Promote practices.

Think ‘us’.– John Wiegand

Adapt to context.

Hone your skills.

Fake it ‘til youbecome it.– Ann Cuddy


RECOGNIZE!

17!


Motivation & ‘inventing on principle’

Source: Bret Victor, Inventing on Principle: Living for a Cause, CUSEC 2012 (http://vimeo.com/36579366)

“Creators need an immediate connection … This principle is so important to me that when I see a violation of it, I consider it a moral wrong. And I don’t think ‘opportunity’, but rather ‘responsibility’.”

18!

Larry Tesler – “No Modes”


Image source: http://www.designinginteractions.com/interviews/LarryTesler

“… what drove him was the belief that ‘no person should be trapped in a mode’ … and made it his life’s work to fight against.”

19!

Motivation in context

•  Bret’s Principle: “Creators need an immediate connection”

•  Larry’s Principle: “No person should be trapped in a mode”

•  Your Principle: “…”


Motivations – A designer’s perspective


Eng-driven solutions

Wasted time on unused designs

Too problem-solving oriented

Different cadences

Distributed teams

Motivations – A developer’s perspective


Distributed teams

Impractical designs

Too feature oriented

Late-breaking changes Eng-driven solutions



Different cadences

Distributed teams

Hmmm, these seem familiar


Eng-driven solutions



Different cadences

Distributed teams Distributed teams

Impractical designs

Too feature oriented

Late-breaking changes


L

Motivation & ‘designing on principle’


Making software should be satisfying for everyone involved

and result in quality outcomes

Activity #1




26!

27!

•  The Breakup Letter –  Consider your organization or team to be a ‘person’

you’ve been dating

–  Write that person a breakup letter. What would you say if you were going to end this relationship?

•  Time: 5 minutes •  Materials: Pen and paper


Activity #1 – Part 1

•  Share your letter –  Volunteers?

•  Time: 5 minutes

28!



29!

•  Highlight each issue within your letter –  This will help later with Activity #2

•  Time: 2 minutes •  Materials: Pen and paper



Topic #2




30!


affect change

Process in context – Model


Process in context – Players+Activities


Process in context – Issues




Activity #2



affect change


•  Find a partner

•  Welcome to My World –  Take the issues you identified in the breakup letter and

sketch out the interactions around these issues (e.g., what, when, who) – include full context and non-friction points

–  Use the post-its and shapes (circles, boxes, arrows) to make a flow diagram with annotations

–  Add new information if you think of it

•  Time: 10 minutes •  Materials: Post-its, sharpies, large paper

36!IBM Rational . TorCHI - December 12, 2013 . Advancing UX in Your Organization, Kim Peter and Adam Archer ©2013!


•  Share and elaborate on your world –  Share your sketch with your partner –  Clarify and discuss areas of ease, challenge and

interactions with others –  Elaborate your drawings

•  Time: 10 minutes –  5 minutes to share / 5 minutes to discuss –  You can share in succession, or share then clarify

each person in turn


Topic #3




38!


affect change



context


Being a PROBLEM SOLVER is a good thing.


Being a PROBLEM SOLVER is a good thing. Right?

Reframing from the design perspective




ProblemSolving



ProblemSolving

Problem Understanding

ProblemFinding

Recognizing areas for change


Shifting emphasis

45!

WHAT HOW


Shifting emphasis


Planning content Planning activities

WHAT HOW

Shifting emphasis


Planning content

Problem solving Problem finding and understanding

Planning activities

WHAT HOW

Shifting emphasis


Planning content

Problem solving

Independent design Co-making

Problem finding and understanding

Planning activities

WHAT HOW

Shifting emphasis – Examples


Planning content

Problem solving



Planning activities

WHAT HOW

Planning activities

EXAMPLES 1.  Story mapping an holistic user-centric picture 2.  Shared team rhythm


1. Story mapping


Activity

Task

Sub-task

Time

Release 2

Release 1

Great sources for learning more: Jeff Patton and Winnipeg Agilist

1. Story mapping – Example


1. Story mapping – Our first experiment


A messy start

1. Story mapping – Remote (template)


2. Shared team rhythm




Planning content

Problem solving



Planning activities

WHAT HOW

Problem finding & understanding

EXAMPLE 1.  Using hypothesis-driven exploration


1. Hypothesis-driven exploration




Planning content

Problem solving



Planning activities

WHAT HOW

Co-making (and co-learning)

EXAMPLE 1.  Team book club 2.  Design studio method


1. Team Book Club


2 1 3

61!

2. Design studio method


Follows a pattern

Understand THE PROBLEM

Sketch A SOLUTION

Present THE IDEAS

Critique THE IDEAS

Great sources for learning more: Will Evans, Nathan Curtis and Todd Zaki Warfel


Benefits •  Collaborate to understand together



Benefits •  Collaborate to understand together •  Generate ideas from different perspectives



Benefits •  Collaborate to understand together •  Generate ideas from different perspectives •  Solidify ideas via sharable artifacts



Benefits •  Collaborate to understand together •  Generate ideas from different perspectives •  Solidify ideas via sharable artifacts •  Create shared ownership



Benefits •  Collaborate to understand together •  Generate ideas from different perspectives •  Solidify ideas via sharable artifacts •  Create shared ownership •  Allow for open and honest critique



Benefits •  Collaborate to understand together •  Generate ideas from different perspectives •  Solidify ideas via sharable artifacts •  Create shared ownership •  Allow for open and honest critique •  Force participants to defend concepts


2. Design studio method – Remote


+ Audio/teleconference Screen sharing software Social software Sketching tools

2. Design studio method – Remote


Activity #3 – Homework J




71!


affect change



context

•  Brainstorm solutions from a distance –  You now have some perspective on your partner’s

challenges and context –  As someone at a distance, reflect on possible

solutions to your partner’s challenges –  Use post-its to write down all the possibilities you can

think of –  Place post-its on your partner’s world maps/sketches

•  Time: 5 minutes •  Materials: Post-its, sharpies, your world

maps/sketches



•  Discuss solutions –  Take turns sharing your solution ideas with your partner

•  Time: –  10 minutes: 5 minutes each to share

(we will signal at 5 minutes)




Conclusion

74!

How are we doing?

75!

Is making software satisfying for everyone involved

and resulting in quality outcomes?


How are we doing?


J people

How are we doing?


J design people

How are we doing?


J design quality people

How are we doing?


J design quality people It’s a work in progress

A few last take aways …

1.  Change takes time – a lot of time


Timeline example


2009 2011 2012 2014 2010 2013

Partner w/ tech leads to influence dev plans

Lead cross-functional feature teams

Plan w/ PM + tech leads

Lead design studios

Engage dev peers in synthesis activities

Book club

Change project teams

Increased emphasis on design

Review + periodically collaborate w/ individual devs

81!



2.  Relationships matter – both bottom-up and top-down




2.  Relationships matter – both bottom-up and top-down

3.  Small changes keep you motivated To keep your momentum and motivation up, get in the habit of accomplishing small victories along the way.– Rework by Jason Fried and David Heinemeier Hansson



Thank You!

84!

Kimberley Peter [email protected] @kpeter

Adam Archer [email protected] @agarcher

Sources for methods (adapted) Activity 1 : The Breakup Letter •  Hanington, B., Martin, B.,

Universal Methods of Design: 100 Ways to Research Complex Problems, Develop Innovative Ideas, and Design Effective Solutions, Rockport Publishers (2012)

Activity 2 : Welcome to My World •  Gray, D., Brown, S., Macanufo, J., Gamestorming: A Playbook for Innovators, Rulebreakers, and Changemakers, O’Reilly Media, 1st Edition (2010) Activity 3 : Getting Distance (not used in this version of the workshop) •  Heath, C., Heath, D., Decisive: How to Make Better Decisions in Life and Work, Random House Canada (2013)


Sources for further learning (1 of 3) Agile / Lean UX Methods •  Gothelf, J., Seiden, J. (editor), Lean UX: Applying Lean Principles to Improve User Experience, O'Reilly Media (2013)

•  Ramsey, A., Designing with Agile Workshop: Fast, Effective Methods that Work (Anders Ramsey – Blog, 2011)http://www.andersramsay.com/2011/10/06/designing-with-agile-workshop/

Design Principles •  Hess, W., Design Principles: The Philosophy of UX (Slideshare, 2011)

http://www.slideshare.net/whitneyhess/design-principles-the-philosophy-of-ux Design Studio Method •  Curtis, N., Sketching for Understanding (UIE Webinar, 2013)

http://www.uie.com/events/virtual_seminars/sketching_understanding/ •  Zaki Warfel, T., The Design Studio Method (Agile UX NYC 2012 – Vimeo, 2012)

http://vimeo.com/37861987

•  Evan, W., (no longer available at UXMag – try Semantic Foundry (http://www.semanticfoundry.com) for possible updates): –  Evans, W., Introduction to Design Studio Methodology (UX Magazine – Article, 2011)

http://uxmag.com/articles/introduction-to-design-studio-methodology

–  Evans, W., The Design of Design Studio (UX Magazine – Article, 2011)http://uxmag.com/articles/the-design-of-design-studio

–  Evans, W., Design Studio and Agile UX: Process and Pitfalls (UX Magazine – Article, 2011)http://uxmag.com/articles/design-studio-and-agile-ux-process-and-pitfalls

Feature Teams •  Larman, C., Vodde, B., Feature Team Primer (PDF, 2010)

http://featureteamprimer.org/feature_team_primer12.pdf


Sources for further learning (2 of 3) General Theory, Practice, and Inspiration •  Brown, T., Change By Design: How Design Thinking Transforms Organizations and Inspires Innovation, Harper Business, 1st Edition

(2009)

•  Buxton, B., Sketching User Experiences: Getting the Design Right and the Right Design, Morgan Kaufmann, 1st Edition (2007)

•  Cuddy, A., Your body language shapes who you are, TED Talk (2012)http://www.ted.com/talks/amy_cuddy_your_body_language_shapes_who_you_are.html

•  Fried, J., Heinemeier Hansson, D., Rework, Crown Business (2010)

•  Merholz, P., Wilkens, T., Schauer, B., Verba, D., Subject To Change: Creating Great Products & Services for an Uncertain World: Adaptive Path on Design, O'Reilly Media (2008)

•  Victor, B., Inventing on Principle: Living for a Cause (Canadian University Software Engineering Conference, CUSEC 2012 – Vimeo, 2012) http://vimeo.com/36579366

•  Wellings, P., Gray, C., Turning a Developer-driven Organization into a UX Company (UX Week – Vimeo, 2010)http://vimeo.com/15136913

Remote Collaboration Methods •  Curtis, N., Efficient Sketching Studios With Remote Participants (EightShapes – Blog, 2011)

http://www.eightshapes.com/blog/2011/10/13/efficient-sketching-studios-with-remote-participants/

•  Gothelf, J., Designing with remote teams (Jeff Gothelf – Blog, 2013)http://www.jeffgothelf.com/blog/designing-with-remote-teams/


Sources for further learning (3 of 3) Strategy and Planning Methods •  Milan, M., Ladner, S., Backcasting: How I learned to stop predicting and help my clients (IA Summit – Slideshare with audio, 2007)

http://www.slideshare.net/mmilan/backcasting-ia-summit-2007-session-presentation

•  Milan, M., Backcasting 101: Collaborative Strategy Development for Information Architects (IA Summit – Slideshare, 2008)http://www.slideshare.net/mmilan/backcasting-101-final-public

•  Patton, J., The new user story baclog is a map (Agile Product Design – Blog, 2008)http://www.agileproductdesign.com/blog/the_new_backlog.html

•  Patton, J., Story mapping for UX Practitioners: Tying Agile and UX together (UIE Podcast, 2011)http://www.uie.com/brainsparks/2011/10/07/jeff-patton-story-mapping-for-ux-practitioners-tying-agile-and-ux-together/

Synthesis Theory and Methods •  Kolko, J., Exposing the Magic of Design: A Practitioners Guide to the Methods and Theories of Synthesis, Oxford University Press

(2011)


Advancing UX in Your Organization (TorCHI Talk - December 12, 2013)

Design

Transcript of Advancing UX in Your Organization (TorCHI Talk - December 12, 2013)