You have five recorded interviews and forty pages of scattered notes. Somewhere in there is the moment a participant hovered over the pricing toggle, said "I don't get what this changes," and moved on. That moment is the finding. The problem is getting it out of a two-hour recording and in front of your team in a form they will actually read.
Here is a workflow that turns those buried moments into one review anyone can open in a browser, no install and no signup. It works whether your player is a video call recording, a transcript tool, or a local file open in a media player.
Step 1: Queue up the exact frame in your player
Open the recording and scrub to the second the finding happens. If your player shows the participant sharing their screen, pause on the frame where the confusing element is visible. If it is a talking-head clip with a transcript on the side, pause where the quote sits so the words are on screen. The point is to freeze one still that captures the moment, because Cobalt Capture takes still frames, not video. You are trading a 90-second clip for a single frame plus your words.
If you have never done a screen capture instead of a recording before, the difference is covered in screen capture vs screen recording. For research synthesis, stills win: a reader scans ten frames in the time it takes to watch one clip.
Step 2: Capture the frame in a browser tab
Open a new review in Chrome or Edge and click Capture screen. The browser prompts you to share a window or the whole screen. Pick the window with your player in it. The current frame is drawn to a canvas, and that becomes your first item.
You do not install anything and you do not sign in to start. An anonymous review is kept for 30 days, and you can claim it permanently later by signing in with Google or a magic link.
Step 3: Crop to the moment, not the whole screen
Drag a rectangle around the part of the frame that matters. Crop out the player chrome, the timeline scrubber, the browser tabs. If the finding is about the pricing toggle, crop to the toggle and the label beside it. Cropping the still is the only image edit, and that is on purpose: a tight crop tells the reader where to look faster than any arrow would. There is more on that trade-off in why a cropped still beats an annotated live page.
Step 4: Add the finding as a comment, and pin the spot
With the frame captured, add your comment. Type it, or dictate it with the browser's built-in speech recognition if you are on Chrome or Edge. Dictation is faster when you are working through a stack of clips; you talk through what happened while the frame is still fresh. Write what the participant did and said, not just your interpretation. "P3 hovered the annual toggle, said 'I don't get what this changes,' and clicked away without switching" beats "toggle is confusing."
If the frame has several elements and you mean one, drop a numbered pin on the exact spot. Pins point at a specific place on the screenshot, so "see pin 1" removes any doubt about which button you mean. The mechanics are in pinning the exact spot on a screenshot.
Step 5: Add a free-floating comment for the pattern
Not every item needs a screenshot. When three participants stumbled on the same step, add a free-floating comment with no frame: "3 of 5 participants did not switch to annual even after asking what it changes. Pattern, not a one-off." This is where synthesis happens. The captured frames are the evidence; the free-floating notes are the reading of the evidence. Keeping both in one review means nobody has to reconcile a slide deck against a folder of screenshots.
Step 6: Publish and send one link
Click Publish. The review is saved and gets a short public URL of the form /r/<slug>. Anyone with the link can read it, no login required. Send that one link to your team, your PM, and the designer who owns the flow. This is the heart of user research synthesis: instead of scheduling a readout, you hand people a document they can open on their own time.
Readers can post a comment on any individual item, and you as the owner can mark each one resolved as decisions land. That gives you a lightweight way to track what the team agreed to do about each finding, without a bug tracker or a board.
Step 7: Export for the readers who need a different format
The same review is available as a PDF and as a Word document for a stakeholder who wants something to file, and as plain markdown at /r/<slug>/markdown. If a finding turns into a build task and a coding agent is doing the work, the markdown is the format it reads. One capture pass produces a public link for people, a polished doc for the report, and clean text for a tool. You choose what each receiver gets.
Working from written notes instead of recordings? The same idea applies, and it is walked through in turning raw interview notes into a shareable review. Either way, the output is one link that ends the argument about where the findings live.
Grab your recordings, open a tab, and capture the first moment that made you pause during the sessions.