Or, you can clone the sample project from GitHub: slack create -template You can create a fresh new project: slack create deno-github-functions Make sure you have everything you need before constructing your app using the CLI.Īfter you've installed the command-line interface, you have two ways you can get started: Start from scratch It’s much easier for an individual to adopt a product on their own than for them to need to convince a coworker to use a product with them.Every Slack app built using the CLI begins with the same shared steps. I think there is an opportunity here to take this a step further: Drive adoption within a company by getting independent individuals to use your product. Eventually, enough teams inside a company were using Slack that it made sense for the entire company to adopt it. This is actually the approach that Slack used to gain adoption. The other problem with this approach is that it requires a large upfront investment in building a product with many features before it’s viable for the entire company to switch.īottom-up: Drive adoption within a company by getting independent teams of 2 or more people to use your product. This is especially true the more employees a company has. This is difficult to accomplish as changing the primary communication tool of any company will meet a lot of resistance internally. Top-down: Convince the C-suite executives to replace Slack with an alternative tool. There are two ways to replace this network effect: Top-down and bottom-up. Microsoft TeamsĪs mentioned, one of the reasons Slack works so well is that it has large adoption within a company. To their credit, they reduce the number of apps you use or need to search for information, which was a minor pain point that came up in a few research sessions. ![]() They then need to break the network efforts of all these products within a company to see strong adoption. For example, not only do they need to ensure their chat functionality is better than Slack’s but they also need to ensure their task/project management features are better than Asana / Monday / Jira / Notion / G-suite etc. The problem with the apps in the second category is that they end up competing with two existing tools. Examples of these apps are Chanty, Rock.so, Flock, Ryver, Twist (there are many more). Feature X is usually something like task management, project management, notes etc. At scale, these solutions run into the same problems as Slack. Slack alternatives tend to fall into two categories:Ī pure slack clone but with some small variations e.g. Have employees that are distributed across timezones. These tend to be companies that have one or more of the following characteristics: These pains are particularly felt by companies that rely on written communication for collaboration since they produce a lot of information that is consumed inside Slack. This causes people to forget to respond to messages or even where to respond to a message. Slack becomes difficult to navigate and easy to lose your place in. They can’t find or refer back to earlier discussions. They miss important discussions happening in channels and especially in threads. ![]() ![]() There are too many channels and too many messages. Whilst this can be a good thing, Slack users don’t have the ability to filter high-quality information from low-quality.Įmployees feel overwhelmed. This increases the amount of information generated in a company. As a result, the way to scale Slack for a large company is to create more and more channels. It was built for synchronous communication and not for collaboration. Slack is based on IRC and is a messaging client. The more people in a Slack workspace, the noisier it becomes.
0 Comments
Leave a Reply. |