Friday, 16 June, 2017

Five for Friday (16/6/17)

Another week in which technology seems the least important thing in the world. Still, I’ve got nothing else to give, so here goes.

  1. Join the DH digital communities and channels team – two great jobs going on a great team at the Department of Health.
  2. Slack is raising another $500 million — and has attracted interest from a range of big buyers like Amazon – Slack is a really interesting tool. I swing wildly from thinking it’s not really that signficiant to considering it the harbinger of a new way of doing technology within organisations. As ever the truth is somewhere in the middle. The idea of Amazon buying it does not make a huge amount of sense to me. Amazon have inroads into big enterprise IT through their web services division of course, leading the way in the infrastructure as a service bit of cloud. They don’t have much (any?) of a footprint in software as a service – tools that actual users actually use. Do they want to get into that space? I’ve no idea but surely Google would be a better fit for Slack, and it would help out with the moribund and confusing state of the G Suite’s communications tools (Hangouts seems to have stagnated for years now).
  3. Survey points to digital skills gap in civil service and Public sector struggling with cloud due to skills shortage – to both of which my response is “yes, and?”. Seems to me that we see a lot of reporting of the problem with digital skills/confidence/mindset but very few examples or ideas around how to tackle it. If you’ve ideas to share, then please do so in the Digital Skills in the Workplace group on LinkedIn.
  4. History by lawsuit: After Gawker’s demise, the “inventor of e-mail” targets Techdirt – fascinating mixture of computer history combined with out and out oddness. The man who wrote a program called EMAIL claims this means he invested the generic tool e-mail.
  5. Minimum Viable Architecture – good enough is good enough in an enterprise – nice bit of myth-busting around the supposedly special requirements of IT in a larger organisation. The word ‘enterprise’ is used to justify all sorts of crap: higher prices, costly maintenance agreements, hard to use and complicated tools. The fact is that the only difference is one of time – bigger organisations have existed longer than most small ones and thus have built up baggage around infrastructure and process. Achieving change in such organisations means trying to reduce that cruft… as James notes in his post “If enterprises are going to drive a successful digital transformation, and develop a culture that supports agile development and devops, then they need less architecture, not more of it.”

https://www.slideshare.net/RandyShoup/minimum-viable-architecture-good-enough-is-good-enough-in-a-startup

 

These have mostly all been tweeted during the week, and you can find everything I’ve found interesting and bookmarked here.

#Five for Friday (16/6/17)

Friday, 9 June, 2017

Five for Friday (9/6/17)

Not sure anything in tech world can match politics right now for interestingness, but here goes…

  1. Tandridge Council are recruiting a Technology Implementation Manager. Details here.
  2. What a digital organisation looks like – smart stuff from Janet Hughes. Answer = responsive, open and efficient.
  3. We need a Minister for Digital Government – according to Dan Thornton at the Institute for Government. Quite a bit of commentary has been around the limitation of the word ‘digital’ – though that’s largely semantics – and I would argue that even if you (wrongly) take digital to mean just tech, there’s still enough that needs fixing to make it worthwhile.
  4. “Which third are you?” – asks James Governor from Redmonk. The thirds being change agents, persuadables or heel diggers. All about your attitude to change. Every organisation has every type, and you need them all onside – or at least enough of them – to make stuff happen.
  5. Coté shares some slides from a workshop he ran in the States on how Government can go cloud native. Also see this post for further ruminations.

https://www.slideshare.net/cote/transforming-government-agencies-into-cloudnative-organization-76730434

These have mostly all been tweeted during the week, and you can find everything I’ve found interesting and bookmarked here.

#Five for Friday (9/6/17)

Friday, 2 June, 2017

Five for Friday (2/6/17)

Here’s five dollops of interestingness I’ve spotted this week:

  1. There’s a few interesting digital (and non-digital, for that matter) jobs going at London City Hall.
  2. Digital Transformation: Why Tech Alone Won’t Cut It – a useful reminder that digital and transformation are not necessarily technical terms. Human behaviour and culture are key.
  3. Where terrorists go to chat – thoughtful stuff from Hadley Beeman on security, encryption and the role of government
  4. Not even wrong – ways to dismiss technology – nice long read on technology adoption and why predictions around what will be the next big thing are often (not even) wrong
  5. Lessons from piloting the London Office of Data Analytics – Eddie Copeland talks about data issues at scale:

These have mostly all been tweeted during the week, and you can find everything I’ve found interesting and bookmarked here.

