How to find the steps that matter in a long tutorial video

A 40-minute tutorial often hides ten minutes of instructions inside the introduction, the personal story, the sponsor read and the recap. You do not need to skip the video. You need to know which minutes contain the steps before you press play.

Decide what you need before you press play

Write down the question the tutorial should answer for you. It sharpens what you look for in the summary. Typical questions are:

• Which tools or versions does this use?
• In what order do I do things?
• Which settings or numbers matter?
• What mistakes does the author warn about?

If you cannot answer one of them from the summary, that is the part of the video to watch.

Start with the summary, not the video

Paste the link into getbrief and read the three parts that matter for a tutorial:

1. TL;DR tells you whether the video answers your question at all. If it does not, you just saved the 40 minutes.
2. The brief gives the steps in the order of the video, grouped under headings for long videos.
3. Worth remembering collects the numbers, commands and settings that are easiest to forget, like temperatures, ratios, versions or limits.

For a long tutorial, the detailed length (Pro or credit packs) keeps more of the steps. The normal length is a good first pass.

Use timestamps to verify only what you will follow

On YouTube, points in the brief link to the exact second of the video. Open the ones that involve a risky step, a setting or a value you will copy, and watch twenty or thirty seconds around it. You get the accuracy of watching the video for the minutes that need it, and the speed of reading for the rest.

What a summary will miss in a tutorial

A summary is built from the spoken words. In a tutorial, a lot is shown but not said: the code on the screen, the menu being clicked, the value typed into a field. Two consequences:

• When the author says "now click here", the summary cannot know what here is. Open the timestamp.
• When a number is displayed rather than pronounced, it will not appear in the notes.

The Open questions section of a brief helps here, because it lists what the transcript does not establish. Treat it as the list of moments to watch.

A workflow that works

1. Paste the link and read the TL;DR. Decide whether the video is worth your time.
2. Read the brief and copy the steps you will follow into your own notes.
3. Open the timestamps for every step that involves the screen.
4. Do the task alongside the video, pausing only on those moments.
5. Save the brief as Markdown with the source link for next time. See YouTube to notes.

Example: a four-minute recipe, in seven lines

A cold brew tutorial of four minutes is already short. Its brief compresses it to two methods (immersion and hot bloom), the same 80 g of coarse coffee for both, 12 to 24 hours of fridge time, and a note that cheesecloth over a fine mesh can leave grit. The strength depends on the steep time: twelve hours gives a lighter brew, twenty-four a much stronger one. Everything else in the video is context. The raw Markdown of this brief is shown on the notes page.

When to use the “for AI” mode

If the tutorial is long and technical and you plan to ask an assistant to turn it into a checklist or code, the “for AI” mode is built for that. It reads the whole transcript in chunks and keeps the rules, numbers and tools in dense Markdown. See how to hand a video to your own AI agent.