Anyone who has cooked from a YouTube video knows the specific frustration. Hands covered in flour, phone propped against a bowl, and the presenter has moved on to step six while you are still on four. You scrub back fifteen seconds. Too far. Forward ten. Now they are talking about their sponsor.
Video is a terrible format for instructions and an excellent format for demonstrations, and tutorials are usually asked to be both at once.
What Roadmap does
Roadmap reads a tutorial's transcript and returns the steps in order — the sequence, with the reasoning attached, as a document you can read at your own pace instead of the presenter's.
Paste any YouTube URL at xyzyoutube.com, or type xyz in front of one, click Analyse, and choose Roadmap.
The demonstration stays where it belongs — in the video, which you can consult for the parts where seeing it matters. What you no longer have to do is use a timeline as a set of instructions.
Where it fits
Cooking. Read the whole thing first, discover you needed to marinate something for four hours, adjust your evening accordingly. This is a better outcome than discovering it at step five.
Software setup and configuration. Long tutorials on deployment, environment setup, or tool configuration are pure sequence. Having the steps as text means you can copy commands, work at your own pace, and — critically — find your place again after the inevitable interruption.
DIY and repairs. Hands are busy, phone is somewhere with sawdust on it. A written sequence you can glance at beats scrubbing a video with your elbow.
Processes described in talks. Not every roadmap comes from a tutorial. A conference talk describing how a team migrated a system contains a sequence worth extracting even though it was never framed as a how-to.
Roadmap or Todo List?
Two related formats that people mix up.
Roadmap keeps the process intact: this step, then this one, and here is why it is in that order. It is the video's method, made readable. Use it while you are following along.
Todo List strips the process down to the actions that are now yours. No explanation, no context, just what you have to go and do. Use it after a strategy talk or a productivity video that left you nodding without moving — the format that answers "fine, but what do I actually do on Monday."
Same video, two different jobs. Running both is a reasonable move on a dense tutorial.
The one thing to know before you rely on it
Roadmap works from what was said. Tutorials where the crucial information is visual and unnarrated will produce steps that are accurate and useless.
The tell is a presenter who says "and then you just do this part like so" while their hands do something specific and unexplained. The transcript contains "and then you just do this part like so." So will your roadmap.
Video editing tutorials, design walkthroughs, and any repair video that relies heavily on camera work are the usual offenders. For those, the roadmap gives you a reliable outline of the stages and you still watch the fiddly bits — which is a better outcome than watching all of it, but not a replacement.
Software tutorials, cooking, and anything where the presenter narrates what they are doing tend to produce roadmaps you can genuinely work from.
Tutorials in other languages
Some of the best technical tutorials are not in English. Translation across 70+ languages combines with Roadmap, so a Japanese repair guide or a German software walkthrough becomes an ordered checklist in your language. See translate and summarize in one step.
Related formats
For deciding whether a tutorial is even the right one, Bullet Points tells you in two minutes what it covers. For a question about one specific step — "what size drill bit did he use?" — Ask beats reading anything.
Try it on the tutorial you have already restarted twice. Start here.