an idea does not have to arrive fully formed. it can begin as a sentence, a small frustration, or a need without a name. starting does not require every answer. sometimes it means spending a little time with the right question.
what is this for? who will use it? what should change when they do? these questions help give the work a direction. its scope, name and first shape can emerge from that conversation.
before making a list of features, it is worth looking for the smallest understandable version. does it need a page, a few screens, or simply a drawing? the right beginning does not have to be a large product.
working it out together also leaves room for disagreement. we can discuss what matters now, what can wait, and which questions should stay open.
design and code can continue the conversation. they give a thought a visible form, something to try and discuss again. a first prototype can help make the idea clearer before making it look complete.
one small test for the beginning: can we describe what we are making in a single sentence?