Agile methodology means shipping small, working versions of your work repeatedly, instead of waiting until the full picture is complete at the end. A small version used by real people teaches you more than a complete plan built in isolation.
Key Takeaways
- Agile favors small, working versions delivered repeatedly over one complete version delivered late.
- A first version doesn’t need to be excellent, it needs to exist and be tested against real use.
- Feedback from actual users shapes each next version more reliably than assumptions made in isolation.
- Accepting that the first version won’t be perfect isn’t failure, it’s part of the method itself.
- The right question isn’t how complete is this, it’s what’s the smallest version I can show this week.
Why This Is Harder Than It Looks
When I started building CitizenUp, the first instinct was to design the whole platform before showing it to anyone. What changed my path was deciding to launch a very simple version within a few weeks, then adjusting it based on what the volunteers and organizations actually using it told me. Each version was better than the last because it was built on real use, not a guess at what people needed.
The most important lesson wasn’t the speed of delivery, it’s accepting that the first version won’t be perfect, and that this isn’t failure, it’s part of the method itself. That’s a practical expression of Continuity, one of the five elements of The Method.
The Steps
Step 1: Define the smallest working version of what you’re building. A version that’s too ambitious delays the real feedback you actually need.
Step 2: Show it to real users before it feels ready. Waiting until it feels ready usually means waiting past the point where feedback would still be cheap to act on.
Step 3: Adjust based on what actual use reveals, not on your own assumptions. Assumptions made in isolation are reliably wrong in ways real use exposes quickly.
Step 4: Repeat the cycle, treating each version as a stepping stone, not a final product. The method’s value compounds only if you keep shipping and adjusting, not just once.
A Worked Example
The version of CitizenUp that eventually worked bore little resemblance to the original plan, not because the plan was bad, but because dozens of small adjustments based on real volunteer and organization feedback had reshaped it into something better fitted to what people actually needed.
Closing
If you’re working on something large right now, ask what the smallest version of it is that you could show this week, instead of waiting until everything is complete.
FAQ
Doesn’t shipping something incomplete look unprofessional?
A clearly labeled early version, with a stated intent to improve it based on feedback, reads as intentional rather than unfinished.
What if early feedback contradicts the original vision?
That contradiction is often the most valuable signal you’ll get. Real use reveals what the original vision missed.
How small should the first version really be?
Small enough that building it doesn’t take more than a few weeks, and real enough that people can actually use it, not just look at it.