#Five for Friday (2/6/17)

Tuesday, 30 May, 2017

Publishing stuff

One of the things I love about the internet most is the fact that it puts the power to publish into the hands of pretty much anybody. There are many ways of doing it these days, whether by using a tool like WordPress like I do here – which can be pretty complicated – or perhaps by using Medium, which continues to interest and confuse me in equal measure.

So I was quite excited to come across a really simple thing called publishthis.email which allows anyone to create public webpages by just sending an email.

I immediately got in touch with my friend Lloyd about this, knowing that he shares my enthusiasm for publishing stuff, and also how he really enjoyed using Posterous which did something similar, albeit in a slightly more complicated fashion. Posterous was bought and shut down by Twitter a few years ago.

publishthis.email works in a ridiculously simple fashion. All you do is send an email to page@publishthis.email and a web page is created for you – the link to which sent by return to you. Any formatting in your email is preserved and any pictures you include are uploaded and added to your page.

Here’s my rather boring first effort at a page. Lloyd’s is a little more exciting.

And… that’s it. There’s nothing more to it and it really is that simple. Oh, except for collections. When you send your email, if you add a + and the name of a collection (basically a group of pages) after page and before the @ in the email address (so, for example, send to page+davescollection@publishthis.email) a dynamic list of those pages is then created, with its own URL, giving you a very rudimentary blog.

Here’s my rather boring first effort at a collection.

There’s loads missing, like human readable URLs, navigation links between pages and so forth. However, whether they come or not, publishthis.email is potentially really interesting as a way of very quickly getting text and images onto the web to share with others.

It’d be good to hear what folk think about tools like this, and what uses they could be put to.

#Publishing stuff

Friday, 26 May, 2017

Five for Friday (26/5/17)

Five more nourishing morsels I’ve spotted this week:

  1. LocalGovCamp is back this September in Bristol. Find out more and sign up for the ticket lottery here.
  2. The Disappearing Computer – Walt Mossberg’s last column is a great read on the future of computing
  3. Put employee experience at the heart of the digital workplace – interesting presentation on deploying communication and collaboration technology in your workplace
  4. Digital skills in the workplace – I’ve decided to give this rather dormant LinkedIn group a kick to see if there’s any life in it. If you’re interested in digital skills and confidence at your organisation, do jump in.
  5. I’ve been thoroughly enjoying HBO’s Silicon Valley recently. If you have Sky Atlantic, you can binge on it. Here’s the first season trailer to whet your appetite:

These have mostly all been tweeted during the week, and you can find everything I’ve found interesting and bookmarked here.

#Five for Friday (26/5/17)

Friday, 19 May, 2017

Five for Friday (19/5/17)

Five more nuggets of interest I’ve spotted this week:

  1. Jessica Lessin built a business to prove information doesn’t have to be free – great podcast about the different models emerging for journalism online. The Information is a great site, by the way (I’m a subscriber).
  2. The Department for Health’s fantastic digital team are hiring a Content Editor. You have until 28th May 2017 to apply.
  3. The Weird Thing About Today’s Internet – fantastic piece looking at the last ten years of the web.
  4. Making local authority data work for you – useful looking resource on open data delivered by the ODI and LGA in partnership (I think).
  5. James Governor summarises Microsoft’s Build conference for us in three minutes:

These have all been tweeted during the week, and you can find everything I’ve found interesting and bookmarked here.

#Five for Friday (19/5/17)

Friday, 12 May, 2017

Five for Friday

Am going to try and get a quick link roundup post out every Friday if I can, pointing out some interesting stuff I’ve seen during the week.

  1. Management is not about asking people to do stuff – really interesting article on being a better manager. Something that’s really been brought home to me in the last few years is that being successful in stuff like digital transformation or modernising IT relies on your ability to manage well as much as being some kind of epic visionary.
  2. Enterprise-wide Agility: Doing versus Being – I love the “doing versus being” idea and want to explore it more in a future post here.
  3. Council frontline staff lack digital skills competence – not just frontline staff I’d say and a lack of basic understanding of the role of technology and digital operating models is holding back transformation work in lots of organisations, no matter what the sector. I’m tempted to dust down my digital passport work of yesteryear to see if it could be refreshed to help fill this gap.
  4. Head of Technology Services – I’m moving on from my interim job at Horsham soon, and this is the advert for my permanent replacement. It’s a great job.
  5. Mark Thompson on platforms and government:

