Process · · 1 min read
Seven questions we ask before starting a project
Before the seed goes in the ground: questions that pin down scope, risk and the first step.
Most projects don't stumble in code or design, but in questions nobody asked at the start. We open every job with the same seven. We don't need every answer; we need to know which ones we don't have.
- How will we know this worked?
- Who will use it, when, and on which device?
- How is this done today, and where does it hurt most?
- Is the deadline fixed, or preferred?
- Which systems does it need to talk to?
- Who will look after it and update it after launch?
- What's the budget range? Let's shape the scope to it.
Why so many questions
Because each one catches, cheaply and today, an assumption that would cost dearly later. 'Everyone uses desktop' collapses in week one when mobile traffic shows up. 'The deadline is flexible' collapses in launch week.
A good discovery finishes half the project before any code is written.
The answers become a written proposal: scope, timeline, price and first step. Only then does the seed go into the ground.