Don't Ride the Roller Coaster: create lasting design awarements in your organization

@jayeffvee @chris.na_xd #madpow #DRTRC #UPABos12 @jayeffvee @chris.na_xd #madpow #DRRC #UPABoston @jayeffvee @chris.na_xd #madpow #DRTRC #UPABos12

Don’t Ride the

Roller Coaster . . .

Create lasting design awareness

in your organization

hCp://www.flickr.com/photos/jclement/2647899239/

@jayeffvee @chris.na_xd #madpow #DRTRC #UPABos12

E. Chris.na Persson Joan VermeCe @chris.na_xd @jayeffvee

Creating Design Awareness in Your Organization

•  Mad skills, methods, talent

•  Process & culture

•  Rela.onships

Our Conversation about Process

•  Do you need process?

•  Is there an inherent, natural process?

•  What’s at the core?

Process & Culture

Draw Make Think

Illustrator, Brandon Baselice Thanks to Brian Ling, thinkdrawmake.com, Design Sojourn

It’s about balance

hCp://www.flickr.com/photos/statelibraryofnsw/3073045010/sizes/z/in/photostream/ @jayeffvee @chris.na_xd #madpow #DRTRC #UPABos12

•  hCp://www.flickr.com/photos/statelibraryofnsw/3073045010/sizes/z/in/photostream/

One size

fit all

•  h<p://www.flickr.com/photos/sebilden/3518661163

But there’s something more . . .

What are the values that successful, innova.ve companies hold?

Verme<e photo library

Relationship Companies

•  Integra.on

•  Communica.on

•  Flexibility

. . . regardless of what formal process they use

Process plus the Glue

•  Organiza.ons need process & structure

•  But these are not sufficient towards innova.on and market success.

But also . . .

•  Transparency

h<p://www.flickr.com/photos/kennedylibrary/3620931196/

But also . . .

•  Respect

h<p://www.flickr.com/photos/84423669@N00/4396558735/

The Relationship Principles

•  Integra.on

•  Communica.on

•  Flexibility

•  Transparency

•  Respect

The 5 Principles

Principle 1: Integration

Integration

Break down the walls.

Integration

Organiza.onal silos are old thought made concrete.

Integration

Your less obvious colleagues are a wealth of informa.on.

Integration – the outcome

•  BeCer product •  Less rework •  Buy-‐in from the ground up •  Early, abundant crea.vity

–  Never know where the awesome will come from –  Divergent thinking

Principle 2: Communication

Communication

Communica.on is important. •  OH: “I don’t care what my internal partners think; I care what people think.”

Communication

Always working on it •  What does “done” mean?

Communication

Ask the stupid ques.ons

Paraphrase and confirm

Check in with folks

Validate ‘common’ terms

Use their vernacular

Communication – the outcome

•  Less rework •  Cohesion leads to efficiency •  Involvement •  Knowing what’s around the corner – comfort •  Trust from the top-‐down •  Repeat business •  You’re easier to work with

–  so R&D gets pulled into projects earlier, geqng the ‘what work’ not just the ‘how work’.

Principle 3: Flexibility

Flexibility

Adapt your techniques

Flexibility

Adapt your process

Meeting 10:00-11:00pm Virtual signoff by 5:00pm Meeting 3:00-3:30

Meeting 10:00-11:00am Meeting 3:00-3:30 Meeting at 9:00-11:30am Touch Points

1.  Sign off meeting Attendees: representatives from FIL business and systems teams; the design team; FeBDesign business line owner and product line owner. Goal: to completely sign off and deliver 2. Incorporate feedback from Sign off meeting before close of business; obtain virtual signoff.

1.   2nd check-in meeting Attendees: IA, VisD, Proto Agenda: go through page inventory to understand status Goal: to make sure a full, publishable draft of each page has been created and is ready for hand off and sign off on Friday morning. To understand any remaining unresolved issues and decide an action plan to address them. 2.   Design work

1.   Internal review Attendees: Usability, reviewing designer, style guide reviewer, IA, VisD, Proto, Analyst Agenda: Explain context of pages and scope of changes; take teamthrough the page flow. Goal: to surface any usability issues that can be addressed without functional changes. 2. Incorporate Usability feedback

1.   1st check-in meeting Attendees: IA, VisD, Proto Agenda: go through page inventory to understand status Goal: to understand status so any issues can be appropriately resolved/escalated. Note that this is not a design meeting; design discussions -- unless there are issues -- should be occurring during the rest of the day as needed. 2. Design work continues.

