Lessons learned as a Government (deputy) CTO James Stewart - - - PowerPoint PPT Presentation

lessons learned as a government deputy cto
SMART_READER_LITE
LIVE PREVIEW

Lessons learned as a Government (deputy) CTO James Stewart - - - PowerPoint PPT Presentation

Lessons learned as a Government (deputy) CTO James Stewart - YOW!West 2017 @jystewart GDS Revolution, not evolution That became the UK No more than seven words per line I w Government Minimum font size of 36pt Digital Service


slide-1
SLIDE 1

Lessons learned as a Government (deputy) CTO

James Stewart - YOW!West 2017 @jystewart

slide-2
SLIDE 2

GDS

slide-3
SLIDE 3

Revolution, not evolution

slide-4
SLIDE 4

@jystewart

No more than seven words per line

Minimum font size of 36pt

I w

That became the UK Government Digital Service

@jystewart

slide-5
SLIDE 5

GDS

slide-6
SLIDE 6

We joined forces with the technology reform team, gaining spend controls

@jystewart

slide-7
SLIDE 7
slide-8
SLIDE 8

GOV.UK 25 redesigned services GOV.UK Verify, Pay, Notify Assisted digital support Digital skills in government Digital Marketplace Better, cheaper technology Saved billions

GDS @jystewart @jystewart

slide-9
SLIDE 9

https://www.gov.uk/design-principles & https://www.flickr.com/photos/psd/9120523574/

slide-10
SLIDE 10

@jystewart

slide-11
SLIDE 11

@jystewart

No more than seven words per line

Minimum font size of 36pt

U.S. Digital Services Playbook

The American people expect to interact with government through digital channels such as websites, email, and mobile applications. By building better digital services that meet the needs of the people that use our services, we can make the delivery of our policy and programs more effective. Today, too many of our digital services projects do not work well, are delivered late, or are over budget. To increase the success rate
  • f these projects, the U.S. Government needs a new approach. We
created a playbook of 13 key “plays” drawn from successful best practices from the private sector and government that, if followed together, will help government build effective digital services. SEE THE PLAYS HELP IMPROVE THIS CONTENT

DIGITAL SERVICE PLAYS

  • 1. Understand what people need
  • 2. Address the whole experience, from start to finish
  • 3. Make it simple and intuitive
  • 4. Build the service using agile and iterative practices
  • 5. Structure budgets and contracts to support delivery
  • 6. Assign one leader and hold that person accountable

Information and services

Govt.nz

Connecting you with government information and services Government A-Z Government A-Z Information and services Information and services About Go About Go Search govt.nz ! We've rebuilt newzealand.govt.nz - tell us what you think Births, deaths, marriages Certificates, ID, wills, relationships, name change, pregnancy, divorce. Citizenship and immigration Residency, visas, work and study in NZ. Community, arts and sport Tramping and camping, funding, fishing and volunteering. Consumer rights Consumer disputes, complaints, scams and fraud. Crime, law and justice Jury, fines, prison and neighbourhood issues. Driving and transport Driver licences, tickets and fines, WOFs and registration. Education and training School terms, special education, student loans and apprenticeships. Emergencies and disasters Civil defence alerts and emergency planning. Environment and climate Conservation, daylight saving, natural resources and weather. Health Public funded healthcare, GPs, children's health. History, culture and heritage Historical records, Māori culture, family history. Housing and property Buying, selling, renting, renovating and building. Internet, media and communication TV and radio, online security, advertising. Money, benefits and tax Financial help, NZ Super, paying tax and KiwiSaver. Parliament and politics Parliament and elections,
  • fficial information requests
and have your say. Passports, travel and tourism Visit NZ, go overseas to visit
  • r live.
Work and jobs Holidays and time off, paying ACC, redundancy and working for yourself. Rules reduction The Rules Reductio looking at updating property rules in Ne Compliance Ma small business If you’re a small bu you can manage al compliance require new tool from busin New duty free rules cigarettes and to The limit for duty fr An official website of the United States Government

f

Building the 21st century digital government.

Part of a global movement working for open, digital government

@jystewart @jystewart

slide-12
SLIDE 12

@jystewart

slide-13
SLIDE 13

Digital transformation is a big deal

slide-14
SLIDE 14

We saved £3.56 billion over three years

slide-15
SLIDE 15

but we started with a prototype of a website

slide-16
SLIDE 16

GDS

slide-17
SLIDE 17

@jystewart

GOV.UK did many things

slide-18
SLIDE 18

@jystewart

Simpler, clearer, faster for users, with savings and efficiencies for government

slide-19
SLIDE 19

@jystewart

It demonstrated that a different model of delivery was possible

slide-20
SLIDE 20

@jystewart

It showed government could work together, across silos

slide-21
SLIDE 21

@jystewart

It energised a group of people inside and

  • utside government
slide-22
SLIDE 22

@jystewart

It started to generate data to deepen (and challenge) our insights

slide-23
SLIDE 23

@jystewart

It let us work from the

  • utside in
slide-24
SLIDE 24

Show don’t tell.

(the formal strategy came later)

slide-25
SLIDE 25

@jystewart

No more than seven words per line Minimum font size of 36pt

GDS GDS GDS @jystewart

slide-26
SLIDE 26

@jystewart