https://vimeo.com/216550724

These have all been tweeted during the week, and you can find everything I’ve found interesting and bookmarked here.

#Five for Friday

Friday, 5 May, 2017

Six principles for good local government technology

As part of the work putting together a Technology Strategy (think IT + digital) for my current employer, I came up with six principles of good technology. The idea is that each of these principles must be met by any piece of technology the organisation wishes to buy or to build.

(The purpose of the strategy is to develop what was a fairly traditional IT team into a rebranded ‘Technology Services’ team; and to bring them out of ‘maintenance mode’ and into more proactive space, where technology can be used to drive improvement and efficiency in the way that services are delivered. To my mind, IT in this sense cannot be worked around or ignored in a JFDI sense if you’re serious about transformation in your organisation – it must be tackled head on, otherwise you’re doomed to failure. More on this in a future post.)

Anyway, here are the principles, in case they are useful.

Cloud native – to ensure all the systems we use are designed for the internet age

Core to the Technology Strategy is for the Council to become a ‘cloud native’ organisation, making use of commoditised utility computing wherever possible. A district council has somewhat limited resources, and those resources are best spent where we can add most value, and to my mind, that isn’t in upgrading firmware or patching servers.

Our preferences when investing in systems is as follows:

  • Software as a Service – where possible, we prefer to use a SaaS solution to minimise the responsibility we have to support and maintain a system’s infrastructure
  • Platform as a Service – for bespoke workflows and requirements, we develop using a cloud-hosted, capability-based, off the shelf PaaS
  • Infrastructure as a Service – where the market is yet to deliver an acceptable SaaS solution and the requirement is too complex to deliver via PaaS, then a more traditional application will be hosted within a public cloud environment such as Amazon Web Services or Microsoft Azure

Mobile ready – to ensure all the systems we use can be accessed anywhere, from any device

Legacy software was built for desktop based computing and thus doesn’t work well with the new style of devices that have emerged in the last decade.

We want staff to be able to make use of easy to use devices such as smartphones and tablets while working away from the office.

Any software we purchase, renew or develop must be enabled for mobile working out of the box, without the requirement for middleware or extra investment in specialist hardware.

Interoperable – to ensure the data our systems use is easily shared between people and applications

Legacy software makes exchanging data between systems difficult and expensive.

Cloud native systems and software offer freely accessible and publicly document application programming interfaces (APIs) and web services, which can be used to link systems together very simply, often with very limited programming required and use of ‘drag and drop’ style interfaces.

We will insist that all technology we invest in offers this ability to share data across systems.

Flexible – to ensure we make good use of shared platforms and capabilities across our services

Many of the systems we use are made up of the same common capabilities – booking , reporting, managing cases, payments, assessments and so forth – however they are trapped in service specific silos.

We wish to tackle this inflexibility by investing in flexible, generic capabilities that give us the building blocks to design our services, and the systems they run on, in the way we want to, and not be beholden to system suppliers.

Enabling customers – to ensure all the technology we deploy helps our customers enjoy a consistent journey across our services

We want to put our customers at the centre of the way we do things. This means two things:

  1. Any system we purchase or develop must have online self service as a foundational part of its design, to ensure as many as possible choose to take this option
  2. Service and system design should be based upon evidence generated through user research and take a customer-centric approach

Proportionately secure – to ensure that the Council’s and our customer’s data is as safe as it needs to be to enable us to deliver our best work

Information security is extremely important and we must be vigilant in looking after the data we hold, particularly that which belongs to our customers.

However, with our move to internet based technology, we can follow best practice guidance from central government to classify our information assets to enable us to work flexibly when it is appropriate to do so.

We want to encourage colleagues to think for themselves around information security, rather than relying on one size fits all policies that often are not adhered to.

#Six principles for good local government technology

Tuesday, 25 October, 2016

Toad

Maybe tomorrow I think I’ll settle down

Why should I let the toad work
Squat on my life?

It’s hard when thinking about the things we do to scratch out a living not to recall Larkin’s words about the manner in which work can dominate our lives.

I’ve been thinking about work a lot in the last few months, to the point where I’m making a change in what I do and how I go about it. This Friday will be my last working at Adur & Worthing, and from the following Monday onwards, I will be shifting up the road to Horsham District Council.