1. Collaborative analysis meeting Attendees: IA, VisD, Proto, Analyst Agenda: Context brief (analyst) View pages, assess components by page to identify which need further IA and visual work. Goal: go directly to code as much as possible. 2. Work on first draft begins.

Activities

Present for approval Incorporate changes First draft ready for Internal review

Working, with IA/Analyst answering questions

Create a shared understanding of Context Determine how much of the work can go to code immediately.

Goal for the day

Friday Thursday Wednesday Tuesday Monday

Flexibility

Adapt your design

Flexibility – the outcome

Focus on making it beCer, not perfect •  Easier to work with •  More .me & opportunity for interes.ng work. •  Researchers and designers are seen as less preten.ous and

prickly.

Principle 4: Transparency

Transparency

Share your process, share your ra.onale •  Result: Users squealing with joy in tes.ng

Transparency

The more you share, the more you show your value.

Transparency – the outcome

Enhances your value to the organiza.on. •  The team realizes this is challenging. •  Team members begin to trust you. •  Repeat business, more resources, more .me

== BeCer design •  You get beCer ideas •  Garner support for further research efforts •  Garner support for schedule changes

Principle 5: Respect

Respect

Without respect, you can’t apply the other principles Value is not always obvious Expect they’re there, and the value and ideas will come

Respect

Start with the Premise: •  Partners are naturally crea.ve, resourceful & whole Just as we do with our users: •  The user is always right, so are your partners

Respect – the outcome

•  You’ll realize their value –  and step out of your own perspec.ve

•  You don’t waste mental energy.

•  Respect is reciprocal

•  Leadership –  you posi.vely energize and influence the team

Toolkit

Toolkit – Integration

•  Regardless of process, do it. •  Understand the silos, pull them in. •  As a consultant, integrate with the client:

–  Help them feel rescued and validated.

•  Don’t just invite them, insist on par.cipa.on & contribu.on.

•  Visit them at their desks, call them. •  With developers, “Can I see it?”

Toolkit – Communication

•  Listen, really listen

•  Asking stupid ques.ons

•  Paraphrase & confirm

•  Validate ‘common’ terms

•  Use their vernacular

Toolkit – Flexibility

•  Use tried and tested techniques, but if there are impediments . . . –  understand the constraints –  where the freedom might lie –  define the goals

•  Take ini.a.ve

Toolkit – Transparency

•  Design Studio

•  Invite par.cipa.on in research and usability tes.ng –  ask them for their conclusions –  include their awarenesses in your report –  ask them what ques.ons arise for them

•  Create and post collateral –  Posters on walls –  Post deliverables on a shared resource –  Post schedule & milestones

Toolkit – Respect

•  Self-‐awareness

•  “They add value,” and turn the energy into curiosity.

•  Modify your mindset: –  They are resourceful, crea.ve, and whole

•  When you ques.on the ideas or feedback –  Ask, “Why?” –  Build on the ideas of others: "Yes, and…”

Exercise

•  You: Share your experiences [Successes and Tough situa.ons]

•  Colleague: shows how a principle could be brought to bear.

•  Get free stuff

•  Integration

•  Communication

•  Flexibility

•  Transparency

•  Respect

Creating Design Awareness in Your Organization

•  Mad skills, methods, talent

•  Process & culture

•  Rela.onships

The Relationship Principles

•  Integra.on

•  Communica.on

•  Flexibility

•  Transparency

•  Respect

E. Chris.na Persson chris.na@madpow.com @chris.na_xd

Joan VermeCe jvermeCe@madpow.com @jayeffvee

Connect with us . . .

Don't Ride the Roller Coaster: create lasting design awarements in your organization

Design

Ashley Roller Coaster Fun

Roller Coaster

Roller Coaster Physics - K'Nexmedia.knex.com/.../78880-TG-Roller-Coaster-Physics.pdf · 2016-12-28 · Roller Coaster Physics Teacher’s Guide KNX96007 -V2 ©2008K'NEXLimitedPartnershipGroup

Donaho Roller Coaster Fun

Roller Coaster Rascal

Robinson Roller Coaster Fun

Roller Coaster Physics

Roller Coaster Project

Roller Coaster Installation

Roller coaster opinions

Beason roller coaster fun

Roller Coaster Sales Performance

Roller Coaster Project - UW Computer Sciences User Pagespages.cs.wisc.edu/~kma/downloads/roller-coaster.pdf · Roller Coaster Project Ke Ma Introduction The roller coaster project

Wise Roller Coaster Fun

Roller Coaster Deconstruction

Huey Roller Coaster Fun

Roller Coaster Design

ROLLER COASTER C

Roller coaster images2

Don't Ride the Roller Coaster: Creating lasting design awareness in your organization