innovation

How to be an everyday innovator

PlugsAlongside watching James Graham Gardner’s book on innovation develop online, I was reminded recently about the concept of ‘everyday innovation’ – making innovation something that we all do in our day jobs, rather than something mystical and abstract which is done by pointy-heads in research labs (and alternatively, as more than something as meaninglessly fluffy as a bit of random brainstorming).

In as much as the stuff my team does is ‘innovative’ in a low-key, process-oriented kind of way, I thought I’d describe how we go about it. There’s really not a great deal to it.

1. Gather stuff

Read lots about the work and experiences of people in similar fields to you (for me, government webbies), parallel fields (government non-webbies; webbies outside of government; supplier blogs; technology magazines) and totally different fields (random New York bloggers; lifehackers; science bloggers).

Use tools like Delicious, Instapaper and starred items/favourites in Twitter and Google Reader to keep track of interesting ideas, technologies and individuals. For example, I tag interesting WordPress plug-ins, themes, projects and people so I can find them when I need them.

Go to events (like UK GovWeb Barcamp, TeaCamp, gov 2.0 conferences) and make time to talk to people who work in interesting fields, even if there’s not an immediate project on the table to work on. My first professional WordPress project, the commentable version of Innovation Nation, came out of a chance coffee with Glyn from Open Rights Group about their use of the tool. Of course, there’s a small risk of developing a reputation as a time-waster here, so be up front about your interest and whether you’re just interested or want specific help.

Play (briefly) with new tools you come across. Get a sense of whether they’re useful yet, whether they’re good value and how they might be used. Most tend to be free, after all, so try them for 10 minutes and see what you get out of them.

Bottom line: have plenty of links, tools and contacts floating around ready to use.

2. Connect things together in a new way

Take something you’ve gathered – maybe a tool, a contact or an approach – and see how it would fit into one of the projects that lands on your desk:

Build in analytics and measures to help you track the success or otherwise of the new approach – Google Analytics, Bit.ly stats, or some manual work to benchmark before and after mentions/downloads/perceptions and feedback from the people involved. When you’re innovating, it’s not just about the output – whether the process itself worked is a valuable learning too.

Think about the risks involved too and what you can do about them. What if it doesn’t work? (Fall back to the traditional way of doing it). What if we get overwhelmed with feedback? (Great problem to have! Anyway, in that unlikely event, there are people who can help) But it’s not accessible! (Do your best, and have good, accessible alternative content in place. If it takes off and you start using the approach regularly, you can make it more fully accessible in due course).

Bottom line: take a real world project, try doing it with a new tool or technique. See if it works better or worse than the normal way. Have answers to people who ask you about the risks involved.

3. Share it widely

On the face of it, this looks like the hardest part, in that projects that don’t work or seem risky are potential bad news stories that won’t do much for your credibility. Personally, I’ve hardly ever encountered resistance to talking about the things we’ve tried or negativity when I’ve done so, though to be honest I usually try to couch the less successful results in context of some positives too. Being human, I sometimes don’t bother writing – even though I should – about the most dismal failures. But without talking about your approach and its results, I’d argue you’re not really innovating – to do that, you have to provide something others can see, learn from and build on.

Blog and tweet about it. Take screenshots and present them as warts-and-all case studies at events. Volunteer to run seminars internally and externally to share your learnings. If you can, release what you’ve done in a form and with a licence others can re-use – especially if it’s code or a methodology. Sure, it takes time, but not only will others get something, you’ll benefit from the feedback and improvements people suggest.

Bottom line: make an effort to communicate what you did, how, and what you learned. Be frank and open, but above all, be shameless.

Steph works in digital communications in central government and blogs at http://blog.helpfultechnology.com

Photo credit: Eisenrah

Full time at the Pool

Learning Pool

2010 sees the start of a new adventure for me, as I leave the world of freelancing behind and start full time with Learning Pool – who I have been working for on a part time basis for the last six months of 2009.