The main reason for the change really is a temperamental one, I guess. I’m moving from a permament job to contracting. At Horsham I’ll be an interim with a defined period of time to work in. Having a go at a permament role has been an interesting experience, but it has become clear to me, and I suspect to one or two colleagues, that I am a sprinter rather than a marathon runner. I do my best work in short bursts, before momentum runs out and boredom sets in.

The other interesting thing to me is the new role itself – Head of Technology Services. That might sound to you like a fancy way of saying IT Manager, and to an extent you’re right. Somehow I’ve pivoted from being someone who knows a little bit about how the web works to being the bloke in charge of the infrastructure, the applications, the data, the security, and yes, the web. I’m not quite sure how this happened, but I’m kind of pleased it has.

My role going into Horsham is to put a technology strategy together, get the programme of work lined up, and to ensure the structure of the team and the roles within it are the right ones for the future. You’ll notice that the ‘D’ word, digital, hasn’t been mentioned yet. It might be a semantical thing, but I’m trying to avoid it this time around.

There’s a thing about being able to talk about digital ways of doing things, without people automatically assuming that it is the digital team’s job to do it. It isn’t always, and I think having a team and a strategy that isn’t called digital means that one can talk about digital in a much more open way, without it being seen as a land grab, or a takeover by one particular group in an organisation.

Anyway, I’m looking forward to the challenge and getting stuck in at Horsham. And then in six or so month’s time, I’ll be moving on again.

So the answer I’ve found to the conundrum of work, I think, lies in words from another of Larkin’s poems: peculiarly for him (and perhaps for me to choose them) amongst his most uplifting:

Begin afresh, afresh, afresh.

#Maybe tomorrow I think I’ll settle down

Wednesday, 27 April, 2016

What I use 2016 edition

Here’s an update on the kit and software I’m using on a daily basis, just in case it’s of use.

My main computer is an 11” Macbook Air.

It has the i7 processor and 8gb of RAM and is the best computer I’ve ever used. I use it for home and at work, thanks to our Councils’ move to cloud based services.

I do have a work laptop, which I turn to when I need to access things like our HR and finance systems; and if I need to do some printing. It’s a Dell somethingorother.

In terms of software:

  • Chrome is running the whole time, hooked into my work Google account, where I access Gmail, Google Drive, my calendar and so on. Pretty much all the productivity work I do for my job is in Google’s suite of apps.
  • Trello and Tweetdeck are usually open too
  • Safari is often open, which hooks into my personal Google account
  • I have two other email addresses that I check regularly my desktop (I know…) which I host with Fastmail and pipe into Apple’s Mail app
  • Slack is usually open. I’m a member of about five teams that I access regularly via the desktop app
  • I use Reeder to keep up to date with RSS feeds (old skool, right?) – I use Feedly as the web service to keep it all in sync
  • I bookmark stuff in Pinboard, which then autoposts into Twitter for me via Zapier. Zapier also zaps bookmarked links into Pocket for me, so I can read them later at my leisure
  • Following a chat with Matt Jukes, I do most of my writing in Ulysses, whether taking notes, drafting blog posts or my email newsletter
  • Occasionally I’ll use Transmit for FTP, I have Microsoft Office installed but very rarely use it, do the odd mind map in MindnodePro, draw something with Omnigraffle, have a chat with someone in Skype, listen to music on Spotify, or screenshot something with Skitch.
  • I still have loads of different tools installed for editing text, most of which I don’t use very often or at all (Byword, Scrivener, BBedit, Atom, Writeroom, MarsEdit, probably others)
  • Utilities wise, I use Alfred as a Spotlight replacement and TextExpander is usually running
  • I store pretty much all my files in Dropbox
  • My blog uses WordPress.com and I pay to use my own domain and to not have adverts
  • My newsletter uses Mailchimp’s free tier

My phone is an iPhone 6, space grey with 64gb storage.

On my home screen I have the following things:

  • On the top row: photos; camera; app store; settings
  • Next row down: A folder with emails apps (Mail, Fastmail, Outlook, Inbox and CloudMagic – each app has a different email account feeding into it. I have too many email accounts); Natwest; Music; Google Maps
  • Next row: Spotify; Simplenote (for todo lists and quick notes, rather than ‘writing’); Overcast (easily the best podcast app); a folder with ‘reading’ apps (Medium, Buzzfeed, Nuzzle, Yahoo News Digest, Pushpin (an app for Pinboard), Kindle, NextDraft, iBooks)
  • Next row: Trello; HulloMail (provides a visual voicemail like tool, plus emails voicemail messages as MP3 files and transcribes them too); Wikipedia; Reeder (mobile version of the deskptop RSS reading app – again syncs with Feedly)
  • Next row: Slack; Pocket; folder with messaging apps (WhatsApp, Facebook Messenger, Skype, iMessage); Safari
  • Bottom row: Facebook; LinkedIn; Ulysses – for bashing text in during idle moments; Twitter
  • Dock: Phone; Hangouts; Google Calendar; Gmail – the last three are all logged into my work Google account

