sayhushCapture a brainstorm in short sections, then group the transcript by question rather than by the order you spoke. Choose a central point, move supporting ideas underneath it and remove unrelated branches. Sayhush provides the transcript; the outline is an editing step.
Give the brainstorm one question
Start with a narrow question such as “What should our onboarding explain first?” A broad recording about the whole product can be difficult to review. Keep a scratch document open and use a heading for the question. You can think aloud without treating every sentence as a commitment or an item that belongs in the finished piece.
Capture small clusters
Speak a short cluster of thoughts, stop and insert, then begin the next cluster when ready. If you need a break inside a recording, use Pause and wait for Paused. Short sessions also fit Sayhush’s five-minute recording limit. Do not rely on one very long take as your only copy of an important idea.
An illustrative collection of thoughts
For example: “We should explain microphone permission. People might not know where text goes. Maybe show the shortcut first. Billing is another question. We should make it clear that Pause is different from Stop.” These are invented notes for this guide, not output from a transcript test. Their speaking order is not yet an article structure.
Group by what the reader needs
Manually group the example into “Start: permissions and shortcut,” “Control: Pause versus Stop,” and “Result: where text appears.” Put billing in a separate account section unless it changes the first-run task. This is an editorial decision: you are choosing what answers the original question, not asking dictation to infer the correct structure.
Keep discarded ideas somewhere intentional
If an idea is worthwhile but out of scope, move it to a parking section with a brief reason. Delete repeated filler from the final outline. Preserve any uncertainty that matters: “test whether the shortcut is discoverable” is different from “users cannot find the shortcut.” The second requires evidence the brainstorm may not contain.
Draft from the outline
Read only the next heading, dictate a short explanation, then review it before moving on. This keeps the finished draft from repeating the entire brainstorm. Confirm examples and product facts before publishing. The success criterion is whether the outline answers the question you started with, not whether every spoken idea survived.