Speed is only useful if you're going in the right direction
Key takeaway: Spend the first days of a project understanding the problem, because AI makes building the wrong thing cheap and fast.
Velocity has a direction. A team shipping fast toward the wrong goal isn’t productive, and AI makes it easier than ever to build the wrong thing quickly.
I’ve seen teams build entire systems in weeks with AI tools, then realize they’d solved a problem nobody had. The code was clean, the tests passed, and none of it mattered, because they started building before they understood what it was for. Speed amplifies whatever direction you’re already headed.
Rework costs more than the redo. You lose what you could have built instead, morale drops, and stakeholders stop trusting you when they see the same problem “solved” twice. A team that spends two days thinking and three building will almost always beat one that spends five building and five rebuilding.
So slow down at the start, just long enough to answer four questions:
- What problem are we actually solving? The human one, not the technical one.
- How will we know it’s solved?
- What’s the simplest thing that could work?
- What are we choosing not to build?
You don’t need a ceremony for this. Answering them up front is cheap insurance against expensive mistakes.
When the cost of building drops to near zero, building the wrong thing becomes the biggest expense. Cheaper building also means more things become worth building, so choosing among them matters more. Typing was never the bottleneck. Understanding was, and now you can build the wrong thing in an afternoon instead of a quarter.