Collaboration tools don’t have to suck
In our time of social distancing and working from home, workplace collaboration software has become clutch.
For instance: Zoom’s worldwide downloads has skyrocketed from 90,000 in January 2020 to 343,000 in March.
Similarly, Slack’s number of simultaneously connected users grew 20% between of March 17—25. That’s 12.5 million simultaneously connected users in total.
The shift to organizations working from home has put tremendous demand on collaboration software to help these organizations continue to get their work done.
But even before the coronavirus outbreak, workplace collaboration remained a popular category. Gartner, a leading research and advisory company, estimates that the collaboration software market is expected to be $4.8 billion by 2023. Both Slack and Zoom IPO’d in April of 2019, paving the way for cloud-based collaboration tools to make it big. This is a confirmation of current workplace trends: more remote work, more distributed teams, and the need for organizations to remain adaptive in today’s rapidly changing environment. And I’m sure you discover a new collaboration tool from a colleague or a quick Twitter scan at least once-a-month.
With more collaboration tools, many suck. Few don’t. Let’s look at what separates the two.
What makes a collaboration tool suck?
1/ Non-intuitive UX.
Example: Sharepoint
Sharepoint is Microsoft’s intranet solution, allowing teams to store, organize, and share documents from any device.
Its chief criticism: terrible UX. Sharepoint is confusing and frustrating to learn and bloated with features.
2/ Choosing the wrong customer.
Example: Microsoft Teams
From Merci Grace, an investor at Lightspeed Venture Partners:
Few individual contributors will want to convince their company to use Microsoft Teams. Even though Teams’ UX is better than its Office 365 counterparts, to buy it, you have to buy Office 365. 365’s cheapest tier is $5/month for an annual commitment. This is a decision usually made by an IC’s manager or higher.
In my experience, most enterprises would prefer Teams over Slack because they already have Office 365 purchased and are concerned about any security implications of using a different tool like Slack. But as Merci pointed out earlier, more junior folks prefer Slack because of the quality of its UX and its stance on defaulting to transparency.
Now I’m not saying Office 365 is failing. Microsoft Teams now has 44 million daily active users. But as Office 365 is a business that relies on monetizing existing customers, its long-term growth will stunt from not being able to acquire new customers. From Microsoft, Slack, Zoom, and the SaaS Opportunity:
If Microsoft wants new customers, they need to make better software than its competitors. This, of course, is improbable.
3/ Poor go-to-market.
Example: Google Wave
Google Wave aimed to create a single communication channel that spans email, chat, and documents seamlessly. And its announcement in 2009 generated positive feedback. The problem was the way they rolled out the product: they invited 6000 developer accounts while the product was still being actively tested.
From a post by Taskade:
Because they prematurely invited developers before nailing its usability, they saw high churn. This churn didn’t motivate others from joining by the time they were ready to release. Timing and positioning is everything.
4/ No compelling multiplayer mode.
Example: Keynote
I love Keynote. Keynote is one of the few tools that makes me feel like I can design. And their collaborative capabilities are getting better: I often use its collaboration so that my colleagues and I can edit the same file.
But their collaboration features have two hurdles:
Keynote files aren’t collaborative by default. You have to manually invite others to collaborate on it.
You need macOS Sierra or later to use its collaboration feature. I suppose you can access keynote files via browser if you’re accessing it through iCloud, but I haven’t tried this nor seen it done.
People love Google Slides because it’s collaborative by default. And we’re seeing collaborative presentation making software like Pitch and Dekks enter the foray.
5/ Not taking security seriously.
Example: Zoom
We’ll talk about how Zoom nailed it in a bit, but first, let’s look at how they screwed up by not taking security seriously.
First, Zoom automatically sent user data to Facebook, unknowingly to their users. Second, their customers have experienced a number of unwanted intrusions on Zoom calls (Zoombombing). Third, this tweet:
For the company that most people are turning to for video conferencing, massive security issues is irresponsible. At least they’re on the path to fix these issues.
What are the traits of a good collaboration tool?
1/ It solves a current use case better than every other tool.
Example: Zoom
While they have screwed up a lot security-wise, Zoom’s video and audio quality is the best out there. From Stratechery’s Microsoft, Slack, Zoom, and the SaaS Opportunity:
They’ve solved a current use case better than every other tool and its recent increase in usage prove it.
2/ It prompts a new use case.
Example: Slack
Slack is the poster child of how great collaboration tools introduce a new way of working. From their S-1:
Slack convinced businesses that more internal transparency was better, and their efforts paid off.
3/ It integrates with other tools.
Example: Notion
Notion, an all-in-one workplace collaboration tool that just raised $50 million, allows users to embed links from other systems, like Figma. This is extremely helpful: no need to manually update your Notion doc with the most up-to-date design.
Notion treats the data and objects it integrates from other sources as first-class citizens. Why is this important? It helps users benefit from their existing habits in other systems.
I think data from other systems as a first-class citizen is also a form of social proof. If a new tool I use integrates with Slack (a tool I trust), I’m more likely going to like it.
It’s worth mentioning that Slack also nailed integration:
4/ It has a strong single player experience.
Example: Roam
Roam is a notetaking tool designed to help you find connections between your notes.
Although Roam intends to improve its multiplayer capabilities (their collaborative editing feature is in beta), Roam has a strong single player experience. Its structure is fluid and doesn’t abide by the traditional “folder structure hierarchy” most notetaking apps like Notion, Bear, and Evernote use. They also allow bidirectional linking: making connections between notes seamless and fluid.
They wisely released their MVP as a single-player experience before building out its multiplayer capabilities, validating the desire for a non-hierarchical and fluid way of taking personal notes before building out more features.
5/ It’s frictionless for a new user to join.
Example: Parabol
Parabol, a tool that allows remote teams to do retrospectives, allows others to join their retro through an invite link.
From its founder Jordan Husney:
In my mind, a link invite to a tool is generally a win-win for the user and the business: less friction for the user to join means more user acquisition!
6/ It’s easy to buy.
Example: Trello
Obviously being easy to buy benefits the business. But there’s a benefit to users here too: for older enterprise tools, implementing the tool was a matter of buying it and using IT to help install it. From the SaaS Opportunity:
With many collaboration tools offering a freemium model, implementation is just a matter of paying for it.
With tons of tools out there, it needs to be really good
Again, factors of unsuccessful tools:
Non-intuitive UX.
Choosing the wrong customer.
Poor go-to-market.
No compelling multiplayer mode.
Not taking security seriously.
And factors of successful tools:
It solves a current use case better than everyone else.
It prompts a new use case.
It integrates with other tools.
It’s got a strong single player experience.
It’s frictionless to join as a new user.
It’s frictionless to buy.
Knowledge workers are overwhelmed with the amount of tools out there. And because of this, new tools must provide value immediately upon use. If not, users will abandon it and stick to what they know.
What else would you say makes a collaboration tool stick?