Clarifying the project
Now you're in "requirements gathering" mode and it's time to find about what they need done. Find out the scope of the project and the players. Who will be in charge of the database? Who will be using the database? Who will be your main point of contact for the various phases of the project? Discuss the access you will need to other staff members in the design and implementation of the project.
Clarify exactly what output they are expecting on the project.
- Find out what's working and not working about their current situation.
- Why do they need a new solution? Ask them if they have any specific solutions in mind.
- Find out what's really important to them with regard to this project. Ask what they are expecting to be different as a result of implementing this solution.
- Ask what specific deliverables they are expecting as outcomes of this project.
- Find out how they will measure the success of the implementation and the solution.
- Propose a few possible solutions or ideas after fully listening to them.
Start formulating in your mind how you fit into their solution. Jot down points you will make later to sell yourself. There is no need to discuss technology or 4D at this stage. The product is the last thing you want to address.
Other considerations
- Ask about the timing of the project. When do they want to start? When does the project have to be complete? Are there any outside deadlines or events that impact the timing of the start or completion of the project?
- Ask if there is a specific amount budgeted for the project. They may not tell you, but if they do, it will help you tailor your proposal.
Make sure you get all of your questions answered so you can prepare your proposal.
Repeat back briefly to the client the main points you heard (intended outcomes, deliverables, timing, etc.). Ask them if you left anything out.