There are two kinds of bug reports. The first kind is a paragraph of text that describes what went wrong — what page you were on, what you clicked, what you expected, what happened instead. The developer reads it, tries to reproduce it, can't, marks it as "can't reproduce," and moves on.
The second kind is a 90-second screen recording where you show exactly what you did and exactly what broke. The developer watches it, understands instantly, and fixes it.
The difference in outcome between these two approaches is dramatic. Here's how to record the second kind.
Before you record, navigate away from wherever the bug happened and start fresh. You want to capture the full reproduction path from scratch — not drop in halfway through. This helps developers reproduce it exactly.
Narration is what makes a bug recording useful rather than just a video of something breaking. As you go through the steps, say out loud what you're doing and why. "I'm on the checkout page, I'm going to enter a promo code, and then I'll hit apply — watch what happens to the total."
Don't try to document three bugs in one recording. Make three recordings. Short, focused bug reports are easier to triage, easier to assign, and easier to close.
Download your recording and attach it directly to your bug ticket. A video in the ticket means developers don't have to ask follow-up questions — everything they need is right there.