Use Cases

Teams use Debrief to communicate internally and externally. These are some example use cases for how you can use Debrief

Weekly Operational Metrics Review

Get five person hours back using Debrief instead of an in person operational metrics review

Every week, most teams have at least one operational metrics review. The format has one presenter go through a slide deck filled with charts and graphs detailing the performance from the prior week. Most teams lament the ten person hours spent in this meeting. Even though the information is important, it feels wasteful to listen to one person deliver information to a room of people. However, the meeting can't be an email because the information shared is too rich. The graphs and charts require some narrative and overview.

The meeting can't be an email because the information shared is too rich

Create a Debrief instead

Dense email-like information transfer is where Debrief shines. Instead of an hour-long meeting with ten people, simply record a quick Debrief walkthrough. The team can view it on their own time and as questions directly in the Debrief.

Above is an example from our cofounder Nicolas Salhuana showing what a metrics update meeting might look like. You can watch inline there and click to view on Debrief to see how the commenting system works.

Product Overview

Share product overviews and demos without a meeting

Great teams communicate about their features and designs regularly. While it's fun to get everyone in a room to review a new idea, it's difficult to synchronize schedules in a hybrid workspace. So instead of requiring someone in a different timezone to watch a recording or miss out on the feature drop, create a Debrief!

While it's fun to get everyone in a room to review a new idea, it's difficult to synchronize schedules in a hybrid workspace

Create a Debrief instead

Visual information sharing is where Debrief shines. Trying to create an email capturing all of the detail of a product walkthrough is next to impossible.

Above is an example from our cofounder Nicolas Salhuana showing what a product design walkthrough looks like. You can watch inline there and click to view on Debrief to see how the commenting system works.

Bug Report

Share reproducible steps when reporting bugs

Finding and reporting is part of any team's workflow. Showing reproducible steps sets apart the good teams from the great ones. Instead of listing out steps in words within a JIRA ticket along with a handful of screenshots, Debrief allows you to show your team exactly what's going on.

Showing reproducible steps sets apart the good teams from the great ones

Create a Debrief instead

Visual information sharing is where Debrief shines. Trying to create a comprehensive bug report with a video can be trying. Doing so often leads to back and forth trying to understand the nuance of the steps to reproduce. In the worst case it leads to meetings which use up already scarce hours from your team.

Above is an example from our cofounder Nicolas Salhuana showing what a bug report using Debrief looks like.