lessons leadership and legacy
play

Lessons, leadership and legacy With Jon Fisher @ergonjon Head - PowerPoint PPT Presentation

Lessons, leadership and legacy With Jon Fisher @ergonjon Head of User Experience Lessons, and leadership Amanda and legacy Payne @mandalyn97 Account Director Lets talk about delivery across Government Chapter 1


  1. Lessons, 
 leadership 
 and legacy

  2. With Jon Fisher @ergonjon Head of User Experience Lessons, 
 and leadership 
 Amanda 
 and legacy Payne @mandalyn97 Account Director

  3. Lets talk about delivery across Government…

  4. Chapter 1 Project Lessons

  5. You don’t have as many 
 users as you think “You will never understand how complex our 
 service is” said on Day 1 of every project ever. But just because you have 24 job roles doesn’t 
 mean you have 24 personas. Lessons

  6. You don’t have as many 
 users as you think Lessons

  7. Observe your users in the wild Government services routinely involve complex niche audiences across diverse locations. Get out of the lab and watch the daily struggles 
 with your service for real! Lessons

  8. Observe your users in the wild Lessons

  9. Champion inclusive design Leading on inclusion at all levels makes the entire service better. More and more we advocate for diversity to be included in research and not separated out as separate activities. It’s 2019 and we are still frequently having 
 these conversations! Lessons

  10. Champion inclusive design Lessons

  11. If in doubt… content Government services come in all shapes, sizes and budgets but most importantly with di ff ering levels 
 of confidence. But without doubt if looking for maximum “bang for buck” value then change your content. Digital Transformation isn’t always about your tech stack… Lessons

  12. If in doubt… content Lessons

  13. Chapter 2 Leadership Lessons

  14. Actually define the service Break the assumption that service design starts and ends with digital platforms. Whilst digital is key, appropriate channel shift is the desired outcome. Find champions across the service and empower them to advocate the lived experience. Leadership

  15. Actually define the service Leadership

  16. Knowing when to challenge Our role is to prepare leaders in the public sector to challenge and be challenged by stakeholders and GDS. It’s our job to ensure the service is on the right path to not only pass gateways but to be successful to all users. Sometimes di ffi cult conversations need to be had. Leadership

  17. Knowing when to challenge Leadership

  18. Acknowledge when things 
 have changed Recognise that the delivery of exceptional services occurs over years not days, things change. Whether its referendums, new legislation or simply gaps in your knowledge, your research activities need to reflect this. Leadership

  19. Acknowledge when things 
 have changed Leadership

  20. Not everyone is in Gry ffi ndor Putting people into pre-defined groups can lead to large, bulky teams and potentially silos of “specialisms”. Interesting things can happen when you break out of the sorting hat mentality… Leadership

  21. Not everyone is in Gry ffi ndor Content Service 
 design design Development Leadership

  22. Not everyone is in Gry ffi ndor Content Service 
 design design Development Leadership

  23. Chapter 3 The Legacy Framework

  24. “Put in place a sustainable team that can design, build and operate the service, led by a suitably skilled and senior service owner with decision-making responsibility” –The Digital Service Standard Legacy

  25. Will the service be successful? Building on our experiences, we started to think about the types of team behaviours that led to “good” or “bad” projects. We have identified seven indicators that help us judge when to lead, when to listen and when to walk away… Legacy

  26. Maturity of Techniques Box-ticking Reliance on one technique Tokenistic funds for research Reliance on validation and secondary sources Legacy

  27. Maturity of Techniques Box-ticking Cultural change Reliance on one technique Broad range of appropriate techniques applied Tokenistic funds for research Mixture of quant and qual to Reliance on validation and answer open questions secondary sources Legacy

  28. Inclusive Design Box-ticking The ‘box’ of non-standard users The disabled persona The phrase “those kinds of people” Separate and late Legacy

  29. Inclusive Design Box-ticking Cultural change The ‘ghetto’ of non-standard users People are people no matter what The disabled persona Early and often The phrase “those kinds of people” Lots of people talking about Separate and late Recognises di ff erence between permanent and temporary Legacy

  30. Willingness to change Box-ticking Belief that legacy system 
 prevents change Decision paralysis Lack of leaders Legacy

  31. Willingness to change Box-ticking Cultural change Belief that legacy system 
 What can we do with what 
 prevents change we’ve got Decision paralysis Proactively embraces change Lack of leaders How can we make small changes with big impact Legacy

  32. Research Continuity Box-ticking “It’s done” Inability to trace user needs through the dev process No research after discovery User research only attended 
 by URs and Designers Legacy

  33. Research Continuity Box-ticking Cultural change “It’s done” Continues to research across 
 all stages Inability to trace user needs through the dev process User needs for part of the 
 success criteria No research after discovery Research is attended by all User research only attended 
 by URs and Designers Legacy

  34. Deliverables Box-ticking Deliverables sit on the shelf Prescribed at the start 
 and not changed Follows guidance 
 without understanding Legacy

  35. Deliverables Box-ticking Cultural change Deliverables sit on the shelf Deliverables visible and physical and available to all Prescribed at the start 
 and not changed Outputs emerge and change 
 as we learn more Follows guidance 
 without understanding Uses guidance to inform 
 decision making Legacy

  36. Growth of Skills Box-ticking Turnover of sta ff Small teams die on the vine Discipline silos persist Legacy

  37. Growth of Skills Box-ticking Cultural change Turnover of sta ff Emergence of t-shaped practitioners Small teams die on the vine Practitioners assisting in 
 Discipline silos persist resource cover Small teams empowered to 
 achieve by product owners Legacy

  38. Responsibilities Box-ticking Culture of blame Resolving blockers takes time “Not my job” Legacy

  39. Responsibilities Box-ticking Cultural change Culture of blame Silos become invisible Resolving blockers takes time Roles don’t matter in 
 decision making “Not my job” Shared problem solving Legacy

  40. Legacy

  41. Indicators of 
 Cultural change Maturity of Techniques Inclusive Design Willingness to change Research Continuity Deliverables Growth of Skills Responsibilities Legacy

  42. We aim to leave a legacy 
 of user centred cultural change 
 in the services we design.

  43. We aim to leave a legacy 
 of user centred cultural change 
 in the services we design. Stop trying to “pass the assessment” and focus on delivering a great service!

  44. Thank you Jon Fisher Amanda Payne @ergonjon @mandalyn97

Recommend


More recommend