Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

CWP Meetup - All of Government Design

128 views

Published on

Our fifth CWP Meetup looks at All of Government (AOG) design (shared design across the different government agencies).Looking at government as a digital service from a user point of view, one could argue it is disjointed in parts, and consequently does not inspire trust in terms of consistency in experience across its many use cases.
It’s a common problem – not just for government digital services, but also for many large organisations.

Published in: Government & Nonprofit
  • Be the first to comment

  • Be the first to like this

CWP Meetup - All of Government Design

  1. 1. An all of government
 design system. CWP Meetup March 21 2018
  2. 2. • Introduction • Background • GIS • What is a design system? • User needs • Business needs • Pattern library • Plans • Questions
  3. 3. About • Mark Kirkpatrick • Digital Communications • Delivery Manager
  4. 4. Background • Ulster rebrand • Addressing issues with poor UX, accessibility
  5. 5. Goal • Creating cohesiveness and consistency • Engaging active communities with the new practice
  6. 6. Creating a service design manual Ulster
  7. 7. What role GIS plays Government Information Services data.govt.nz govt.nz gazette.govt.nz digital.govt.nz
  8. 8. Operating across government • Develop and improve services for users and agencies • Partner with others (gov/private) to deliver services • Support system outcomes • Experiment in thinking/technology
  9. 9. It doesn’t have 
 to be like this
  10. 10. GIS and MSD working together
  11. 11. Further Collaboration • GIS work with the Service Innovation Lab and SmartStart teams to meet user needs around identifying relevant family and social services when having a child.
  12. 12. Its a.. Open Government Partnership Using new technologies to make government more open, effective, and accountable.
  13. 13. data.govt.nz • A strong need for design components when working with data.govt.nz
  14. 14. data.govt.nz 22% • The team at GIS estimate that savings of approx 22% of the total cost of releasing a beta data.govt.nz in 2016 could have been saved had there been well documented, easily reusable design patterns to reuse in the process of building the beta site.
  15. 15. What is a Design System?
  16. 16. “A scalable framework of decisions & team behaviours across a product portfolio to converge on a cohesive experience.“ - Nathan Curtis
  17. 17. Structure of a Design System Color Palettes Typographic Scales Grid Definitions Icons & Assets Templates Modules Components Elements Design Principles Implementation Guidelines Editorial Guidelines Building Blocks UI Patterns Rules
  18. 18. Design systems help solve problems of scale like: 1. Inconsistent user experience across products and platforms 2. Version control issues 3. Knowledge gaps between design and development 4. Inefficient processes that lead to repetitive or wasted work Source: Atlassian
  19. 19. User needs
  20. 20. Easy to use Joanne “ I was overwhelmed by how hard these tools were to use, I missed opportunities I was eligible for, and felt frustrated and isolated.
  21. 21. Consistent I want it to feel familiar and be intuitive, so I know what to do and can accomplish a task. A consistent look will feel familiar, trustworthy, and secure. “ Joanne
  22. 22. Government inconsistencies (user)
  23. 23. Govt Design System (UK) Different use cases, familiar paths, patterns
  24. 24. “Users need to experience consistently applied interface elements that are familiar, usable and accessible when using government services so that those services are trusted, inclusive and used.”
  25. 25. Business needs
  26. 26. There’s more demand than ever for designers, developers, but with the new scale, new problems emerge…
  27. 27. Business requirements pressure the team to build more, faster and better, but without standards in place, every new team member can further slow down the process.
  28. 28. Team Product New Styles, Patterns, Ideas… New Styles, Patterns, Ideas… New Styles, Patterns, Ideas… Without a Design System…
  29. 29. • Are we always happy with the speed of product development? • How much time and money do we spend on redundant design or code tasks? • How much time and money do we spend cleaning up design or technical debt? Common problems
  30. 30. • What shade of blue are we using? • Can you redline this for me? • Can you redesign this, we can’t build it? • Where are approved stock photos? • Was this pattern used somewhere else? Common questions - design
  31. 31. • Can you rebuild this, it doesn’t match the design? • What’s the latest documentation? • How do we build this pattern? • Does this meet the code standards? • Where’s our components? Common questions - development
  32. 32. Government inconsistencies (business)
  33. 33. • Conceptualised • Created • Evaluated • Tested • Implemented • Iteratively improved / optimised Components / modules

  34. 34. To overcome inconsistencies, organisations are investing in Design Systems.
  35. 35. Yes No, but we're currently working on one No, and we aren't working on one I don't know 0% 10% 20% 30% 40% Does your company have a design system or a pattern library? UXPin surveyed 3,157 designers, PMs, and developers
  36. 36. Benefits
  37. 37. Design system ROI Design systems also save time and money. Just by eliminating code redundancy, more than 20% of a developer’s time can be regained. For a team of 100 developers, this means around $2 million per year.” - projekt202 Managing Architect Drew Loomer • We want to get similar data from a NZ context • Identify cost-saving opportunities • Time-saving too!
  38. 38. Time saved thanks to reuse of components in build/protyping etc. Other benefits include…
  39. 39. We’ll deliver better experiences faster. Users will notice.
  40. 40. By using well-tested components, we’ll lower the cost of long-term maintenance.
  41. 41. New team members can get up to speed quicker - with faster standardised on- boarding with a design system.
  42. 42. We bake in quality and standards - delivering lean, accessible, reusable, useful components.
  43. 43. • Pattern library?… Next steps
  44. 44. Quote 2 “Pattern libraries are sometimes thought of as interchangeable with design systems. But even the most comprehensive and living pattern library is not the system itself. It’s a tool that helps to make a design system more effective.” - Alla Kholmatova
  45. 45. Zombie library!!
  46. 46. Next steps • Explore further government need • Reuse research by other agencies • Start small - release early (alpha) • Test community and contributor model • Explore some exemplar opportunities (DIA, etc.)
  47. 47. Next steps @timpaul
  48. 48. Interesting stuff
  49. 49. Interesting stuff
  50. 50. Interesting stuff
  51. 51. Interesting stuff
  52. 52. Interesting stuff https://inclusive-components.design/
  53. 53. Interesting stuff
  54. 54. Contact @mkirkpat mark.kirkpatrick@dia.govt.nz

×