The layout of apps regularly changes – I try and keep my most regularly used apps towards the right hand bottom corner – easily in thumb reach.

The second screen has other stuff on it, but I don’t use them on a regular basis really.

The main change over the last year or so is that Evernote has dropped out of this completely. It’s still there, but I hardly use it anymore – even to revisit notes previously made (which rather begs the question why I bothered making them in the first place).

Hope this has been useful and/or interesting!

#What I use 2016 edition

Monday, 25 April, 2016

Monday, 11 April, 2016

Anti-patterns of behaviour in big organisations

Michael Coté has written an excellent post describing seven anti-patterns of behaviour in big organisations.

Number six is a particularly egregious crime, in my view:

Pay people to ignore them — BigCo’s love hiring new employees, paying them well, and then rarely listening to them. Instead, you hire outsiders and consultants who say similar things, but are listened to. In fact, the first task of any good management consultant team is to go interview all those bright, but ignored, employees you have and ask them what they’d do. The lesson is to track how many ideas come internally vs. externally and, rather than just blame your people for low internal idea generation, ask yourself if you’re just not listening.

Go read the whole lot – it’s good stuff.

#Anti-patterns of behaviour in big organisations

Sunday, 10 April, 2016

Friday, 19 February, 2016

How much does your technology define what you do?

A fairly quick thought this, but one than keeps occurring to me. It feels like a self evident truth that the technology an organisation uses should follow that organisation’s purpose, and not the other way around, but I wonder how often that is actually the case?

I’d argue that for many organisations, with legacy infrastructure and applications that have been in use for many years, technology is defining the way they run.

This is because the technology locks in ways of working, the design of a service, perhaps even the entire operating model of the organisation.

I’ve been involved in many projects in the past where radical redesign of services was scuppered because the technology wasn’t flexible enough to deliver the new vision.

So while it is vital to rethink how services are delivered and how the organisation works, sometimes you need to fix the technology first to enable that change to happen.

#How much does your technology define what you do?

Sunday, 7 February, 2016

Interesting publications on design, technology and change for ‘good’

I’m pulling together a list of interesting, thought-provoking reading on how design, technology and change (the three things that, for me, define ‘digital’) can help organisations that work in the community, voluntary, charity, non-profit, social enterprise type space.

Is there a less clumsy way of describing these organisations? I think under the last Labour government, ‘the third sector’ was adopted, but that seems to be used less these days. Have heard ‘civic sector’ and ‘civil society’ bandied around, but don’t know how well established those terms are. Any help on that one?

Anyway, I’ve found a few I will point to here:

Any others? Leave a note in the comments or on Twitter and I will add them.

#Interesting publications on design, technology and change for ‘good’

Wednesday, 18 November, 2015

Wednesday, 28 October, 2015

Rehosting podcasts

Last year I recorded a bunch of podcasts that people seemed to enjoy. They were hosted on a service that needed paying for, and when I stopped paying, they dropped off the internet! Oh no!

So, have rehosted them on Soundcloud, which is free. I’ll go back over the original posts and update them when I get a chance, but in the meantime you can find them all at https://soundcloud.com/davebriggs, or you can use the embedded player below.

