Chapter 5 · Practice 2 of 4
Show evidence that the project is feasible
Why it matters
Feasibility is where many proposals are weakest. Saying "the project is feasible" proves nothing; show it.
| Kind of feasibility | Evidence you can include |
|---|---|
| Technical | A small spike: a screen that scans a barcode, a model trained on a sample of the data |
| Data | The dataset link, a letter or email granting access, a count of records |
| Skills | Who on the team has done similar work, and courses you have passed |
| Cost | A rough budget for hardware, hosting or paid APIs, and who pays |
| Time | The timeline in this chapter, with the must features in the first half |
A one-day spike on the riskiest part, such as the speech model or the hardware link, is the most convincing evidence you can bring. If it fails, you have learned something before committing a year to it.
Do
- Build a small spike on the riskiest part before submitting
- Attach data access proof if you can
Avoid
- Writing "the project is feasible" with no evidence