O slideshow foi denunciado.
Seu SlideShare está sendo baixado. ×

PCC2 - How do I incorporate Apple-like design into my products?

Carregando em…3

Confira estes a seguir

1 de 51 Anúncio

Mais Conteúdo rRelacionado

Diapositivos para si (20)


Semelhante a PCC2 - How do I incorporate Apple-like design into my products? (20)

Mais recentes (20)


PCC2 - How do I incorporate Apple-like design into my products?

  1. 1. How do I incorporate Apple like design into my products? Michael Walkden VP Product Delivery Pathfinder Development LLC www.pathf.com April 2, 2011 Product Camp Chicago (c) Copyright 2011 Pathfinder Development LLC. www.pathf.com DEVELOPMENT
  2. 2. Background
  3. 3. Design Matters ...Now more than ever
  4. 4. 1950s
  5. 5. Photo Credit: CC Ezu 1990s
  6. 6. As computing technology moves toward mobile devices, we’ve seen the 1990s’ growth in processor speed taper off and product development become less about horsepower [and more] about the overall design of the product. ... a healthier view of human intelligence ... ... that it is reactive, responsive, sensitive, nimble. Brian Christian, The Atlantic March 2011
  7. 7. 2011
  8. 8. What does Steve Really do For Apple? <ul><li>Chief Design Advocate </li></ul>http://andrewchenblog.com/2009/12/04/does-every-startup-need-a-steve-jobs/
  9. 9. Agile 101
  10. 10. Photo By: Pattista Agile 101
  11. 11. <ul><li>In general agile is not new. It is collection of good software practices evolved over years of experience. </li></ul>Photo By: NettasNursery
  12. 12. Myths About Agile <ul><li>Agile is Working Without Documentation </li></ul><ul><ul><li>Documents that add value are created just-in-time </li></ul></ul><ul><ul><li>Much of the documentation is short-lived </li></ul></ul><ul><li>One specific methodology </li></ul><ul><ul><li>It’s an umbrella term for a set of approaches and practices to software development which share common values. </li></ul></ul><ul><li>A “One Size Fits All” cookbook </li></ul><ul><ul><li>Every project and team adjusts to fit circumstances, environment, and constraints </li></ul></ul><ul><ul><li>It’s not an all or nothing proposition </li></ul></ul><ul><li>Simply iterations </li></ul><ul><ul><li>Software is developed incrementally, in time-boxed iterations </li></ul></ul><ul><li>“ Glorified hacking” </li></ul><ul><ul><li>There is a set of highly disciplined practices, including design which many people skip </li></ul></ul><ul><li>Working without a plan </li></ul><ul><ul><li>Adaptive planning aids in delivery of highest value features to the business </li></ul></ul><ul><ul><li>Planning occurs continually, throughout the project </li></ul></ul>
  13. 13. Agile Values - Ingredients for highly productive, happy teams <ul><li>Focus on activities that add value </li></ul><ul><li>Collaborative </li></ul><ul><li>Transparent </li></ul><ul><li>Adaptable </li></ul><ul><li>Simple </li></ul><ul><li>User engagement </li></ul><ul><li>Continuous Improvement </li></ul>
  14. 14. Lean User Experience Design
  15. 15. Product Concept Working Software
  16. 16. Lean UXD Methods are ... <ul><li>Lightweight </li></ul><ul><li>Low-Fi </li></ul><ul><li>Lo-Tech </li></ul><ul><li>External </li></ul><ul><li>Face to Face - Get out of the building </li></ul>
  17. 17. Lean UXD Methods are ... <ul><li>Collaborative </li></ul><ul><li>Fast </li></ul><ul><li>Repeatable </li></ul><ul><li>Goal Driven </li></ul><ul><li>Outcome Focused </li></ul>
  18. 18. Your Toolbox
  19. 19. Photo By: Hugo90 Working Prototypes
  20. 20. Pair Designing
  21. 22. send annotations load in plans in pdf format annotate plans with text aggregate annotations arrange plans into projects annotate with photos manage site visits within a project support jpeg as well as pdf plans search for a plan by title search for a plan using meta data access past projects upload files via email upload files via iTunes upload files via a virtual plan room m m m m m m add color to annotations separate documents into pages display PDF table of contents M M M X X 3 weeks 6 weeks 15 weeks
  22. 23. Architect in office, preparing for site visit captured site observations and emailed them load pdf plans on iPad for the site go to site launch iPad app find the plan for this particular inspection inspect site create annotations Finish inspection Connect iPad to network Generate annotations summary and send via email find site plans for site review annotations
  23. 25. The _____________ helps _____________ to _________________________ (product, feature) (target audience) (receive a benefit) Problem__________________________________________________________________________________________________________________________________________ The Story Solution__________________________________________________________________________________________________________________________________________ Desired Action __________________________________ Picture Caption ________________________________________________ Construction Obs. App architects/contractors carry whole plan libary to site and record and email observations without extra paperwork Architects often bring the wrong drawings to a site inspection and must reenter and can lose notes taken on yellow pads at a site The iPad punch list puts all the plans at the architects fingertips, gets rid of re-entry and insures notes are not lost Architect watches video demo and is offered link to app store touch an object to annotate, DONE button takes you back
  24. 26. Business Objectives   What does success look like from a business perspective? Users  Who are the primary users of this product? User Objectives  Why do users want this product? What do they expect from it? Brand Characteristics  How do we want customers to perceive the brand? Value Propositions   What value does this product offer to the consumer? Key Differentiators   What does this product offer that no one else can? Measures of Success   How will we know we've been successful? Are there any key performance indicators?
  25. 27. Ken Mitchell Responsible for Gig events, responsible for Gig staff, wants to sell out events, likes the service, likes innovators, staff prints thermal tickets (Box Office Manager, The Gig)
  26. 28. The Challenge
  27. 29. All in a 1-4 Week Period
  28. 30. <ul><li>Storytelling and High level design </li></ul><ul><li>Visualize the personas - a cheap stock photo (www.fotolia.com) for each and their role. Can be more creative if that's of value (a consumer product may need more, a B-to-B product probably not). </li></ul><ul><li>Visualize, using the personas pictures, the main idea of what the app does. Tell the story with one or a few slides. Ask: Does everyone on the team agree? </li></ul><ul><li>For each persona, get every activity they are doing listed. This is important, otherwise can end up designing pieces that don't fit together. This list can jump start the story list. </li></ul><ul><li>For each persona, identify top goals (persona is successful if they can ________). This is usually very quick to do. The thinking work for 1-4 is best done in a time-boxed workshop with designer or PM leading and the whole team participating. Designer then mocks up a slide deck to present and validate. </li></ul><ul><li>After master story list is created, visualize the entire master story list. Sketch a deck of drawings that captures all the stories in visual form. The sketches are purely a fast design with everything in it, not a good design. You can only accomplish this with time boxed workshops (usually two or three 3 hour workshops). It always seems like a lot to do, yet when time boxed and everyone is pitching in it can be done. Somebody, like the PM, must serve as time-watcher and keep things moving so the goal is reached. </li></ul><ul><li>From 5, designer creates and mocks-up core design ideas. If stuck, pair with someone, could be anyone (doesn't have to be another designer). </li></ul><ul><li>Present the core design ideas in a story deck with context (personas pictures, screens, flows, whatever needed) and get client buy in. This will need to be iterated a few times most likely. This deck sets the stage for detailed design wireframes and specs during iterations. </li></ul><ul><li>We usually have about two weeks to do this. Steps 1 -5 and part of 6 would be done during inception. The rest of 6 and 7 are done during the first iteration, which requires the first iteration's stories be independent of the core design. </li></ul><ul><li>If we can't do that in two weeks, we should sell the client on a longer inception if possible. Or, we have to finesse the first two iterations to allow more time for the high level design work. </li></ul><ul><li>Inception Checklist </li></ul><ul><li>Have customer fill out startup toolkit before inception </li></ul><ul><li>Have internal kick off to define project strategy (product design v.s. We are implementers) </li></ul><ul><li>Make sure to start with a PM, a designer, and a senior developer </li></ul><ul><li>Pre-schedule workshops, transition meetings, stand-ups (if used) </li></ul><ul><li>Start visual design in inception - have template of visual design done </li></ul><ul><li>Educate client on our process </li></ul><ul><li>Ensure notes and assumptions about stories get into Pivotal </li></ul><ul><li>Personas </li></ul><ul><li>High level task flows </li></ul><ul><li>Cover FURPS+ for cross functional and nonfunctional requirements </li></ul><ul><li>Select technology and high level architecture </li></ul><ul><li>Estimate and prioritize story list </li></ul><ul><li>Create a tentative release/build plan </li></ul><ul><li>Identify iteration 0 tasks (and start if possible) </li></ul><ul><li>Set up wiki, pivotal, email groups </li></ul><ul><li>Create SOW addendum using inception estimates </li></ul><ul><li>More business strategy conversations </li></ul><ul><li>Show customer story board in key note of story list to tell the product's story </li></ul>
  29. 31. Photo By: nukit1 Wait?!?! Good design takes time
  30. 33. But...Big Designs up Front don’t work either <ul><li>Don’t provide any direct value to product </li></ul><ul><li>Take too long </li></ul><ul><li>Are not accurate anyway </li></ul><ul><li>Foster an anti-change mentality </li></ul>
  31. 34. More about Big Designs up Front <ul><li>Are difficult to estimate </li></ul><ul><li>Are hard to navigate </li></ul><ul><li>Everyone hates reading them </li></ul><ul><li>Have to be transformed into something developers can use </li></ul>
  32. 35. Inception A short period of hard collaborative work; to better understand project objectives, identify potential users, and define high level functional scope so that size of the project can be roughly estimated and an incremental release strategy can be identified
  33. 36. Normally What Happens....
  34. 38. What Should Happen...
  35. 42. Traditional analysis: Exhaustively evaluate each level before moving on Agile recognizes that: Clarity is an iterative process… The levels interact...
  36. 43. Traditional analysis: Exhaustively elaborate each level before moving on Agile process strives to: Do just enough to move down...you can always go back Get to market and realize return on investment
  37. 44. An Agile inception Is... <ul><li>Very visual - centered around tangible models </li></ul><ul><li>Collaborative and inclusive </li></ul><ul><li>Time-boxed and rapid </li></ul><ul><li>Iterative and feedback driven (embracing change) </li></ul><ul><li>Product & implementation cost focused </li></ul>
  38. 45. Photo By: Eleaf How Do I Put it Together?
  39. 46. <ul><li>In battles with the business and technology goals, </li></ul><ul><li>desirability will almost always win out </li></ul><ul><li>Makes it clear that product should be “insanely great” </li></ul><ul><li>Recruits a top design team and protects them from competing goals </li></ul><ul><li>Willing to spend money, adjust technology processes, all for the goal of highly desirable product </li></ul>Choose Design Advocate http://andrewchenblog.com/2009/12/04/does-every-startup-need-a-steve-jobs/
  40. 47. <ul><li>Users </li></ul><ul><li>Needs </li></ul><ul><li>Tasks </li></ul><ul><li>Features </li></ul><ul><li>User Stories </li></ul><ul><li>Story Board </li></ul>
  41. 48. Inception HypothesisTest ResultsPersonasUsability TestingUser StoriesClarityCohesiveFocus on getting started There is Only One Team - Just different roles Design + Development + Testing + Project Management + Product Management
  42. 49. Agile Delivery Velocity Iterations Continuos Deployment User Stories Testing Lean UXD Wireframes Comp Prototyping User Behavior Analytics Usability Testing Product Focus Customer Development Funnels Sign-ups Analytics Constant Innovation There is Only One Team - Just different roles Design + Development + Testing + Project Management + Product Management Rapid Cycles Focus on desirability of end product
  43. 50. Easy Photo By: striatic
  44. 51. Thank You. DEVELOPMENT

Notas do Editor

  • New Products - marketing - Design - Development - Launch - Customer Acquisition
  • Military
  • Individual Contributors - isolated with computers
  • not talking about something lofty, but a real shift in the way we look at things
  • Ubiquitous - tools - NOT computers anymore
  • Real problem - desireabilty
  • Must Build Something - Good Engineering
  • How are these people having fun who are supposed to be working?
  • Solution #2 - Templates aren’t going to work
  • At the most basic level this is what we are trying to do
  • Where, when, why
  • Where, when, why
  • Story Board/Key Design - Where, when, why
  • Where, when, why
  • Personas Where, when, why
  • Because after that you have to START
  • Lower levels validate or challenge higher level assumptions
  • Who is there? - product launch people, stakeholders
  • This is the first thing you need - Next you need to live up to promises