Eduserv is a not-for-profit IT services organisation and a registered charity. We work with universities, colleges and public sector and specialise in providing high-end complex web hosting and CMS development. We also provide single sign-on via OpenAthens and license negotiation for leading software and data resources Clients include DVLA, DCSF, BIS, Victim Support, The Science Museum The important bit here is that we are a highly successful business of around 110 people. We have VERY wide staff skills and a wide range of contexts: staff work together on projects to work for a specific time and to a specific goal ... The daily communication of ideas and operational progress provides a clear challenge.
Not big enough to have dedicated internal comms team! But have complex business goals / markets that mean we need to communicate effectively. Why collaborate? Gets things done faster, better and it can be very rewarding. What gets in the way? Size, all have own day-to-day priorities and heads in sand most of time, getting on with business. Nobody takes time to factor in collaboration. Collaboration takes work. It means knowing who to ask, how to approach them and often doing it in an unobtrusive way – just raising awareness of current projects can unlock all sorts of collaborative possibilities.
- Same as with Web2.0 outside the walls: resistance to trying new, 2.0 things… - Blocking is common: quote from a head of IT (who will remain unnamed!) “ IT departments exist to say no!” (it’s a bit rude, but there is some truth in it..)
invisibility! Fit in with real working lives - our staff aren’t (all) bloggers or Twitter users! stop things getting lost in translation avoids duplication smarter to work together work things out quicker less embarassing.... sharing intelligence
- Wordpress to the rescue! - Theme – simple, open source, some branding around the edges (logo, colours, etc)
Free WP plugin – details in the paper. Some confusion about difference between blog and forum posts
- constant need to tell people to visit Inform - resistance to YET MORE EMAIL from some staff, but even now a year later we see 70% of our traffic coming from here - track click-throughs with Google Analytics
- the most meaningful of the stats is the 42 authors: nearly half our staff have written a post, which is exciting - also “add it to Inform” has become a standard phrase...the practice is starting to be embedded in the culture
Some issues about the difference between forum and posts, or even WHAT to post Staff still need to be helped along: the technology (however good or simple) won’t replace human contact We’ve found that lots of people have opinions and ideas that just weren’t being voiced before – innovation brings people out from the shadows. But you do tend to sometimes hear the same voices – so again, need to keep pushing the message and encouraging all to get involved.
As I said before, we’re a medium sized organisation We also employ contractors. People are coming and going. Skills change; people work on disparate projects Knowing who people are is one thing. Knowing what they do and their skills is another altogether
Everyone has AD, but it is cumbersome, complicated and difficult to surface ...so we built a prototype system which pulls information from AD but also has additional info
removes the need for a separate series of cumbersome “bio” documents on a shared drive search allows staff to look for people with skills they might need staff can edit their own data (apart from some “core” data) built on a “forms” system which allows us to add fields in seconds login to authenticate using their existing Active Directory U/P we’ve included pictures – so you can put a face to a name (or vice versa!) actually, one of the most viewed pages is a grid with *just* faces which links to profiles...!
- this is also important: we built it so we could grab core information across the web...
which means we can use this info in lots of places: single source, duplicate channels taking a key web 2.0 concept – data distributed everywhere – and applying it to inside the organisation on the left is a “bookmarklet” - staff can drag this to their browser toolbar; clicking on it gives instant access to the directory on the right is an example of an embedded profile from the directory on an Inform blog post
accessing staff information is a surprisingly key thing to many people. our old sharepoint intranet shows this... we weren’t expecting this to be as useful as it has!
- Everyone suffers from inbox fatigue - Email overload has diluted the impact of the medium.
- we’re new to this, but staff seem keen on Yammer: 56 staff are currently using it (more than half the staff) we don’t know yet if it’ll continue to be popular – time will tell currently people use it for sharing links, asking about local resource (“where is the nearest picture framing shop?”) etc
still learning on this one ironically, it is people who use twitter who “get” Yammer, and their question is “why can’t I just use Twitter...?” all of this is optional – we’re not forcing it on people (that has pros and cons) but people like to have a choice
- by this I mean that many daily tasks: finding templates, expenses forms, documents are common, but too hard - we have a sharepoint intranet but are now replacing this..
- ..with a rapidly built “dashboard” which is (or will be shortly) personalisable for each person, pulling in info from relevant places in the business. - panels are drag/drop/add/remove: think www.netvibes.com but for internal use only - this dashboard approach is going to be how we start to grab information from disparate data sources and display top-level rapid information: for instance, HPSD, Sage, “Elbow” (our in-house contacts database), Salesforce, etc - we also have a google search box which we have pointed at our internal filestore, Inform and several other useful sources
as a technology company, we sometimes assume we need complicated technology... ...when actually the problem (not being able to find common documents) is really, really simple and can be solved really easily!
we do have some access to dev resource (in these examples, me: I’m not actually a coder, more a dabbler!) but if you don’t, many of these things can be done with existing web-based tools. even if you don’t want to use these tools longer term, they are valuable to demonstrate proof of concept and get buy-in for internal investment
Collaboration 2 0
COLLABORATION 2.0 Real world examples, and what we’ve learnt
Mike Ellis, Solutions Architect @m1ke_ellis Lisa Price, Web Communications Manager @lisapr1ce Hello.
> these slides are CC licensed > they will be available online at slideshare.net/eduserv By the way...
It is easy saying “web2.0 is good”... ...but making it happen is harder
1. doing things quickly 2. building community and content 3. finding out what “2.0” does for organisations This is about our real experiences
> 256 posts, 42 authors > 14,000 visits > 53,000 page views > 3.75 pages/visit > 04:30 avg. time on site ...tangible results
> get agreement to play > use a known, easy platform (WP) > perfection isn’t a necessity > iterative improvement > launch, then continue to cultivate > innovation is infectious! total spend: £0 + 20 days effort (of which maybe 2 days tech) What we learnt:
> some messages are better suited to a micro-blogging format > some staff find it spammy / noisy > others are a bit non-plussed > in general it seems popular (so far!) total spend: £0 (but admin tools would be nice..!) What we learnt (are learning..)
* when the task is often straight-forward Problem #4: things are too complicated*
> Sharepoint wasn’t delivering everything we needed ...but people assumed that we *should* use it > 95% people’s day-to-day tasks are simple: staff search, expenses form, templates total cost: £0 + 5 days build What we learnt:
> we’re a hosting and development company so we have skills and resources in-house > BUT! Wide range of easy-to-use, low-cost apps out there that can help you transform how you work. Don’t need to be an uber geek to get started. Caveat
> social software in the enterprise requires a different approach: speed is essential.. > rapid build, adapt on the fly > fail quickly! > internal marketing is essential > push for open editorial policy > put users at the centre Conclusions
Mike Ellis @m1ke_ellis [email_address] Lisa Price @lisapr1ce [email_address] Thanks!