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

"Open" includes users - Leverage their input

Carregando em…3

Confira estes a seguir

1 de 124 Anúncio

Mais Conteúdo rRelacionado

Diapositivos para si (20)

Semelhante a "Open" includes users - Leverage their input (20)


Mais recentes (20)


"Open" includes users - Leverage their input

  1. 1. “Open” includes Users - Leverage their Input
  2. 2. + Open Source Enthusiast since 2006 + Ubuntu Loco Zurich 2008/9 + Blending Tech with Business and User needs since 2010 Randy Earl Research Manager + IT & Mgmt. for 20+ years + At Atlantic BT for 4 years + MBA, BS Physics NCSU + Former Naval Officer + Zen Chaplain at NCSU Specialties + Mapping business models + Structuring analytical approaches + Facilitating team collaboration + Translating business to technology
  3. 3. I am the Usability Curmudgeon https://www.wired.com/2016/10/how-the-web-became-unreadable/
  4. 4. I don’t make Software… I make software Better!
  5. 5. To scratch an itch? To make something new? To do something better than it is done elsewhere? Often, Open Source is Innovative - both at the major concept level and at the iterative improvement level! Why Do you write Open Source Code?
  6. 6. All Things Open 2016 keynote statements focused on Diversity and Innovation: ● “To truly innovate, you need to intentionally seek diversity” ● “Diversity has to be intentional” ● “You have to question your opinions in order to be open to others”
  7. 7. “To seek the truth, you must first cease to cherish opinion.” From Faith in Mind (Xin Xin Ming) By Sengcan, Third Patriarch of Zen 7th Century China
  8. 8. + Demographics? + Skill Level? + Knowledge & Interests? + Use Case? + Background / Context? ALL OF THE ABOVE What does “Diversity” Mean?
  9. 9. There is a great discussion around the value of building and encouraging diversity. However, the majority of that discussion thus far has been around the developer community – yet there are two sides to any interface. How to Get Diversity?
  10. 10. If you think of your application as a window to the world, then the users are the other half of that equation. In terms of sheer volume, users far outnumber contributors for your application. Intentionally building and engaging with a diverse user base can drive innovation and improve your software. How to Get Diversity?
  11. 11. None of us is as smart as all of us!
  12. 12. The open source community has a reputation for often ignoring users and usability – sometimes to the point of ridicule. How many of us have groaned over the years at the quirky interfaces of beloved applications such as the GIMP? (or name your favorite, there are many) Why Does this Matter?
  13. 13. “It’s easy to end up with underlying code that is as wonderful as a bacon flavored mouthguard, and then a user interface on top of that that’s flat out impossible for an average user to navigate.” - Techquickie
  14. 14. Well, it could be simply embarrassing. However, there could be serious Business Impacts. I have seen both consumer and business applications where the interfaces were so bad users were either unable or unwilling to suffer through the interface to use the application and went elsewhere. Is this Important?
  15. 15. What did you think of the Snapchat Redesign?
  16. 16. Snap’s daily average user growth slowed to 2% over prev qrtr. Negative publicity hurt its ad business. Snap’s stock plummeted to new lows. CEO Evan Spiegel ignored early user testing of the redesign that showed mixed results. In hindsight he said: “There is no doubt that collaboration yields better results”
  17. 17. In any business model, and particularly open source, ignoring users can be disastrous!
  18. 18. Why especially Open Source? Fierce competition of ideas and ability to fork. Profusion of Distros, Desktops, and Apps have been both blessing & curse. Think of Nextcloud vs. ownCloud...
  19. 19. + A Tool Portal intended to make life easier for Faculty. + Users found it simpler to work around the system. + Culprits: + Poor Usability Heuristics + Screenflow did not match User Workflow + Inconsistent Mental Model of Overall Approach Tortured Workflow Example
  20. 20. Wolfware: Heuristics Evaluation
  21. 21. Detailed Examination of Each Issue
  24. 24. Research can be seen as Very Complex... https://indiyoung.com/orgs-reject-a-healthy-variety-of-methods/
  25. 25. Or it can be very simple
  26. 26. For greatest effect, focus on Problem Space, not Solution Space + Problem Space - Larger purpose / intent, user needs + Solution Space - Ideas & design, features & functionality Problem Space vs. Solution Space
  27. 27. Research is just Asking Questions
  28. 28. However, Research is NOT asking what people like, dislike, or what they want.
  29. 29. “Often, customers know what they want, but don’t know how to articulate it. So, ask specific questions that allow you to glean insights to use for your innovation.” - Entrepreneur.com “If I had asked people what they wanted, they would have said faster horses.” - NOT Henry Ford
  30. 30. “An innovator should have understanding of one’s customers and their problems via empirical, observational, anecdotal methods or even intuition. They should also feel free to ignore customers’ inputs.” - Harvard Business Review
  31. 31. The Key to Good Research - Asking the Right Questions
  32. 32. 1. Formulate the Question 2. Determine Method for asking the Question 3. Analyze the Results Research is a Structured Process for Asking Questions
  33. 33. A well-rounded solution covers multiple perspectives: + Organizational Objectives + User Needs + Product Features & Interface + Market / Competition There are questions to asks and methods appropriate for each area. 1. Formulating Questions
  34. 34. 2. Asking Questions - an Overview of the Research Methods we use
  35. 35. This can be simple or can be complex. Want to make sure you can get a meaningful answer. Think about analysis when forming question and method. Example - bad survey questions: + Double-barreled (“or”) questions + Biased or Leading questions + Use of Double-negatives 3. Analyzing Results
  36. 36. Analysis methods can range from simply Counting yes / no answers To complex methods:
  37. 37. Prototype Testing
  38. 38. An experimental model of an idea, A way to give our ideas a presence, That we can put in front of someone else, to see if that idea has value. What is a Prototype?
  39. 39. + Very little effort required + No visual design + No code development + Rough sketches on paper + A script of questions + Careful observation of answers and behavior Paper Prototyping
  40. 40. First round Design - first presentation resulted in redoing over a week of design work. Second round - invested 8 hours to do paper prototyping of concepts before proceeding with design. Impact?
  41. 41. Entrepreneur Example Weeks spent writing code for working MVP. Demo to investor showed workflow and result screen. Investor based decision based on result screen, not the code behind it. Image generated (variant on encoded images) could have been simple png files for demo!
  42. 42. + Reverse the process + Pitch a site or application concept + Participants then create paper prototypes + Important to limit them to 10-15 minutes + Have them pair up and pitch their concept to each other + Or present some to the group + Observe the differences in Mental Models!!! Extreme Paper Prototyping
  43. 43. https://www.drawtoast.com/
  44. 44. More Types & Methods of Tests
  45. 45. Collected Comments from Feedback Forms
  46. 46. Collected Comments can be Valuable - BBQ Restaurant Chain
  47. 47. + Common wisdom - mostly complaints - not always true. + Largest word was “thank” + Notice also “please” - often feature requests. + Sentiment analysis - “family”, “party”, “love”, etc. + Topic analysis - “business” and “catering” Word Cloud - Quickie Analysis
  48. 48. Card Sorting
  49. 49. Card Sorts are an excellent way to see how people Organize Information
  50. 50. Simple Card Sort to Prioritize Home Page Elements
  51. 51. Using the Free Tier of https://www.optimal workshop.com
  52. 52. Demo video I created: https://youtu.be/rKbNrN-dx9U
  53. 53. Analytics Review
  54. 54. Google Analytics “Why do this review? We KNOW this industry, we BUILT this industry 40 years ago!” - Marketing Director, B2B Client Client was having problems with users finding products. Their product catalog listed “Personal Care” Users were searching for “Hygiene”
  55. 55. Google Analytics Resolution: We kept both - for those who were used to the existing terminology, but added ‘Hygiene’ for those who were searching for it.
  56. 56. Respect your users - give them an efficient UI
  57. 57. Red Hat + Very smart, talented people. + Reluctance to ‘dumb down’ the experience. + But that is not the point. “the interface needs to be as efficient as possible, because our users are very busy and have little time.” - Tesh Patel; Senior Manager, Learning Technologies and Platforms at Red Hat Red Hat Learning Experience Layer
  58. 58. "Just because I can figure something out doesn't mean I want to." - Tech-Savvy Workshop Participant Don’t Overwork Your Users
  59. 59. Key Point - interface to enable/automate a process online. High-value, low volume interaction (thus low ability to learn, yet high consequences). Interface so bad, new users had to be walked through live. Heuristics & Workflow analysis, implemented in a new design Anonymized Tortured Workflow Example
  60. 60. Examples & Results
  61. 61. Simple Labeling Question: NC Courts Website
  62. 62. Which label is more effective? + Self Help + Help Topics + Legal Topics LABEL TESTING - NC COURTS Label Testing
  63. 63. Legal Topics outperformed Self Help by 6%, with a 23% boost in user confidence. Small improvements can have a significant impact over millions of citizens! RESULTS OF LIVE USER TESTING - NC COURTS
  64. 64. User Task Driven Navigation: NC Department of Revenue
  65. 65. Call Center Data indicated several navigation problems. 14 distinct Personas need to complete a task on the DOR website that involves finding or using information. This indicates that the ability to find and understand the information on the DOR website is critical, because it impacts the experience of a broad range of users.
  66. 66. Navigation: NC Dept of Revenue Issue: There were loops where user could get stuck and not find the path to find and pay their taxes.
  67. 67. Solution: How we addressed the problem: + Performed User Needs workshops + Developed Task-Based Personas + Developed Task-Based Workflows + Built Site Navigation to support those Workflows + Tested Iterations of New Navigation + Revised based on Test Results We switched to Task-based navigation with a clear journey path. Navigation: NC Dept of Revenue
  68. 68. Navigation: NC Dept of Revenue How we validated the improvement Tree Testing with real users showed: + 80% success + 88% directness + 4.8 seconds
  69. 69. Dep’t of Revenue Business Impact Go-Live was Dec 2017 Four Month Tax Season of 2018 saw: + 18% increase in sales tax E-filing * + 14% increase in withholding tax E-filing * + Reduction of 26,000 live agent calls * Typical annual increase is 6-8%
  70. 70. Usability Testing
  71. 71. A thing is usable if: + A person of average - or even below average - ability and experience (i.e. most people) + Can figure out how to use the thing for its intended purpose + Without it being more trouble than it’s worth What is “Usability”?
  72. 72. User-Centric Guiding Principles Use this model to determine what content (including features and functionality) to provide and how to structure it. All use is contextual, idiosyncratic.
  73. 73. + There will always be problems, opportunities. + Finding them earlier saves time and $. + Improve user experience and satisfaction. + Find opportunities to innovate. + Accelerate your Iteration Cycle. Why Do Usability Testing?
  74. 74. + Determine your research questions + What hypothesis do you want to test? + E.g. Labels, Workflow, Navigation, etc. + Write the Tasks needed to force the user to face that issue + Ensure testing Prototype covers those tasks You aren’t looking for the problems you know you are going to fix - you are looking for the problems you don’t know about yet! How to - What do you want to Test?
  75. 75. + Your Site or Application + Competitor Site or Application + A Paper Prototype of the Concept + Wireframes + Clickable Mockups How to - What to Test With
  76. 76. + Representative users often needed, but not always + We sometimes use colleagues in our office + Use a sample from your client’s office + Recruit in related spaces (e.g. jury pool for gov’t sites) + Events like this one! (ask first, don’t violate courtesy) “Recruit loosely & grade on a curve” - Steve Krug How to - Recruiting
  77. 77. + Not a question of statistics & sample size + Focus on gaining key insights + Thus 3 to 5 are enough! + These will reveal major problems + More will just drown you in papercuts How to - Sample Size
  78. 78. + Write the Scripts for the Tasks + Prepare Permission forms + Ensure proper testing equipment + Secure a testing space + Prepare a recording method How to - Prepare the Test
  79. 79. + Have 2 testers, 1 Moderator and 1 Observer (note taker) + Record with Camtasia, webcam, etc. + Have the entire process scripted, not just tasks + Go through the Tasks + Thank and compensate Participants How to - Perform the Test
  80. 80. + Focus on the Key Insights! + Gather these from Moderators and Research Team immediately, while fresh. + Don’t get distracted by papercuts. + Don’t need a fancy report + Make images, recordings available to others How to - Perform the Analysis
  81. 81. Recordings can be extremely useful - share broadly!
  82. 82. “This Test is Over” Usability Test Participant before the first task - why? You will learn something useful, guaranteed!
  83. 83. When to Test? “A little before you think is reasonable” Steve Krug
  84. 84. Agile Development is cyclic: 1. Requirements 2. Plan 3. Design 4. Develop 5. Release 6. Track & Monitor In simple form it is the Deming Cycle:
  85. 85. User testing can help: + Tweak, not re-design + Make smallest changes that address an issue + Test impact and repeat Agile Development and Iteration
  86. 86. + Focus ruthlessly on a small set of important problems. + Don’t get lured into quick & easy fixes to trivial problems. + Ask each observer to rank top 3 most serious problems. What to do with Test Results?
  87. 87. Resources to Get Started
  88. 88. Just Enough Research By Erika Hall
  89. 89. Gamestorming.com Book and website, great resource for group & workshop methods.
  90. 90. Steve Krug ❖ Don’t Make Me Think ❖ Rocket Surgery Made Easy ❖ Sensible.Com
  91. 91. Where to Get Help
  92. 92. Triangle UXPA User Experience Professionals Association The Triangle UXPA was founded in 2006 and is the North Carolina Raleigh/Durham/Chapel Hill chapter of the User Experience Professionals Association. We are focused on building and supporting the local community of practitioners who craft great user experiences.
  93. 93. + TriUXPA + Other meetups such as A11Y + Graduate student interns + Open Source Community Volunteers + UX / Design professionals in your office/team Where to Get Help?
  94. 94. Q&A Time
  95. 95. Thank you! I’d love to talk to you Randy.Earl@Atlanticbt.com @randy_Earl
  96. 96. NC Department of Commerce Card Sort Session
  97. 97. Site Navigation Navigation design draws from 3 key sources: 1. User Needs 2. Content 3. Business Goals
  98. 98. NC Department of Cultural Resources Tree Test using Optimal Workshop Tree Test
  99. 99. Content types help your content creators maintain standards and work efficiently. Content types allow designers to create custom page templates. Content Types
  100. 100. Example from State of NC Digital Commons Government Content Type
  101. 101. NC Courts Search capability is tremendously enhanced by a well structured taxonomy. Such search capabilities are only possible with taxonomic categories established for each filter and facet, with vocabularies populated for each one. Taxonomy
  102. 102. Build Search Capability We believe Drupal 8 native search is not a suitable option as it is limited in functionality. ABT plans on evaluating all options, along with an option we propose - Swiftype, a SaaS solution. Search Options to Evaluate: + D8 Native + Acquia / SOLR + Elastic + IBM Watson + Swiftype
  103. 103. Design
  104. 104. WIREFRAMES
  105. 105. MOCKUPS
  106. 106. PAGE TEMPLATES
  107. 107. WIDGET DESIGN
  108. 108. WEARABLE DESIGN + Accessibility & Convenience + City Information Source + Retail Opportunities + City Event Notifications + City Maps and Parking Info + Transportation Options & Locations
  109. 109. Development & Integrations
  110. 110. We Live and Breathe DevOps We write, deploy, and support software code and applications every day. We adopted DevOps best practices years ago, because it was the best way to improve the efficiency and quality of the applications we create for our clients.
  111. 111. DevOps Philosophy + Facilitate faster deployments of features into production + Deploy in a more structured and automated way + Deploy features with fewer errors
  112. 112. ABT DevOps for CoR + CI/CD already set up for CoR + ABT’s Drupal team is experienced & growing + We can leverage the work we have done already
  113. 113. Technical Audit An application architect or lead developer will audit the existing site to determine existing functionality that needs to be implemented on the new site. This includes looking at the code base, determining how existing features are implemented and how they might be implemented in Drupal, and determining the existing data structures. Technical Specifications An application architect or lead developer will begin documenting any technical plans that come from the research, designs, or technical audit. This will not result in a polished, unchanging set of specifications; instead, it will be a reference document that can be updated during development. Site Administration & Settings Setup Much of the administration and settings have already been established, but it is very likely some changes will be identified throughout the design and development phases. Site Structure & Navigation The site structure and navigation should have been identified in a previous stage, and therefore building the navigation will need both front end development to build the navigation in the template and to site-build the navigation through the admin. DEVELOPMENT PREPARATION
  114. 114. The development of the base work in Drupal include the following: + Content Type Development: This is creating the content type definitions in Drupal, such as assigned fields, types, and selection values + Layout / CT Implementation: This is building the actual site markup for layouts using content types , and connecting front end development with back end development. + Template Creation: Converting static markup developed in layout step to Drupal’s template system. + Views Templates: Developing Drupal templates for dynamic lists of content known as Views. + Components / Widgets: Similar front and back end development for widgets identified in requirements gathering. PRIMARY SITE DEVELOPMENT
  115. 115. This is additional development beyond developing the primary content types and layouts. For the City of Raleigh, we have identified this as the following: + Content Type Workflow Setup: the workflow developed in Phase 1 needs to be applied to each new content type that is created. Additionally, additional workflows may need to be created based on the requirements developed for those content types. + Forms Setup: It is identified in the RFP there are forms to migrate. Some development occur to set these up and process submittals. + Accessibility Development: Additional development and QA will be required to verify all front end development meets WCAG AA standards beyond the typical 508 compliance. Atlantic BT uses industry standard tools for testing compliance. + Permissions: While a permission system is in place, permissions will have to be updated after when content types and modules are added to the system. It is also expected additional permissions based on user departments will be a requirement as well. + Digital style guide: This is a standard deliverable from Atlantic BT, especially useful for any design where microsites may be utilized. It provides very clear documentation tying the visual design to the markup of the site. + Analytics Configuration: Marketing support for any Google Analytics configured required by the City of Raleigh. ADDITIONAL SITE DEVELOPMENT
  116. 116. 3rd Party Integrations can range from straightforward to complex when factoring in requirements gathering, implementing within a new design, and development. APPLICATION INTEGRATIONS
  117. 117. + Google Analytics + Google Search Appliance/SEO + Everbridge Atlantic BT expects these integrations to be straightforward. ABT will of course work with the City of Raleigh on requirements and approach, but the use cases and interfaces are pretty standard. APPLICATION INTEGRATIONS
  118. 118. + ArcGIS + GovDelivery + Sharepoint These integrations will likely be more involved, in determining how these services will be used and/or the actual development and integration. Sharepoint in particular is a large unknown, and will benefit from agreeing on a prioritized list of features and iterative development. APPLICATION INTEGRATIONS