1. Understand user needs 2. Do ongoing user research 3. Have a multidisciplinary team 4. Use agile methods 5. Iterate and improve frequently 6. Evaluate tools and systems 7. Understand security and privacy issues 8. Make all new source code open 9. Use open standards and common platforms

  • 10. Test the end-to-end service
  • 11. Make a plan for being offline
  • 12. Make sure users succeed first time
  • 13. Make the user experience consistent with

GOV.UK

  • 14. Encourage everyone to use the digital

service

  • 15. Collect performance data
  • 16. Identify performance indicators
  • 17. Report performance data on the

Performance Platform

  • 18. Test with the minister

https://www.gov.uk/service-manual/service-standard

slide-27
SLIDE 27

@jystewart

1. Understand user needs 2. Do ongoing user research 3. Have a multidisciplinary team 4. Use agile methods 5. Iterate and improve frequently 6. Evaluate tools and systems 7. Understand security and privacy issues 8. Make all new source code open 9. Use open standards and common platforms

  • 10. Test the end-to-end service
  • 11. Make a plan for being offline
  • 12. Make sure users succeed first time
  • 13. Make the user experience consistent with

GOV.UK

  • 14. Encourage everyone to use the digital

service

  • 15. Collect performance data
  • 16. Identify performance indicators
  • 17. Report performance data on the

Performance Platform

  • 18. Test with the minister

https://www.gov.uk/service-manual/service-standard

Do you know what to do? Are you serious about it? Are you seeking feedback? Can you make it better?

slide-28
SLIDE 28

@jystewart

“How do I make that pink?”

  • Ben Terrett, so many times
slide-29
SLIDE 29

Start small, focus on users, build trust through delivery

slide-30
SLIDE 30

Make things open, it makes things better

slide-31
SLIDE 31

We made a big splash by committing to open source code and open standards

things Make

  • pen,

it makes things better

slide-32
SLIDE 32

Openness is about so much more than source code

slide-33
SLIDE 33

@jystewart

High performing teams have autonomy

slide-34
SLIDE 34

@jystewart

Autonomous teams thrive in an open culture

slide-35
SLIDE 35
slide-36
SLIDE 36

He made it beautiful

slide-37
SLIDE 37

GDS @jystewart

slide-38
SLIDE 38

https://www.gov.uk/design-principles / https://www.flickr.com/photos/psd/9120523574/

slide-39
SLIDE 39

Openness is about transparency of values and principles

slide-40
SLIDE 40

@jystewart

“The James Branch”

slide-41
SLIDE 41

Openness is about accepting challenge

slide-42
SLIDE 42

@jystewart

"Blame the process, not the people"

  • W Edwards Deming
slide-43
SLIDE 43

@jystewart

It’s time to go beyond “the andon cord”

slide-44
SLIDE 44

Openness is about participation

slide-45
SLIDE 45

Everyone must know why the work matters & what matters about the work

slide-46
SLIDE 46

Moving security out

  • f the square of

despair

slide-47
SLIDE 47

GDS

Unclassified Protect Restricted Confidential Secret Top Secret IL0 IL1 IL2 IL3 IL4 IL5 IL6

& &

baseline control set, accreditation, assurance, SIRO, RMADS, IAO, GPG, CIAN, PGA, CLAS, (business) impact level

slide-48
SLIDE 48

GDS @jystewart

slide-49
SLIDE 49

@jystewart

We’d quietly been building relationships and finding a different way

slide-50
SLIDE 50

@jystewart

We’d been learning to talk in the language of “risk”

slide-51
SLIDE 51

@jystewart

Working with others who had come to the same conclusions by different routes

slide-52
SLIDE 52

@jystewart

We experimented on GOV.UK, on Universal Credit, with new tech for Cabinet Office

slide-53
SLIDE 53

@jystewart

We focused on an approach that put users first

slide-54
SLIDE 54

@jystewart

We collaborated on things with names like “Security Policy Framework”

slide-55
SLIDE 55

GDS

slide-56
SLIDE 56

@jystewart

We should have done more to show worked examples

slide-57
SLIDE 57

@jystewart

By taking policies back to first principles, we make space to engage the whole team

slide-58
SLIDE 58

@jystewart

By engaging the team, we can think about security as design, not just compliance

slide-59
SLIDE 59

National Cyber Security Centre

slide-60
SLIDE 60

@jystewart

“If security doesn't work for people, it doesn't work”

  • Emma W from NCSC

https://www.ncsc.gov.uk/blog-post/cyberuk-2017-people-strongest- link

slide-61
SLIDE 61

Real change requires everyone to learn each others’ languages

slide-62
SLIDE 62

“No one is coming. It is up to us.”

slide-63
SLIDE 63

https://thenewkingmakers.com @jystewart

slide-64
SLIDE 64

GDS

slide-65
SLIDE 65

@jystewart

Multi-disciplinary teams can work with far more people

slide-66
SLIDE 66

@jystewart

The unit of delivery is the team

slide-67
SLIDE 67

@jystewart

We have to find our satisfaction in the whole job being done well

slide-68
SLIDE 68

@jystewart

The real legacy is people all over government who’ve found a different way

slide-69
SLIDE 69

Software as a public service

slide-70
SLIDE 70

Thank you

James Stewart @jystewart