Design for Product Managers

65
Dealing with Design A survival guide in three acts

description

a tragic tale in three parts

Transcript of Design for Product Managers

Page 1: Design for Product Managers

Dealing with DesignA survival guide in three acts

Page 2: Design for Product Managers
Page 3: Design for Product Managers

When do you need a designer?

Page 4: Design for Product Managers
Page 5: Design for Product Managers

What are the flavors of designers?

Page 6: Design for Product Managers
Page 7: Design for Product Managers
Page 8: Design for Product Managers
Page 9: Design for Product Managers
Page 10: Design for Product Managers

Hiring & Vetting• What are my product’s goals and challenges?• What must users do/experience for us to win?• What competency must the designer have?• Where do I find them?

Page 11: Design for Product Managers

The Interview1. Portfolio

• Watch out for “we”2. Design exercise

• Same exercise for everyone• Short, and reveals thinking• Not about making a good design

3. Interview• How did you solve a similar problem?• What would you change about our product (if

existing) or competitor• What’s your ideal job?

Page 12: Design for Product Managers

Working effectively with designers

• Bring them in EARLY• Set clear priorities• Get the flows (or IA) first• Critique with goals, not solutions• Push respectfully forward

Page 13: Design for Product Managers
Page 14: Design for Product Managers

Ten reasons to kill your designer

1. "I did the best I could - there's only so much you do with..." 2. "Just tell me what you want and I'll make that." 3. “Oh, that can't be done.”4. “Oh, but my idea is much better” 5. "Well you never told me it was supposed to be REALLY good!" 6. "Your database doesn't work with my design" or “Is all of this stuff

really necessary?”7. "That solution would be non-standard" or “Users don’t scroll.” 8. "I went to design school" 9. "Because it looked better.“10. “Trust me"

http://www.linkedin.com/answers/product-management/product-design/interface-design/PRM_PDS_INF/173714-1751812

Page 15: Design for Product Managers

When it’s you

Page 16: Design for Product Managers

Layers of design• Base: User need/business need/tech

options• Information Architecture and/ or Interaction

Design• Interface Design• Graphic Design

Page 17: Design for Product Managers

Four Design Hacks

Page 18: Design for Product Managers

Participatory Card Sort

Page 19: Design for Product Managers

Running a successful card sort

• 50-75 pieces of content (not categories!)

• Provide as much information as possible while not overwhelming

• Lay all content out on a large table, shuffled thoroughly

• Provide blanks for category labels

• Encourage thinking-out-loud

• Be helpful, but do not suggest or advise. Play psychiatrist.

• Collate results and look for patterns.

Page 20: Design for Product Managers

Scenarios and Task Analysis

Page 21: Design for Product Managers

Example Persona Scenario

Page 22: Design for Product Managers

Task analysis

• Step by step breakdown of scenarios

• Helps define interface/interaction needs

• Flushes out potential opportunities for errors

Page 23: Design for Product Managers

Task analysis

“CHECK OUT” BECOMES

a. Select checkoutb. Sign in/sign upc. Input shipping addressd. Input billing address

e. Input paymentf. Review orderg. Finalize checkout

Purchasing a purse at nordstroms.com might include the tasks:

1. locate purse 2. add purse to shopping cart3. check out

Page 24: Design for Product Managers

Task analysis

“CHECK OUT” BECOMES “INPUT BILLING ADDRESS” BECOMES

a. Select checkout d. Input billing address (prepopulate all fields from c.)

b. Sign in/sign up i. Input first name

c. Input shipping address ii. Input family name

d. Input billing address iii. Input street address

e. Input payment iv. Input street address

f. Review order v. Input state (dropdown of standard abbreviations)

g. Finalize checkout vi. Input country

And so on…

Page 25: Design for Product Managers

Page Zoning

Page 26: Design for Product Managers

• Table setting?

Page 27: Design for Product Managers
Page 28: Design for Product Managers

Title

Content

Viral featuresmetadata

Related content

Page 29: Design for Product Managers

Graphic design hacks

Page 30: Design for Product Managers

Minimalist Design• Only use one font. Preferably helvetica. • Only use three, maybe four sizes, all very very

different. • Only use one color, with variations, and one

“accent” color.• Turn on the grid (if you are using photoshop, etc)• Never align center.• Never use stock photography.• Have a hierachy

Page 31: Design for Product Managers

I am a serifed font

I am sans-serif

Page 32: Design for Product Managers

I am Times New RomanHey, I’m arial

Page 33: Design for Product Managers
Page 34: Design for Product Managers
Page 35: Design for Product Managers
Page 36: Design for Product Managers
Page 37: Design for Product Managers

niiiiiiice

Page 38: Design for Product Managers
Page 39: Design for Product Managers
Page 40: Design for Product Managers

Cheat• Patterns• Libraries• Odesk• Conference proceedings

You can’t buy taste

Page 41: Design for Product Managers
Page 42: Design for Product Managers

ResearchBeyond usability

Page 43: Design for Product Managers

Who does it?

• Internal User Research Specialist

• Outside Consultant

• You

Page 44: Design for Product Managers

Why do it?

• Know if the product meets user needs before you build it

• Cheap to change a sketch

• Affordable to change a Photoshop comp

• Expensive to change fully coded product

• Customer service expensive as well

Page 45: Design for Product Managers

Why do it?

• Enable you to develop easy-to-use products• Satisfy customers

• Decrease expenditures on technical support and training

• Advertise ease-of-use successes

• Improve brand perception

• Ultimately increase market share

Page 46: Design for Product Managers

Who are the users of the system?

• Start by collecting pre-existing information

• Hunt down previous data (marketing demographics, surveys, past usability tests)

• Hold stakeholder interviews

• Conduct customer service interviews

Page 47: Design for Product Managers

Finding the end user

• Recruiting • Develop a portrait of the user (a la the persona)• Develop a screener based on this• Recruit typical end users

• Professional recruiter• Do it yourself

• Offer a consideration: cash or a gift• Watch for ringers

• Professional testers• Inarticulate users

Page 48: Design for Product Managers

Not the end user

• Employees• Designers• Programmers• Market researchers• You

Page 49: Design for Product Managers

Three Research Hacks

Page 50: Design for Product Managers

Site visit

Page 51: Design for Product Managers

Site visit

Page 52: Design for Product Managers
Page 53: Design for Product Managers
Page 54: Design for Product Managers

Rules• Ask them to use your product, and “think

aloud” while doing so• Take photos (with permission)• Record quotes• Note interruptions, accessory items, and

social itneractions

Page 55: Design for Product Managers

Friends and Family Usability

Page 56: Design for Product Managers
Page 57: Design for Product Managers

OK, if• They are just like your target users• Unfamiliar (or typical familiarity) with

product• NO CHEATING!

Page 58: Design for Product Managers

Form of… usability test!• Set of tasks• Think aloud• Time tasks, if relevant• One more time– no hints, no leading

questions

Page 59: Design for Product Managers

Paper Prototyping

Page 60: Design for Product Managers

Tools

Page 61: Design for Product Managers

Research Don’ts• Ask leading questions• Show people where things are• Let them get frustrated• Make them feel stupid• Take your own notes• Do focus groups

Page 62: Design for Product Managers

Research dos• Do it.

• Any way

• Do it

Page 63: Design for Product Managers
Page 64: Design for Product Managers
Page 65: Design for Product Managers

Organizations• Iainstitute.org• Ixda.org• Aiga.org

These all hold excellent conferences. Ixda.org will be posting videos of last weekend’s conference shortly (including my talk on viral design).