How do I start when my idea is still vague? — answered by Engineer Saeed Baatiah
Do not wait for clarity. Start with a short scoping session answering only three questions: which problem is costing you money or time today? Who exactly suffers from it? And how will you know it is solved? Those three answers yield a small first version launchable in weeks rather than months. A vague idea sharpens through incremental building far faster than it sharpens through thinking.
Vagueness is not an obstacle — it is the normal starting state, and the mistake is waiting for the idea to clarify itself, because ideas do not clarify by thinking but by contact. A scoping session turns “I want a system” into something estimable through four questions: who exactly is the user? What is the one thing they will do here that they cannot do today? How do they manage it now? And how will you know the solution worked?
The third question is the most important and most skipped: how does the work get done today? Because the answer reveals what the system must actually do rather than what you imagine. Many projects are built on an idealised description of a process and then collide with a team working an entirely different way. The fourth prevents the worst outcome: a system delivered with nobody able to say whether it worked. The first consultation and scoping is free, and its output is a written scope and an estimate — with no obligation.
- Who is the user? What is the one thing they will do?
- How is the work done today? — the most important, most skipped question
- How will you know it worked? — settled before the build, not after