# Show the bug on screen, walk through the code, skip the call

> Bug reports with the steps on video, code walkthroughs with timestamped review comments, and a library you can search by what was said.

URL: https://office.greatwork.company/record/for/software-teams
Last updated: 2026-11-21

Engineering teams lose hours to "can you hop on a call and show me?". A two minute recording of the bug, or of the pull request, answers it, and it's still there next month when someone asks why.

## What gets in the way

- Bug reports that say "it's broken" with no steps
- Code reviews where the context lives in one person's head
- Time zones that turn a 5 minute question into a day's wait
- Decisions explained once on a call and never written down

## The workflow

1. **Get the bug on video.** Send the reporter a request link with three lines of instructions. They record the steps in their browser, address bar and all, and it lands in your library.
2. **Walk through the change.** Record the diff with your camera in the corner and paste the link in the pull request. Reviewers comment on the second they have a question about.
3. **Keep the why.** The transcript is searchable. Six months later, searching "rate limit" finds the walkthrough that explained it.
4. **Wire it up.** A webhook on new requested recordings can open an issue with the video link attached.

## Example: A flaky checkout bug, fixed in one round

QA reports checkout fails on some orders. The lead sends a request link. The recording shows the failure at 0:41, right after a coupon is removed, which nobody had tried. The fix ships with a 90 second walkthrough linked in the pull request, and the reviewer's one question is a comment at 0:58.

---

Office by Great Work. Questions or corrections: hello@greatwork.company
