“Let’s import this 100GB CSV into a PostgreSQL table.”
One simple ask, articulated correctly, might seem to reduce the cost of a requirement.
It is a simple requirement; how hard can it be? It should not take more than a day.
As soon you uncompress the requirements, inevitably, the estimate will go up.
How do you know when you need to uncompress a requirement? It is very simple: if no one in your team has done it before.
If no one in your team has experience with the compressed requirement, your or your team’s estimates are wrong.
Uncompress the requirement into multiple tasks, then estimate.
Founder & CEO at InTheValley
I help founders like you fix engineering teams that should be moving faster. If you're scaling a startup, you've probably felt the pain: great people on paper, but execution feels slow. I've been building remote teams for Bay Area startups since 2005 — engineers you can trust who actually deliver and know how to use AI to ship faster, not slower.
Latest posts by Leo Celis (see all)
- The Wrong AI Tool Is As Bad As the Wrong Hire - 04/15/25
- COVID, Remote Work & AI - 04/08/25
- The Tech Downturn is Here – It is Not About Budgets - 04/01/25