Every project we take on starts with the same question: what is the smallest thing we can build that stands up on its own?
Not the smallest thing we can build. The smallest solid thing. A wall with half its bricks missing isn't a small wall, it's a pile. A website with no contact page isn't a lean website, it's an unfinished one. The goal is a version that is complete for its purpose, even if that purpose is narrow.
Why we scope this way
Most projects that run late don't run late because people work slowly. They run late because the scope keeps moving. A feature gets added in week two, a page in week three, an integration in week four, and every addition pushes the finish line further away while quietly making the whole thing more fragile.
When the scope is the smallest solid version, three things happen:
- We can give a fixed price. We know what we're building, so we can say what it costs.
- We can move fast. Fewer pieces means fewer decisions, fewer dependencies and fewer things to test.
- You get something real sooner. A working site or tool in week four beats a perfect one in month six.
How we find it
We start by listing everything the project could include. Then we ask, for each item: if this were missing on launch day, would the thing still do its job?
If the answer is yes, it moves to a second phase. If the answer is no, it stays. What's left is usually a third of the original list, and it's almost always the most valuable third.
The second phase is not a graveyard. Most of our clients build it — but they build it knowing what the first version taught them.
What it isn't
The smallest solid version is not a prototype, an MVP that falls over, or a way to cut corners. Everything in it is built properly: tested, accessible, documented and handed over. We just build fewer things, and build each one to last.
That's the whole method. Small solid pieces, laid in order, until it stands.