The road ahead for iterative practices in Swiss government

  • Andreas Amsler

Iteration as a method is ‹safe-to-try› for government, too. If there is a conflict between government processes and iterative methods, this needs to be unmasked and fixed. 2017 I took a CAS course in Public ICT Procurement to learn more about relevant government processes, regulations and laws.

Learn more about our Service Design, UX Design and Analytics services.

When I say ‹relevant›, I mean those government processes, regulations and laws which have got relevance for drafting, procuring, building and running government digital services. And which in that respect probably are generating uncertainty, if iterative methods can be applied without violating existing processes or laws.

Why government can[not] build digital services iteratively

I wrote a thesis on the topic, and tried to condense my findings in a 20 minutes’ presentation as a PDF on speakerdeck, and as a Google-Presentation, which includes my speaker notes, too.

(Old graphic, published until 5 January 2018.)

My thesis got accepted, but I will invest some time until the end of 2017 to revise it, before it is going to be published in early 2018. I will add it to this blogpost, when it's ready.

What is your experience with iterating in government?

I am thankful for any feedback on the topic. Please get in contact with me via the following channels:

Tell us what you think