lean ux integration

Download Lean UX Integration

Post on 22-Jan-2018

272 views

Category:

Documents

2 download

Embed Size (px)

TRANSCRIPT

  1. 1. Lean UXTransforming How We Work
  2. 2. 22 Too busy to innovate? Too busy not to.
  3. 3. 33 History of complications following build kit hand off to developers Duplicative, unnecessary work leads to long hours and reduced morale Interferes with our ability to scale operations Projects routinely under scoped and over budget as a result Too busy to innovate? Too busy not to.
  4. 4. 44 Case Study 1 Standard Build Kit provided to developer Site build did not match specs in Build Kit Our team spent excessive hours reviewing staging server to identify discrepancies o Over 600 discrepancies found across 72 unique screens for desktop, tablet, and mobile Several additional calls with the client were necessary o Supposed platform limitations were never communicated to our team despite tremendous, up front coordination with developers to manage expectations o Outdated, front end development methodologies hindered ability to quickly and easily implement site wide modifications Adversely impacted overall quality of final product o Limited to zero resources available to correct the issues identified and was launched with known defects Too busy to innovate? Too busy not to.
  5. 5. 55 Case Study 2 Standard Build Kit provided to developer Site build did not match specs in Build Kit Our team spent excessive hours reviewing staging server to identify discrepancies Developer transcribed copy from PSDs rather than importing or copy and pasting from provided manuscript Additional hours spent on QA and editorial reviewing the content in staging environment for accuracy Adversely impacted timeline Too busy to innovate? Too busy not to.
  6. 6. 66 A lot of times, people dont know what they want until you show it to them. Steve Jobs From UX to Lean UX
  7. 7. 77 Inspired by Lean and Agile development theories, Lean UX is the practice of bringing the true nature of our work to light faster, with less emphasis on deliverables and greater focus on the actual experience being designed. Jeff Gothelf Lean UX: Getting Out of the Deliverables Business Smashing Magazine, March 7th, 2011 The greatest exponents of UX design are some of the biggest brands to emerge in the last 15 to 20 years. Google, Amazon, Facebook and Apple have all invested heavily in refining their user experience and reaped the rewards. Apple and Google are currently the two most valuable companies in the world, a fair justification for the current trend of enthusiasm for UX. Citation Needed From UX to Lean UX
  8. 8. 88 From UX to Lean UX Lean UX Drivers: Technology moves fast, so should we Thriving in a rapidly changing landscape requires the ability to adapt quickly Operational Efficiency Increased ability to provide new service offerings and greater value proposition for our clients Leadership by Example Unprecedented opportunity to excel in the industry through adoption of innovative techniques Lean UX is industry and content agnostic Known Adopters:
  9. 9. 99 From UX to Lean UX Lean UX Principles: Continuous Discovery Allows research, feedback, and analytics to remain relevant beyond a fixed point in time. Constant Iteration Frequent incorporation of research and feedback minimizes time spent in the wrong direction. Fact Based Decision Making Creates objectivity within the team and confidence in the product. Validating Early and Often Turning assumptions into actionable facts moves projects forward rapidly and concisely. Greater Collaboration Promotes shared understanding and consensus amongst all stake holders. Workflow Integration Reduces effort exerted on extraneous documentation. Build
  10. 10. 1010 From UX to Lean UX Lean UX Results: Estimates for build time and cost can be 50% more accurate Request for clarification by the development team can be reduced by 80% The amount of rework and bug fixes post-launch can be reduced to 25% of similar previous projects Prototyping can require 45% less effort than conventional development methodologies 5000 4000 3000 2000 1000 0 | 1000 | 200 | 300 | 400 | 500 | 600 | 700 | 800 | 900 | 100 S3 S3 S1 S4P2 P1 P S P3 PROTOTYPING PROJECTS DEVELOPMENT EFFORT, MANHOURS DeliveredSourceInstructions PROTOTYPING VS. SPECIFYING SIZE AND EFFORT COMPARISONS SPECIFYING PROJECTS
  11. 11. 1111 Wherever I see people doing something the way its always been done, the way its supposed to be done, following the same old trends, well, thats just a big red flag to me to go look somewhere else. Mark Cuban What Ive Learned Esquire, Nov 17, 2008 Transforming how we work
  12. 12. 1212 Transforming how we work Going from this:
  13. 13. 1313 Transforming how we work To this:
  14. 14. 1414 The Status Quo The Big Design Upfront model requires revisions for every deliverable at every stage of development. The constant reconciliation causes efforts to be expended on documentation management instead of the product itself. Standard Workflow Overview: 1) CW creates content outline 2) IA creates sitemap 3) Internal/External Review Cycles 4) Revisions applied to Content Outline 5) Revisions reconciled to Sitemap 6) CW creates Manuscript 7) Internal/External Review Cycles 8) Revisions applied to Manuscript 9) Revisions reconciled to Content Outline 10) Revisions reconciled to Sitemap 11) IA creates wireframes 12) Internal/External Review Cycles 13) Revisions applied to Wireframes 14) Revisions reconciled to Manuscript 15) Revisions reconciled to Content Outline 16) Revisions reconciled to Sitemap 17) AD creates PSDs 18) Internal/External Review Cycles 19) Revisions applied to PSDs 20) Revisions reconciled to Wireframes 21) Revisions reconciled to Manuscript 22) Revisions reconciled to Content Outline 23) Revisions reconciled to Sitemap Note: Production design focused diagram, does not include additional documentation such as brief, BRD, FRD, and Style Guide AD: DesignsIA: Sitemap CW: Manuscript IA: WireframesCW: Content Outline Reconcile Review Cycle Submission Revisions Review Cycle Submission Revisions Review Cycle Submission Revisions Review Cycle Submission Revisions Reconcile Reconcile Reconcile Transforming how we work Review Cycle Submission Revisions
  15. 15. 1515 AD: DesignsIA: CMS Backed Prototype The Opportunity A high fidelity prototype model focuses on outcomes over output. By linking the prototypes to a CMS, effort spent on reconciliation is replaced by automated integration. Potential Workflow Overview: 1) IA creates prototype in CMS 2) CW publishes content outline to CMS 3) Internal/External Review Cycles 4) Revisions applied to CMS 5) CW publishes Manuscript to CMS 6) Internal/External Review Cycles 7) Revisions applied to CMS 8) AD exports Style Sheet to CMS 9) Internal/External Review Cycles 10) Revisions applied to CMS Note: Production design focused diagram, does not include additional documentation such as brief, BRD, FRD, and Style Guide Review Cycle Transforming how we work Submission Revisions Integrate Integrate CW: Manuscript
  16. 16. 1616 Transforming how we work The Benefits A data driven system enforcing separation between content, layout, and behavioral elements would allow us to be more nimble and adaptive to the changing requirements of our clients CMS data exports can replace the majority of build kit documentation including Manuscript, Wireframes, PSDs, and Style Guides Direct integration can eliminate the risk of error when transposing content Original source documentation can be utilized to fulfill regulatory submission expectations and requirements Required capabilities exist within current production software Built in responsive browser behavior allows for concurrent design of multiple screen sizes Real time rendering allows for quicker review cycles and constant quality assurance
  17. 17. 1717 Knowing is not enough, we must apply. Willing is not enough, we must do. Bruce Lee Getting Lean
  18. 18. 1818 Adopt Train Test Deploy Adopt the right CMS for our future needs: Provide continual training to key departments: Identify potential projects for Lean UX incorporation: Turn Lean UX into a competitive advantage: Open Source Intuitive UI Feature Rich Creative Technology Strategy Capabilities App White Papers Pitch Work Operational efficiency Higher value proposition Industry Leadership Getting Lean
  19. 19. 2525 Reference Material
  20. 20. 2626 http://moduscreate.com/baby-steps-lean-ux/ https://www.rallydev.com/blog/agile/top-3-reasons-designers-object-agile-and-how-overcome-them http://www.smashingmagazine.com/2014/01/08/lean-ux-manifesto-principle-driven-design/ http://blog.teamtreehouse.com/responsive-web-design-in-the-browser-part-1-kill-photoshop http://blog.teamtreehouse.com/responsive-web-design-in-the-browser-part-2-the-tools