Snowflake removed 86% of its weekly status meeting time

Snowflake engineering teams collaborate in Slack channels and manage their work in Jira Cloud. Those two systems only tell the same story if a person keeps them aligned, and that person is always an engineer who would rather be doing something else.A design decision gets settled in a thread. Someone has to go and put it in the ticket, or it does not exist as far as Jira is concerned. Multiply that across every project channel and it becomes a constant, unlogged tax on the team.The weekly sync had the same problem in a different shape. Teams distributed across time zones cannot find a slot that suits everyone, so the meeting is always inconvenient for somebody, and the content is largely status that could have been read.

Snowflake connected their Slack project channels to their Jira Cloud projects with Troopr, then let the channel do the work.Each team invites Troopr into its channel and sets up notifications and a custom emoji that turns a Slack conversation into a Jira issue. Issue updates and reminders arrive in the channel, and the follow-up action is fulfilled there, in Slack, without a trip to Jira.With Troopr Check-ins, the weekly sync became asynchronous. Team members answer when it suits them. Troopr compiles the report with the issue context and recent Jira activity already attached, and posts it to the channel for the manager and the team to read at their convenience.

Snowflake removed roughly 86% of the time its teams were spending in weekly status meetings.The report that replaced the meeting is better than the meeting was, because it arrives with Jira context attached rather than depending on what each person happened to remember. Nobody joins a call at an unreasonable hour to deliver an update that Troopr could have assembled from the work itself.