Simplicity Must Permeate #gov20 Efforts

Simplicity is not the Hallmark of Government, Yet...

Simplicity is not the Hallmark of Government, Yet...

The fine folks over at the Telegraph continue to have great mashups based upon the UK Gov’s open data work.  This image made me laugh a bit.  It shows the overly complex nature of HMG and one is left to wonder why.

I am not as cynical as Gerry McGovern over at Giraffe Forum, but his post on bureaucracy and complexity does give some insight into, at least, the historical reasons such complexity existed.  In many parts of the world the overt corruption that used to drive such complexity has gone (although I am fully aware that such detrimental practices continue to exist in many parts of the world).  But the lack of the overt corruption has resulted in an even more difficult set of challenges in many cases.

When corruption was actively present, it was obvious to those involved why the complexity existed.  As it was eradicated, and as civil servants took over who had no need for it, the positioning became difficult to move.  You see, these civil servants aren’t corrupt, are driven by mission and therefore, defend their organizations as protectors of that mission.  They see attacks on it as thwarting objectively good outcomes and fight against the threat.  And when folks mention that corruption may result, or indeed may have been the cause of the complexity, they resist with righteous indignation, because, in fact, they are not engaged in it.  Therefore they defend the complexity as part of the mission, since they cannot buy into the argument that the structure inculcates bad things, in their mind, it does not.

So, we need to be careful what arguments we use to advocate for governmental reform.  Instead of labeling civil servants as corrupt protectors of a corrupt system, which is not true, we need to take a different tack.

This is where Gerry has it right on.  And it is incredibly prescient given the industrial shift right now to the cloud.  He argues eloquently that:

Bad complexity creates dependence. Good complexity creates independence. One of the things the Web reflects is a movement away from the production of products to the delivery of services. In a world of production the thing itself often dominates, but in a world of service the satisfaction of the customer dominates. In other words, in a service-driven world, the measure of success is not what you have produced, but rather how satisfied your customer is.

As I engage with customers in Government around cloud topics this statement rings very true.  Not just for us as managers of online services, but to them as managers of government services.  Instead of creating a dependent culture that protects a franchise, we need to make sure that we enable our governments to create unbelievably happy and satisfied customers (a.k.a. citizens).  The shift is vital.  And as some centralized ICT bodies look to provide cloud services for their own Ministries, they need to make the shift as well.  Their customers (internal) must be unbelievably happy with the solutions they are providing.  They must shift from holding a monopoly to holding a franchise based upon the satisfaction of their customers.

As we each, industry and government, make the mind shift to the cloud, the strategic imperative is obvious.  Change your organization structure to reflect the simplicity that your customers demand to be satsified.

Related posts:

The following two tabs change content below.
Matt Miszewski has been a leader of incredible teams, that accomplished unbelievable goals - together. From rebuilding an enterprise technology strategy from the ground up as Chief Information Officer of the State of Wisconsin to driving a struggling global sales and marketing team to live beyond their potential and helping take their stock from $45/sh to over $110/sh, I have been honored to take on huge challenges and beat them by building collaborative and high performing teams. I was proud to be a regular speaker on Digital Realty's earnings call each quarter and being able to brief and advise the Board of Directors each quarter. Focusing on our shareholders needs while coupling that focus with the needs of our top customers was the combination the street was searching for and our increase in equity value proves the effort worthwhile. Our focus on total leasing costs, net present value of long term leases, closing the gap on cash performance and elimination of stagnant inventory helped to drive a stalled stock. Most proud of standing up a revenue engine that will be used for decades including a renewed global salesforce, inside sales expertise, demand generation focus, new global Partners and Alliances program, sales operations team and a heightened focus on connecting lead development to sales outcomes (including a new social marketing program, AR/PR, digital presence, brand identity refresh, SEO/SEM and a regular campaigning process). Combining decades of technology leadership with this commercial success creates an incredible package to unleash revenue and hack growth for companies from any industry out there.

3 Responses to “Simplicity Must Permeate #gov20 Efforts”

  1. Brad says:

    Interesting report card on Gershon Review of Australian Govt IT lansdcape and progress made (or not) two years down the track at

  2. Ben Tremblay says:

    Thanks so much for the image! Creates a certain context, no? ;-)

    The way I approached the problematic: what’s the link? what’s common ground? what’s salient in all cases?
    I wish I could say “and then it came to me” but it took *blush* decades. After years of banging around (MIL-SPEC tech_docs for avionics R&D helped some, in one area. And studying cog-psych helped too, in another area.) a whole flurry of factors came together.

    We made decisions. That’s not a simple process, but it’s a finite set of factors.

    “If it doesn’t really matter, then it’s /just/ news.”


Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>