Upgrade to Pro — share decks privately, control downloads, hide ads and more …

People Over Process: Turning Assumptions into shared understanding

Michael Jovel
November 20, 2014

People Over Process: Turning Assumptions into shared understanding

Every project is based on a number of assumptions. Assumptions about our users and assumptions that our team has a shared vision of what we are building and why we are building it. The longer we hold onto these assumptions, the greater we increase the risk of not meeting our users needs and ultimately, our project fails.

This talk will be about how we ensure we are meeting our users needs. In addition to learning project workflow, we will cover specific techniques that you can use to ensure that the user is at the center of our design and that you create a shared understanding among your team.

Michael Jovel

November 20, 2014
Tweet

More Decks by Michael Jovel

Other Decks in Design

Transcript

  1. MICHAEL JOVEL - @MJOVEL JAVIER RIOS - @JAVIERIOS PEOPLE OVER

    PROCESSES: TURNING ASSUMPTIONS INTO SHARED UNDERSTANDING
  2. The version of a product that brings the maximum amount

    of validated learning about customers with the least effort. MVP
  3. “People don’t want to buy a quarter-inch drill. They want

    a quarter-inch hole.” - Theodore Levitt
  4. Redesign Report A Problem Page Instead of: Outcome Reduce the

    amount of time it takes for a user to report an adverse event with medical products
  5. A Tentative Assumption Made In Order To Draw Out And

    Test Its Logical Or Empirical Consequences merriam-webster
  6. Why Hypothesis • Rather than make assertions it puts forth

    a question which must be validated • Engages Team Creativity
  7. Risk • What assumptions do you have that if proven

    false will cause your solution to fail?
  8. Design Idea Inventory • high number of unvalidated design ideas

    leads to large deliverables • leads to lag in production as team awaits deliverables • maximizes the risk as there more time between creation and validation
  9. Pattern Library • Library of UI Patterns that developers can

    use (i.e. buttons, fields, etc. • Library of UI Components composed of multiple patterns (i.e. forms, video player, etc.)
  10. Supplies • Butcher paper, painters tape, sharpies and stop watch,

    grid template sheets • Build small 3-4 person teams composed of designer, developers and business team. • Give each team a persona to focus on
  11. Critique • Each member lists 1 or 2 ways in

    which sketch achieves goal • Each member Lists 1 or 2 ways in which sketch fails to achieve goal
  12. Unicorn? Mythical user experience designer with an advanced and adaptive

    skill range. Outstanding skills in graphic design, rapid prototyping, front end development, user testing, technical specifications, marketing and branding. It does not have an opinion, it has a process, and will harmonize with any environment.
 http://uxunicorn.com/
  13. The days of designers simply pushing pixels are long gone.

    Leading design means building a design culture, designing for the future, and adapting constantly.
  14. Designers need to help build a company culture that values

    design by not only producing a well designed product but by helping other team members understand and respect design.
  15. –Stewart Scott-Curran, Creative Mornings “The designers that actively seek out

    opportunities to contribute and influence other areas of the company become the leaders regardless of title. They are the people that others look to when problems arise or if an expert opinion is required”
  16. Designers need to get better at articulating their ideas through

    direct business communication. We need to show that our thinking is grounded in logic and produces results.
  17. Learn to quickly absorb and synthesize feedback should push us

    to take action. We need to learn to fail fast and make adjustments
  18. Benefits Of Pair Design • Make sure designers and developers

    spend time working together • saves time on implementation • promotes ownership
  19. Validation • send multi-disciplined team to meet with customer •

    take a copy of the MVP to visit customers • have one members lead the interview while the others observe and record
  20. Great products require investment across many different parts of a

    business, so we put a bigger effort on collaborating with our customers.
  21. It doesn't change the organizational dynamics or shift the way

    people think about building great products.
  22. Invest clients into the work and focus on smaller deliverables

    to create momentum. Dedicate a small group across the entire product development cycle, thus providing value beyond just wireframe flows.
  23. “It’s easier to ask forgiveness than it is to get

    permission” - U.S. Navy Rear Admiral Grace Hopper