My role at Learning Pool is a hard one to define exactly. A couple of weeks ago, we had a big company meeting where everyone got together to discuss the last year’s efforts, and what we want to achieve in 10/11.
At one point Paul asked everyone in the room to raise their hands if they knew what I did for the company. I don’t think anyone raised their hands. I know I didn’t.
That’s ok, though, and I stood up and rather incoherently tried to explain it all. I don’t think I did a great job, but I do think I managed to get across that it isn’t just about going to conferences.
My job title is Community Evangelist, and the first thing to say is that I’m not a Technology Evangelist. The role of technology evangelist is a pretty well established one in the techie sphere, pioneered by Guy Kawasaki at Apple in the 80s. Robert Scoble fulfilled a similar role for Microsoft in the mid-noughties.
This is important, because I’m a newcomer to Learning Pool’s core technology, based on Moodle, and would probably be a pretty terrible evangelist for it. Not only that, but my actual technical knowledge is sketchy at best, and I’m as good an example as any that a little knowledge can be a very dangerous thing.
Instead of technology, my focus is people – as individuals, members of communities of practice or interest, and organisations. My aim is to promote the behaviour and culture of the internet: collaboration, openness, generosity, curiosity.
So what do I actually do?
- Well, I do go to conferences. I speak at them, sit and listen at them, wander around chatting to people at them. I collect business cards, I give out my own. I enthuse about the wonders of the internet and what it can do for people and organisations.
- I also turn up at organisations, like Councils – occasionally invited – to talk to groups of people, whether management teams or whole departments about the work we do and why it’s important
- I manage communities. This will be really important once the new LP website is launched, which will be full of online networking goodness. Encouraging participation, getting more people to join, providing real value for both members and for the company.
- I convene. One of the things Learning Pool effectively invested in when they recruited me was my network: as a result of the past 5 years I’ve spent writing this blog, whoring myself on Facebook and Twitter and attempting to be as helpful as possible, I’ve built up a group of people who find knowing me occasionally useful. I introduce people who may not have otherwise known one another, and hope that interesting things happen as a result.
- I curate. I spend a lot of time following hundreds of blogs and Twitter streams, picking out the best bits and distributing links to them via Twitter, Delicious, Google Reader, and of course this blog. As I like to say, I find this stuff so you don’t have to.
- Of the stuff I read, a lot comes from sectors other than the public, and so I spend time thinking how emergent technology and ideas can be applied to public services. I guess I just put stuff into context. It isn’t that hard, and the joy of it is that I don’t need to have too many original thoughts of my own.
- I write longer pieces than blog posts, like the Twitter guide – and I have some more of these planned. Hopefully they are useful for those that download and read them, and they promote LP as a helpful company who know more or less what they are talking about
- I have ideas. 99% of them are stupid and never go anywhere. The other 1% are stupid but get made less stupid by someone else, and may end up actually happening.
- I get wind of potentially interesting projects for Learning Pool to be involved with, which are often way outside the usual day to day business of the company. I do my best to win the work, and after completing it, we decide whether it is an activity that could be ‘productised’ and marketed as a service we could offer more widely.
- Finally, I share stuff. Pretty much everything I ever think gets written up and published, whether here or on Twitter. I also try to share the interesting stories I come across in local government, finding the pockets of great innovation that are going on and making more people aware of it, so everyone benefits. My recent interview with Mark Lloyd is an example of that. I’m always looking for more.
So that’s a brief run through of what I do. In practice, I spend a lot of time reading, mainly off the screen and mainly within Google Reader, and a lot of time out and about meeting people. There are worse ways of making a living.
And I think they are very lucky to have you.
We are indeed! – I do a lot of the “people meeting” stuff with Dave and as well as everything else – we have great fun. As we often say to each other when we’re out & about – it isn’t really like work, is it?
Good job too. Sure the fellow wouldn’t know real work if it hit him in the face 😉
… and you do it so well! Do you need a company to be a community evangelist …? What I mean is, (how) does the back up from the other roles make a big difference? I’m still trying to avoid having a proper job.
I’m a self-employed personal evangelist. Sadly my employer doesn’t pay me much.
@Shane – you are far too kind!
@David – good question. It makes a difference for me – the business development side of things is what adds a real frisson of excitement to the whole thing. Plus being part of a wider team gives you a) admin and technical backup which frees up time for the fun stuff; b) a salary, which means you can afford to spend time at the conferences etc – something I really struggled with when freelance; c) a sense of defined purpose – fundamentally my job is to make money for Learning Pool, however tangential my role in it actually is. Having that helps focus the mind, and makes it easier to decide if an activity is worthwhile or not.
@joe – yes, as I mentioned above, it was a problem I had when I was freelance. The convening, curating and conferencing took a back seat to paid work – hence why the decision to give up a little freedom (although, luckily, in my case hardly any at all) and become an employee again was actually quite easy.