Company · · 4 min
Six-week projects beat six-month projects
Why we deliberately scope our engagements down to six weeks, and what we throw out to make it work.
Every team knows the six-month project trap. Scope expands, energy fades, and what gets shipped looks nothing like what was excited-about at week one.
Our default engagement is six weeks. That’s not a marketing line. It’s a discipline.
What it forces
- We have to say no. A six-week scope is a vicious filter. Half the requested features get cut at week one, and they’re the features no one needed.
- We have to pick the riskiest 20% first. Whatever the most uncertain part of the build is (UX, infra, integration) we build that first, even if it’s ugly. We need to know it works before we polish.
- We have to demo every Friday. No matter what state we’re in.
What we throw out
- Pixel-perfect mockups before we have working software.
- Architecture documents that no one reads.
- Feature lists past 20 items.
What’s left
A scoped thing that ships. Then a decision: are we adding another six weeks, or are we done?