[soundcloud url=”https://api.soundcloud.com/users/13017131″ params=”color=ff5500&auto_play=false&hide_related=false&show_comments=true&show_user=true&show_reposts=false” width=”100%” height=”450″ iframe=”true” /]

#Rehosting podcasts

Sunday, 20 September, 2015

Eleven years a blogger

15595978411_3d22af62ac_k

According to the archive on this site, I’ve been writing this blog for eleven years today – since September 2004.

This is the 2,646th post and there have been 4,263 comments on them over the years.

Lots has changed in that time, personally and professionally. It’s fair to say that I wouldn’t be where I am now without having started it.

It’s done three things, I think:

  • helped build my profile over the years, creating all sorts of opportunities
  • helped me develop my ideas, from the half baked to the barely lukewarm
  • helped me build my network of friends and collaborators

There’s a bunch of other bits too, in that I’m sure I must be a better writer now than I was when I started, and eleven years of fiddling with WordPress have taught me a load about technical stuff (mostly to leave well alone).

I’m so grateful for the folk who read this blog and respond, for the occasional kind words of encouragement I get.

On the very odd occasion that folk ask me for advice on getting on the world of digital and/or government, I almost always suggest people start blogging.

I’m hoping I’ll be able to continue for at least another eleven years.

#Eleven years a blogger

Wednesday, 2 September, 2015

What I’m talking about when I’m talking about government as a platform

platorm

So, a little while ago I posted about government as a platform, and mentioned three main components that matter, particularly to us at Adur and Worthing with our approach.

However, I’ve been involved in various conversations where I’ve been confused about how other people define platform thinking, which I think goes to the root of the lot of the issues around the wider digital agenda – issues brought to prominence recently in the debate following several key folk from GDS deciding to leave recently.

For me, I defer to Mark Thompson‘s thinking on a lot of this stuff, which Sean Tubbs neatly summarised with the benefit of some of his practical experience.

This piece from Thompson is required reading on the two different approaches to platform thinking, and which he – and I, as it happens – think is the right one. He characterises GDS as a ‘web agency’ – which I think is a little harsh, but gets to the heart of the debate around whether digital is more front end design than fixing the back office line-of-business IT stack (hint: a great website is lovely, but real change can’t happen until the legacy is fixed, which itself can’t be achieved without thinking more widely about how your organisation works).

Effectively the proposition is this: that digital describes not a set of specific technologies or even approaches to technology, but rather the age in which we are currently living, and the appropriate operating models for that age. It also describes the way in which an ever increasing number of our customers want to interact with organisations.

Thus digital, and the strategy for delivering on the digital opportunity that is government as a platform, is not around technology but rather rethinking how organisations work.

Technology is a convenient way to practically start delivering on government as a platform, but it is very much the start of the process. This is slightly unfortunate as it does provide the opportunity for people to put digital, and platforms, into the box marked IT project, which is a massive mistake. Platform technology without a platform operating model  will never deliver on the opportunity.

So, the key elements for me when it comes to platform thinking are:

  • capabilities not systems – instead of thinking about solving problems with a single ‘system’ (think of that word in the widest sense, not just as in an IT system) we break down requirements into generic capabilities, which can then be put together, building block style, to create the most appropriate solution to the problem at the time
  • making use of commoditised, utility-like computing – in government, we do not need to be using bespoke technology, but instead in many instances can use what the market can provide, at a much lower cost than traditional technology – which then frees up resource for the front line (which is the key bit)
  • solutions for now that don’t limit us in future – capabilities must be designed in such a way that they are not ‘hard coded’ (tech metaphor, sorry) for the way they run now, but so they can be flexible to meet future needs which may be very different
  • create and consume – the platform must be put together in such a way that both we and other organisations can make use of its capabilities, as both creators (building our own apps) and consumers (making use of what others have done)
  • disintermediation – or getting rid of the middle men. Catherine Howe spoke a lot about this a few years ago – showing her talent for prescience yet again. We’re only now really starting to see the effects of this with the likes of Uber and Airbnb cutting out bureaucracy and using the internet to directly connect people with needs with those who can meet those needs. These are true digital business models, not just slapping nicely designed front end lipstick onto legacy pigs.

This is what has been so frustrating about some recent discussions – rather than focusing on the big picture of rethinking operating models, folk go straight into IT mode and start discussing which booking system is best, or who has the payment engine everyone should be using. The concept of capabilities is grasped, but only at the level of technology, not any further.

So, at Adur and Worthing, we are at the very beginning of delivery of platform thinking and operating models. We starting, as is customary, within the domain of technology – but we are not limiting ourselves to that, and are constantly challenging our thinking to ensure we don’t continue to work in non-digital age ways outside of tech.

With technology, we build or buy capabilities that can then be used and re-used many times to deliver appropriate solutions to needs, both by us and by others, and we are also able to consume on the platform too – so if someone else has something neat we’d like to use, we can slot it into our systems. This way of working can happen with other assets, as well as tech, though – people, knowledge, skills, buildings, open spaces, vehicles – anything.

The key is to construct our organisation in such a way that all our assets are effectively capabilities that can be used in different ways by different people – and indeed so that we can bring in assets from elsewhere on the ‘platform’. Often this this supported by digital technology, but that isn’t the starting point, nor the outcome.

For example, I’ve recently been thinking about how ‘people as a platform’ might work in the local area. How can we make the most of the people who work at the Council – and their expertise and skills – as well as those who don’t work here but nonetheless might help us make things happen?

The capability here might be an effective time banking system, enabling people and organisations to trade knowledge, skills, time spent etc without the need for money to change hands  – borrowing in expertise as needed, paid for via hours donated to the wider system previously, without the need for costly administration to link people up, make the transactions and so forth.

(On a side note, how exciting would it be for such a time-trading system to work via some kind of blockchain technology, as Lloyd talks about in this post?)

Hopefully this example is useful – a non technology asset being shared across a system, (re-)usable in a number of different contexts, supported by a digital platform, built upon off-the shelf utility technology, which cuts out the need for central bureaucracy. That’s where we need to be with government as a platform.

So, to recap: digital is not about technology, and government as a platform is not about IT. It is instead a way of rethinking the operating model of an organisation to meet the current and future needs of its customers, in the digital age. The technology is an important enabler, but it is the means rather than the end.

It is not about fixing on a single solution for everything, but creating an ecosystem of innovation, where different solutions can compete to deliver the right capability needed by the people using the platform.

It is not about making everyone use computers to do everything, but instead is about making use of modern, internet enabled tech to run a sufficiently minimal back office that enables us to maintain, and potentially grow, front line delivery of what customers need (see Buurtzorg – and see if you can spot me and Mary McKenna in that video).

Hoping to have a chat about this at LocalGovCamp. Come along – it’ll be a blast.

#What I’m talking about when I’m talking about government as a platform

Tuesday, 1 September, 2015

Post-post-bureaucrat

I’ve always rather liked the title of Steph’s blog and how he gives us occasional updates on how his life outside of the government machine is going. His post-bureaucrat life seems to be going really well.

I left government as a direct employee back in 2008 from which point on I was self employed, with a period working for Learning Pool as a proper employee for 18 months in the middle.

Now, I find myself employed directly by government again. Since April I was the interim Head of Digital and Design at Adur and Worthing, but a couple of weeks ago I was interviewed for the permanent role, and I got it.

So now I have gone from being post-bureaucrat to post-post-bureaucrat.

How does it feel? Here’s a few things that have occurred to me.

1) It’s great not having to sell stuff. Over the last few years I’ve had all sorts of ideas on how to do interesting stuff, to solve tricky problems. I didn’t get to test all of them though, because first I had to sell them.

