Month: January 2014

Collaboration ground rules

groundrules_bSometimes to make collaboration work you need to set some ground rules.

It’s easy to say, “let’s start up a google doc!” – and imagine everyone leaping in to give their ideas. But it’s not so simple as that, especially if folk haven’t had the experience or confidence in this way of working.

Instead it’s necessary to have a think about how the collaborative activity might be approached, and ensure everyone is aware of the process you have selected.

Often this will be the case when the technology available is a bit lacking. As an example, a recent collaborative effort I started was based in a ‘Note’ within a group on Yammer. Notes are the collaborative writing part of Yammer, but they aren’t terribly sophisticated and won’t allow you to use formatting such as tables.

So, I spent a bit of time describing how to add ideas to the list. I came up with a fairly simple process that involved a bold heading for each new item, with two bullets points underneath for other related information to be recorded.

Without this introduction, people may have been unsure what to do, and so not bother, or even accidentally start hacking up what others had written.

At the very least, when working on a Google Doc with others, for example, I’ll put “No deletions!” at the top as a general rule to people.

Any other collaboration ground rule tips to share?

Link roundup

I find this stuff so you don’t have to:

Tips for running a LinkedIn group

linkedin-logoI’ve just started a LinkedIn group on the topic of digital skills in the workplace. You are very welcome to join.

I have to admit – I’ve not done much with LinkedIn groups before, and while much of it is pretty intuitive to anyone who has used similar features on other networks, I’ve had to learn a fair bit too.

Here’s some handy hints that might save you some bother if you have a go at setting up your own LinkedIn group in the future.

Sharing files

You can’t post documents – so you need to upload to Dropbox, Box or SkyDrive and link to them.

Likewise, if you want to collaborate on a document, you’ll need to use Google Doc or something similar.

You can only send one announcement email a week

So make it a good one – perhaps summarising the last 7 days activity and getting people excited about what’s to come. This is also a good way of bringing discussions to people’s attention that might otherwise have got lost in the flow of the group.

Be careful who you let in

There are armies of people who seem to attempt to join every single LinkedIn grow going for no apparent reason. My advice is to make your group invite only, and if you don’t recognise someone who applies to join, have a quick look at their profile.

If it isn’t immediately obvious why they would have an interest in your group, you can either just ignore them, or if you are feeling nice, ping them a message asking why they want to join your group.

Build a sense of exclusivity

Linked to the above, because there are a lot of groups on LinkedIn, you need to make yours stand out a bit. I did this by making my group a closed one, that you can only access if you are a member.

Practice in private

Have a private group that only you know about so that you can practice how the features work with minimal embarrassment. Not everything in LinkedIn works the way you’d expect it to, so having a sandbox you can play around in is a good idea!

Curate the stream

LinkedIn groups are effectively streams of content. It does some work for you in listing stuff on the main page in order of relevance and interest. However, bits will get lost unless you do some curation.

As mentioned above, one way of doing this is to use the weekly email announcement feature. However, I think it is probably worth having somewhere separate where the really good stuff can be listed on a web page somewhere – particularly for new members who need to catch up.

Edit the email templates

A key thing to do to make the community welcoming and a bit more personal is to edit the messages that get sent out to prospective members when they first apply to join.

A few of the groups I am a member of don’t do this, and it does make you feel like the group isn’t particularly actively managed or facilitated, so it can be off putting.

Remember – this is about community management

So even though the medium we are using is LinkedIn, everything else still applies – welcome new members, reply to people’s posts, seed conversations, promote the group in other channels, and so on. Go read Feverbee, and do what it tells you.

Have you any further tips for running a successful LinkedIn group?

Fail better

BECKETTAs Samuel Beckett wrote, in Worstward Ho:

Ever tried. Ever failed. No matter. Try again. Fail again. Fail better.

Acknowledging the fact that we surely don’t really want our project to fail, what does failing better actually mean?

It’s surely about openness – in other words, admitting that things didn’t go to plan, and having a frank discussion about what went wrong – so that everyone can learn from it and ensure it doesn’t happen again.

Often projects that don’t quite succeed are brushed under the carpet and never mentioned again, or worse, spun to pretend that everything was hunky dory.

Here’s a lovely example of openness around failure from Chris Poole, the legendary moot of 4chan fame, discussing what went wrong with his company that made the Drawquest app:

With that said, life goes on, and the best path forward is not a wounded one, but a more learned and motivated one. I’m definitely not itching to start another company any time soon—it will take time to decompress and reflect on the events of the past four years—but I hope that if I do some day decide to pursue a new dream, I’ll be in a much better position to. After all, I did just receive a highly selective, four-year education for a mere $3.6 million dollars! (I find humor helps as well.)

So when reviewing a project which perhaps didn’t turn out as expected, rather than covering things up, or apportioning blame, try to fail a bit better. Identity what went wrong, and how it could have been avoided – and tell people about it.

How WordPress as a Platform helps nimble project delivery

wordpress-logoWordPress started as a blogging engine, then became a content management system, and these days is a platform for the development of simple web applications.

After all, an awful lot of applications are basically just about putting bits of text into boxes, and then arranging them in order to suit whatever your purpose is. Putting words into boxes is something WordPress is very good.

The bit of functionality within WordPress that enables this is the custom post type. You’re no longer limited to just blog style posts and static pages – you can create your own content types with their own taxonomies and as many different fields (boxes to put text in) as you like.

Here’s an example from a project I’m working on at the moment. It’s all about building up and managing a disparate community of people within a government department. I need to keep a record of all the members of this community, what they do, what interactions I have with them, whether they attend meetings and respond to surveys, etc etc.

The default position here would be to build an ever-growing spreadsheet in Excel, which would be increasingly difficult to manage and interrogate as it had more and more information added to it. I’ve done this in the past and it’s a nightmare.

Instead, of going down that route, I’ve spun up a quick WordPress instance and got he PauPress plugin installed and running. PauPress helps turn WordPress into a simple CRM (customer relationship management) system, which allows you to record details of contacts and your interactions with them.

Now, I would never dream of advocating the use of this as a corporate CRM solution for any critical purpose (it’s a bit clunky in places and I suspect with lots of data and users it could get pretty slow), but as a way of getting a simple, easy to use database up and running in minutes for a handful to people to be able to use, you really can’t beat it.

It’s a hack – a quick, cost effective and neat solution to a problem. It helps that WordPress is open source, with a huge developer community, which means that a simple Google search for “WordPress [what you want to do]” usually results in a few options to solve whatever problem you’re trying to solve.

What do you need to have in place for your organisation to be able to make the most of this stuff?

Obviously, somewhere to be able to quickly throw up new WordPress sites, and to install the necessary plugins to make this stuff happen. But also the skills and knowledge within your teams to be comfortable doing this and to advise others about making it all happen.

Load more posts!