Skip to main content

Tectonic Speed of Government – PechaKucha Version

Video link is below!!    This is not my favorite screengrab, but that's what YouTube picked...

In March, I was scheduled to speak at the Code for America Summit about the “Tectonic Speed of Government,” which is my metaphor that Government change happens slowly (after the exertion of a lot of force with no visible result), but when it does happen it can be disruptive.   

Then the Pandemic hit, the conference was canceled, and… we went through a Tectonic Shift (to a remote workplace).


Disclaimer: All of the ideas expressed in this article are my personal statements and opinions, and do not reflect the opinions/statements of the City of Urbana.


In March, like many of my peers I was too busy dealing with the Shift to have time for much else. However, in April and May, I had a little more time and some new perspective so I re-wrote my presentation (cutting it in half, for the Internet) and now planned it as a video.   

One thing that I kept was the PechaKucha format. We have a PechaKucha night here in Urbana-Champaign, like many cities around the world. (The last one was just before the lockdown!) PechaKucha is a presentation format that gives the speaker 20 images for 20 seconds each, for a 6:40 presentation.  I modified the format, so originally my live speech was going to be 50 images for 50 seconds (for the 45-minute version), but for the video I went with 50 x 25, so 20:50.  I’m glad, because some editing always makes things better. There was some “filler” in the 50-slide version. 

Many hours of rehearsal and video-editing later, here it is for your viewing pleasure.  Some annotations appear below the video.

About the recording: I did three takes of the whole speech and this was the second of three. I had a timer and an outline of the speech that I could see, but only an outline – so my phrasing changed every time. This is important in PechaKucha, because sometimes you need to stretch it out (or cut on the fly) when the slides advance automatically. 

1:45 - This was the only take where I pointed to my shirt, and I got the wrong side because I was looking at the camera’s viewscreen, which was reversed! 

2:40 – This is one of three sets of three in the speech. I’m a believer in the rule that three points is the right amount of information – but sometimes I overdo it. Later I talk about the impact of CyberSecurity on three aspects, and then give my three rules on personal CyberSecurity. A screen shot from that part was even selected as the YouTube image! 

6:35 – Ironically, I had extra time while covering the Time slide! Notice how I had to drag it out at the end. 

7:20 – a Simpsons reference ( that’s always been a favorite, although I made it more direct since the original “I’m looking in your direction” would be too subtle. (I dropped it in this post, too: Seriously, though – Java upgrades are a constant hassle. 

18:00 – the “also, also” line is a Monty Python reference to the Holy Grail credits ( and no, not the llamas part. 

Final note: a warning for anyone else trying to do this in PowerPoint. Believe it or not, PowerPoint has a known defect with slide timing! (When in PowerPoint show mode, it will not accurately advance the slides on the timing: The solution I used was to render a video file from PowerPoint, which is accurate.  So that’s how you need to do it. Blecch!

Popular posts from this blog

The Tectonic Speed of Government, Part 1: Procurement

This post is my reaction to conversations about how hard it is to create change in government, and how government projects (and IT projects in particular) take so long from genesis to completion. This is part 1, about procurement; part 2 will address project implementations. PS - there was a surprise Part 3 of this series later!

Warning: what follows is an “inside baseball” discussion of government IT procurement. I’m not trying to dissuade you from reading it, but if you’re not enmeshed in this world you might want to consider reading my articles on lighter topics like organizing your electronic life, the greatness of Abbey Road, or the story behind The Room.

If you ARE enmeshed in this topic, then please don’t overlook my call to action at the end! Changing the process will take a group effort, and I’m hoping to get feedback on my scheme to create a library of reusable software specifications.

By the way, this post’s first title was “The Glacial Speed of Government” but that title i…

How To Videos: Lucity Queries with Microsoft SQL Server and Excel

What follows is not a blog, but some suggestions on using Microsoft SQL Server "Views" to query your Lucity data using Excel.   This information is intended to assist Lucity software users, and not for any nefarious purposes.

I recommend watching the videos in Full Screen view and with HD resolution.  They're not as blurry as they look on this page!!  Each of these about two minutes long, but the original actions only took 50 seconds each.  (After recording them, I decided to slow them down to make them more watchable.)
1. How to create a SQL Server "View".  The video shows how to create a new View from the core Work Order table.  (WKORDER - see the data dictionary here.)  The video first shows the simple method of creating a view with all fields, then shows the more effective method of including only needed fields, and re-labeling them with their on-screen names.

Music: "A View to a Kill" - Duran Duran

2. How to Connect to the View with ExcelWith a view …

Why the Tectonic Speed of Government?

The original name was "The Glacial Speed of Government” but that title is both cliché and inaccurate, as today it implies a faster pace than it used to. I decided that “Tectonic Speed” is more accurate because you can push very hard, but change in government shows tremendous resistance.  However, when change happens it can occur in significant outbursts - and in those moments, there is great opportunity!

Part 1Part 2  |  Part 3  | Part 4 | Wait there's a Video?!

The Tectonic Speed of Government, Part 3: It’s Never Over

Recently, I wrote two posts discussing why IT Projects take a long time: one on the Procurement Process and one about Project Implementations.  They were written during a time of three simultaneous projects, and they were therapy for me to exorcise some complaints... and make suggestions for others. From the start, I planned those as two topics – and I thought they'd finish the series.

But this third part was a surprise, and the greatest lesson I learned from those projects.
Disclaimer:All of the ideas expressed in this article are my personal statements and opinions, and do not reflect the opinions/statements of the City of Urbana.
“It ain’t over till it’s over” - Yogi Berra on baseball, not IT projects.Trick Question: When is a software project over?

Answer: Never. 

By “over” I mean the soft…

Tectonic Speed of Government, Part 2: Why do Government IT Projects Take So Long?

This is part two of my series on why government IT projects take so long. Part one complained that the Purchasing process is tough to navigate because methodically describing what you want to buy - and documenting your decision making - takes effort. That blog helped me vent some frustrations about parts of my job, although I admit that it was a little dry. (But please, this is Government Procurement.)

With part two I’m on my home turf: the process that starts with the purchase of an IT tool and ends with its everyday use by people. If the process was successful, users are doing their jobs better than they did before. (A less successful outcome that also occurs: it’s harder to do their jobs, but at least their managers have better data.) This process, which I’ll refer to as the “Implementation” or “Project,” can take months or years for any organization - let alone a government.My first section explains why government IT projects take a long time, while the other three suggest str…