The more we worked with Twist the more we realized how we could improve our experience with Slack. Using Twist, I actually felt less connected to my team-and most of them said the same thing.Īs disappointing as they were, however, I wouldn’t trade those ten days with Twist. Slack did more to shape our culture than we initially realized. One of the hidden benefits of Slack that Twist couldn’t deliver was the way it facilitated fun, social interaction with an all-virtual team. Our team culture is core to our business. I found the labels confusing and constantly felt like I was missing something important. The threads, for example, were less visible than they should have been-which defeated the purpose. The vision for Twist was right, but the implementation fell short. That extra layer of organization keeps the conversations untangled and makes it easy to review them later on.Īfter ten days of using Twist, we decided to go back to Slack. Instead of messages going unmediated into channels, as in Slack, in Twist messages fit inside threads that live inside channels. Twist seemed to address our core problems with Slack.įor instance, threaded conversations were baked into the design from the start. Most of the team was excited about the test. It felt very beta when we switched, but the developers were responsive and helpful. Twist was created by the team that developed ToDoist. The Switch to TwistĪfter reading several positive reviews of Twist, I decided it was time for another full-immersion trial. At thirty and growing, we needed something better. When there were ten or twelve of us, Slack was manageable. These three problems were compounded as the team grew. We also have team members in three time zones so the real-time conversation tends to stretch out the day and steal our margin. That means constant interruption, and time for deep work vanishes. Slack works synchronously, like texting or instant messaging. Slack is built on the wrong communication model. All that needs to get mentally untangled to follow the conversation on just topic A after the fact. Topics A, B, C, and D might interlace as items are brought up and discussed in the relevant channel. The search is robust enough, but, because of a lack of threads, it is very difficult to piece together a conversation. I spend an inordinate amount of time trying to find stuff in Slack. Slack made it difficult to find what you’re looking for.Slack wasn’t built with threads (topics) as an integral part of the model, so conversations wander from one topic to the next and often back to a previous topic. Slack made it difficult to track conversations.We ran into three main limitations with the app, and I’ve heard the same from other users: But, just as email didn’t scale with our growth, neither did Slack. After a full-immersion trial, we were sold!īut then we unsold ourselves. As we grew, email became unmanageable and other solutions like Basecamp weren’t a fit. My team and I have been using Slack as our primary communication platform since June 2014. Status: 400, Response: Failed to send notification.The 3 Changes that Made It Work for Me and My Team Again The output of which says the following:įailed to send notification. When I select these two conditions, it mentions that it must match events created by the core… Not exactly sure what that means, I don’t have rules in either of those links where it takes me to “Notified events for hosts/services” Which sounds like to me, any event will be matched by the notification (I could be wrong, but honestly, this isn’t where the issue lies, at least I don’t believe so.)Īnytime a notification needs to go out, I get a “failed notification” event. I’ve check a couple events from those from the checkboxes, (namely up to down, ok to warn, ok to crit etc) I’ve enabled two notification conditions, “Match host event type” and “Match service event type” (As suggested by someone else on this forum) I’ve added “URL Prefix for links to Check_MK” as checked, and gave it a specific URL prefix to my Check_MK site.įor contact selection, I told it to notify the automation account only. I’ve put in a “Webhook URL” as the next dropbox, then I’ve set the URL in the following text box. The only other option in there is ‘cancel previous notifications’. I’ve created a notification rule, with “Slock or Mattermost” as the Notification Method.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |