Finding an original content idea does not always mean discovering an untouched subject. Often it means answering a familiar question with a better demonstration, a clearer audience, or a useful perspective that existing explanations miss. This guide gives you a worksheet to turn a vague topic into something you can actually publish.
Start with a reader's problem
Instead of “productivity tips,” ask: “What does a student studying in a shared room need help with?” A narrow question makes it easier to know what to research and what your answer must include.
Fill in these prompts:
- My intended audience is: ______
- They are trying to do: ______
- The difficult step is: ______
- They have already tried: ______
- I can demonstrate or explain: ______
Find questions people already ask
Look at public comments on relevant tutorials, questions in communities, and search suggestions. Record the actual problem in your own words. A suggested search phrase is not a promise of traffic; treat it as a lead for further research.
Choose a useful angle
Try one of these approaches:
- Different audience: Explain a familiar process for someone with limited equipment, time or prior experience.
- Different obstacle: Show how to handle one mistake that broad guides skip.
- Different evidence: Demonstrate the method and document what worked and did not work.
- Different format: Turn a long explanation into an accurate checklist or a short visual demonstration.
- Different decision: Compare real trade-offs rather than declaring one solution best for everyone.
Example: turn one broad idea into three useful tutorials
Broad idea: “How to record better videos.”
| Narrow question | What the tutorial should demonstrate |
|---|---|
| Reduce room echo without buying equipment | A clear before/after audio comparison |
| Frame a phone tutorial on a small desk | Two workable camera positions |
| Make captions easier to read | Text size and contrast on a real phone |
These are illustrative editorial concepts, not claims that experiments have already been performed.
Score the best ideas
Give an idea 0–2 points for specificity, viewer usefulness, your ability to provide evidence, and production feasibility. A high score helps prioritize what you can deliver; it does not predict views or monetization.
Collect proof before making strong claims
If you're writing a software tutorial, take screenshots from a version you actually used or link to current vendor instructions. If you're describing an experiment, keep your notes and state the sample size and limitations. When you are speculating, say so. These details provide value that a generic list of tips often lacks.
A 20-minute idea exercise
Spend five minutes listing audience questions, five minutes narrowing them to one problem, five minutes collecting examples or sources, and five minutes sketching an answer. Keep the final brief to one page: audience, question, steps, example, caveats and next action.
Build a reusable idea bank
Store each idea with the question, where it came from, what evidence you need, and whether it has already been answered. Review the list before planning new posts. This avoids relying on sudden inspiration and helps you notice recurring reader problems.
Original value comes from the specific answer you can actually support, not from announcing that an old topic has never been covered before.