I’m delighted for a number of reasons. One is the opportunity to help an established company move in new directions – more on that in a bit. Being part of something bigger is also going to really make a difference to the way I work – I’m going to have the backing of a big team of people: developers, designers, a customer support team, people who can actually manage projects properly. Anyone that knows me will appreciate what a positive thing this is!

The other key thing that Learning Pool offered me was a great working relationship with a huge number of local authorities in the UK who already have a Learning Pool product or service. My background and interest has always been more in local government and I am really excited to getting to grips with the issues facing the sector and coming up with some interesting solutions.

In terms of what it is that I am actually going to be doing, well, it’s going to pretty much be an extension of what I have been working on for the last 18 months; and indeed what I have been writing about for longer than that. Learning Pool has a great reputation at providing collaborative and social learning technology and I think there is more to be done to help councils, and other public sector organisations to become true learning organisations.

This means making use of technology like eLearning, but also the wider use of web 2.0 within the organisation – stuff like I mentioned here. There’s a lot in this, I think, mixing up culture change with innovation and knowledge management. I’m developing a model which tries to put it into some kind of context for public services, identifying:

  • Drivers: efficiency and improvement
  • Enablers: innovation and collaboration
  • Domains: culture and technology

The drivers explain what the high level thing is that needs to be achieved: in other words, doing better with less. The enablers are the things that will help this happen: a proper way of encouraging and managing innovation in the organisation, and to encourage and adopt more collaborative behaviour. The domains are where this stuff happens: getting tech that works is important, but more so is culture – both of these things must be right to ensure those enablers happen effectively.

So this isn’t (just) about tools. I’m as interested in how you can get organisations working collaboratively and innovatively as much as I am in deploying wikis or installing WordPress. In fact, I’m most interested in combining the two – here’s the tools, and here’s how to get people using them. Or, to try and put it yet another way: blogs and wikis and all that stuff is very nice, but what does it mean to a service manager?

Anyway, there is plenty more thinking to be done. I’ll still be blogging it all here at DavePress the blog, even if DavePress the business is no longer around. If you want to chat about any of this stuff and how I, and Learning Pool, can help – you know where I am.

Being up to date

James Gardner has a good post on staying up to date. His point is that if you don’t bother to follow the latest developments – which might mean doing so in your own, not work, time – then you’re going to be left behind:

2010 is going to be a performance – not an experience – competition. That’s why I said the other day that I think people who are connected are going to get all the rewards this year. It’s going to be about making things happen, and that means you need an in-between.

‘In-between’ is James’ term for the time spent doing kind-of worky stuff at home. That might be reading work related books, or blogs for example. It could be tinkering with stuff – or it could even be just thinking.

This resonates with me. When I had a proper job in local government, I’d do my job, then get home and spend at least a couple of hours a night reading, scanning the web for new, interesting stuff and blogging about it. I’d play with technology, trying things out – most of which didn’t work, but some things did.

When talking about using the web as a tool to improve government, a response is often that people don’t have time to engage with all the content that is online. I usually make up something conciliatory as a response, that perhaps if something is useful, then you find time – or that you replace less productive activity with the new ways of working.

But the brutal truth is that if you don’t find the time in your schedule, which may or may not be when you are at home, or perhaps on the train, or whenever, then there is a chance you’ll be left behind. Someone will be doing it, and they will know stuff you don’t.

This could well end up being a problem for you.

Jakob Neilson on intranets

Jakob Neilson has some good stuff in his yearly roundup of intranet trends:

Intranet design is maturing and reaping the rewards of continuous quality improvement for traditional features, while embracing new trends like mobile access, emergency preparedness, and user/employee-contributed content.

Ideas of enterprise 2.0 are leaking into intranet design, and quite right too.

As per this post, I’m focusing a lot of my attention this year on what goes on within organisations. I dare say that few councils and other government organisations have interactive – and mobile – intranets as discussed by Nielson.

I want to explore what technology people are using and what the barriers are to adoption – and then think about what the solutions might look like.

I’m on the lookout for stories about collaboration and innovation in this space within public services – like the stuff Carl Haggerty is up to in Devon. If you have any examples, drop me a line, or leave a comment.

Load more posts!