Process / Notes
From an idea to a first version
Give an idea enough shape to try it in the real world.
An idea can feel complete while it is still only a few sentences in a notebook. Building a first version is often the moment when the useful questions begin.
What does someone do first? Which part matters most? What can wait until there is something to try? These are the questions that turn a possibility into a project.
Start with one useful moment
It is tempting to sketch the whole application. A smaller starting point is a moment worth improving: returning to a project and finding its next action, reading a story comfortably, or practising one unfamiliar phrase.
Write that moment down in ordinary language. If it is difficult to explain, the first version may still be trying to do too much.
Make the first path work
A first version does not need every setting or every variation. It needs one path that makes sense from beginning to end.
Build that path, then try it with realistic content. Empty cards and short placeholder titles can hide problems that appear immediately when a real paragraph arrives.
Build enough to learn something. Then let what you learn choose the next step.
Keep the next decisions small
Once the first path works, the project has something concrete to respond to. A confusing label, a missing piece of context or an awkward mobile layout becomes easier to see.
Treat those observations as decisions for the next version. A short list of specific improvements is often more useful than a long list of imagined features.
Leave a trail for your future self
Keep a few notes about why you chose a direction. They do not need to become a formal document. A sentence about a tradeoff or a screenshot of an earlier attempt can be enough.
When you return later, those notes make the project easier to understand—and make its story easier to tell.
Example article for the portfolio journal. Replace it with your own process, projects and observations.
Continue reading