Now I have this job, I’m in a position where I can just get on and do stuff, to test out some of the thinking I’ve been doing and see if it works in the real world.

2) This is exhausting. Part of the reason why I don’t blog much at the moment and am nowhere near as active on Twitter etc is that I just don’t have the energy. There is so much to be done, and having this role, and being permanent in this one organisation, has given me a sense of responsibility for getting stuff done, which means I am working as hard as I can, all the time.

3) My attitude to sharing has changed. Another reason why I’m not as active socially online as I was before is that my feelings towards it have changed. Social media was really all I had before to market myself, and I don’t have the need to sell any more.

It’s more than that though. There’s something about working at a local authority that affects your sense of loyalty. I haven’t lost my belief that being open and sharing ideas and work with others is a fundamentally good thing. It’s just that, with finite time, energy and attention, I’m more likely to do something that’s on my todo list at work.

I actually think that I need to rebalance this a little, as there is clear benefit for work if I am engaged online, finding out what is going on elsewhere and flying the flag for our approach.

4) I’m only just starting to calm down. It is a different pace when you’re in something for the long haul rather than a short term contract. Since I got here I think it is fair to say I was working at freelance pace, getting involved in everything I could, chucking out ideas, writing papers, making things happen.

It’s important to keep up a quick pace, I think, but I’m starting to learn the importance of pacing myself, choosing my battles a bit more carefully, learning when to step back and let others take the lead on some things.

5) LocalGovCamp will be interesting. Am really looking forward to this year’s event, especially after missing CommsCamp earlier in the year. This will be my first LocalGovCamp as a local government employee, so it will be a special one, I think.

I’m hoping to run a session with others on the topic of government as a platform and also to discussions about LocalGovDigital, which I feel now I can take a full part in, seeing as I’m now a paid up member of the club.

#Post-post-bureaucrat