"After two weeks of working on a project, you know whether it will work or not"
About this Quote
The subtext is about signal-to-noise. Early in a project, reality is loud: stakeholders either show up or they don’t, users lean in or bounce, technical risks reveal themselves, the team’s energy spikes or flatlines. Past that initial window, people get busy defending the investment. The sunk-cost story starts writing itself: one more sprint, one more redesign, one more meeting that will surely clarify the mission. Budge is trying to cut that off by making speed a moral choice, not just a schedule preference.
Context matters: this is a mindset born from environments where feedback is immediate and failure is expensive - startups, product teams, sales-led orgs, anyone who has watched months disappear into a “strategic initiative” that never touched a customer. The line also smuggles in a discipline: design work to be testable fast. If you can’t learn whether it works in two weeks, you’ve built a project that protects itself from the truth.
It’s not anti-ambition. It’s anti-delusion, with a stopwatch.
Quote Details
| Topic | Startup |
|---|---|
| Source | Help us find the source |
| Cite |
Citation Formats
APA Style (7th ed.)
Budge, Bill. (2026, January 16). After two weeks of working on a project, you know whether it will work or not. FixQuotes. https://fixquotes.com/quotes/after-two-weeks-of-working-on-a-project-you-know-121134/
Chicago Style
Budge, Bill. "After two weeks of working on a project, you know whether it will work or not." FixQuotes. January 16, 2026. https://fixquotes.com/quotes/after-two-weeks-of-working-on-a-project-you-know-121134/.
MLA Style (9th ed.)
"After two weeks of working on a project, you know whether it will work or not." FixQuotes, 16 Jan. 2026, https://fixquotes.com/quotes/after-two-weeks-of-working-on-a-project-you-know-121134/. Accessed 9 Feb. 2026.




