An idea can feel complete while it lives in your head. Every button works. Every visitor understands the label. The problem disappears exactly as imagined. The first person who tries it often reveals a different story.
That is why a small, testable version is useful. You are creating a chance to learn before adding more detail.
The GOV.UK Service Manual advises teams to understand what users are trying to do and how they do it now. Its guidance on usability testing recommends observing people attempting realistic tasks. Although written for government services, that approach can also inform a small personal project. Sources: understanding users, usability testing
Start with a task
Write one sentence about the problem. For a blog, it might be: “A reader wants to find an article about food and understand whether it is worth reading.” Build only enough of the experience to test that task.
Ask a likely reader to try it. Avoid telling them where to click. Watch where they hesitate and ask what they expected. Compliments are pleasant; a specific point of confusion is more useful for the next edit.
If you take notes or recordings, get permission and keep unnecessary personal details out. A handful of conversations can reveal issues, but it cannot prove what every reader wants.
Change one meaningful thing, then try again. Perhaps the category name needs to be clearer, the introduction more concrete, or the reading link easier to find.
This creates a healthier relationship with an unfinished idea. It becomes something you can improve through evidence, rather than something you must defend because you have already spent time on it.