Collaboration’s Biggest Challenge
A few years ago, SLACK was the messaging darling, enabling quick, simplified messaging with minimal setup and management for administrators. In addition, it boasted a robust API/Integration framework which let it do what so many collaboration applications to date had struggled with – get inside everything you work with.
Or rather, you get inside SLACK with everything you work with.
Fast forward to today and there are not only a number of challengers to SLACK but also SLACK has been hit by a few complaints about being “too much”, “always on”, “never able to get away”, etc, etc, the list goes on.
This isn’t a SLACK problem though, this problem has been in existence since the first iteration of that green jellybean icon came to represent your availability – you are here, you are available, let’s get to work. That little icon came to represent not only your availability to get work done but also an indicator of when you are available to get work done (read: how much work are you putting in, how later are you up).
Collaboration’s biggest challenge to autonomy and not micromanaging your team has always been that little green icon.
How do I know where they are if it’s not green?
They’ve been away for so long, they must be doing something else?
Why aren’t they answering when they are green?
It’s the perceived notification that someone is available and ready to do work for you – that’s how it is interpreted but what it was never meant to show.
Want to know how pervasive the colour schemes are in messaging tools? Look no further than them all using similar schemes – green – available, yellow – maybe, red – busy – they flow between different systems so we don’t need to relearn anything. And just like a traffic light, they mean exactly the same things to a user.
But the question for the traffic light – Would you leave it on green all day long? – probably not, because eventually, it’d burn out.
When email took on the collaboration challenge it did so without presence, asynchronous communication – “I’ll get back to you when I can because I could get busy” – which unfortunately turned into the simplest of messaging protocols that allowed and enabled people to SPAM us with updates on everything and anything.
As much as we want to make it, Collaboration’s biggest challenge will never be the technology, the protocols, the AI to reduce message flow, where it’s hosted, whose hosting it, etc, etc, etc. It will be the trust we put in each other around presence and messaging to ensure that those boundaries are preserved and supported.
Think that’s an easy way out? Then here’s a question for you – What is your company’s collaboration policy and does everyone know what it is and how it works?
Doubtful, if you do fantastic and if you do, that means this post wasn’t meant for you, it’s for the rest of us that are working against that little green jellybean trying to find the right way out.