What should the purpose of artificial general intelligence be? Cut jobs? Slash costs? I argue that the purpose could be to elevate our creativity.

Consumer AI is outpacing enterprise AI tools. The bigger the chasm between these experiences gets, the greater the security and engagements risks for employers.

While tools aren’t the end-all and be-all for distributed collaboration and knowledge sharing, they’re hardly trivial. Companies cannot allow their collaboration tool stack to languish. They must aim for a world-class user experience.

With the right systems and the right people in community management and curation roles, you can brew the perfect storm of “organised serendipity”. I daresay, that this can often work better than the proverbial water cooler meeting.

In this post, we’ll discuss how you can enhance your knowledge ecosystem by building on your existing collaboration stack. I’ll also go over how to create the right team of people to govern, curate and nurture that platform.

Chat is an essential part of your toolset. The trouble is in the “instant” of “instant messaging”. To be “instant”, you need to monitor chat all day. Not only does that build interruptions into your way of working, it can be mentally exhausting to keep up with all the channels your team and company have created. So in today’s post I want to share a few ways you and your team can use this set of communication tools effectively and support a more productive, async-first way of working.

Let’s look at the categories of collaborative tools most software development teams will need. Many of these will seem familiar to you already, and that’s a good thing. You just need to use the tools effectively. I’ve broken down the list into three categories - must haves, good to haves and optional extras.