Product Design Organization

221a911c59d66a716ec8fcb79bdb4692?s=47 clearwired
August 22, 2013
1.5k

Product Design Organization

221a911c59d66a716ec8fcb79bdb4692?s=128

clearwired

August 22, 2013
Tweet

Transcript

  1. Jive Product Design  Chris Rivard, Product Designer

  2. Paul Rand (1914-1996)

  3. None
  4. Users our “consumer” sovereign product usage design Customers decision maker

    transient product usage product management
  5. Jive Design should focus on ethnographic research in combination with

    analysis of behavioral data as drivers for all design decisions.
  6. Risk

  7. • Repeatable, testable results • A common language (patterns, processes)

    • Certainty of “the thing” What’s missing?
  8. Break the cycle.

  9. The Business provide value to our shareholders sales leverage margin

    leverage innovation? Our Customers faster horses? competitive advantage/parity? arms race? Our Users empowered smart & competent (we’re not really sure...)
  10. The Business provide value to our shareholders sales leverage margin

    leverage innovation? Our Customers faster horses? competitive advantage/parity? arms race? Our Users empowered smart & competent (we’re not really sure...)
  11. Design Culture.

  12. Product Design Narratives A: We’re amazing project managers interpreting customer

    requirements from product management and through that interpretation (the design process) we deliver a compelling (and integrated) user experience. B: We’re amazing designers who know what is best for our users through the sheer gestalt of our design experience (without having to actually ask them).
  13. Some (painful) examples: • apps strategy • usability initial findings

    from Marquette • there are many others
  14. Why change? 1.Users do not know what they want. 2.We’re

    moving too fast. 3.We’re designing for Gen-Y.
  15. Some ideas: 1.PD / UI collapsed into one design team

    2.PD / UI designers paired and working as a cohesive team 3.Up-level design management 4.Speed up design loops (we should be designing for 7.0 now 5.Send designers out on the road (with a structure for presenting findings back to the team). 6.Findings should drive some requirements
  16. Thanks for your time.