DEV Community

Cover image for Ship the small version first
Pratyush Shivam
Pratyush Shivam

Posted on

Ship the small version first

The biggest product mistakes I have seen were not small features that failed. They were big ones that took months to build before anyone outside the team used them.

The fix is simple to say and hard to do: ship the small version first.

Small is not the same as unfinished

A small version still has to work properly. It just does less. One workflow instead of five, one type of user instead of all of them, one report instead of a dashboard. What it does, it does well.

What the small version teaches you

  • Which part people actually use. It is rarely the part the team argued about most.
  • Where the real load is. Real traffic shows you which parts need to scale and which never will.
  • What you got wrong. It is far cheaper to learn this after two weeks than after six months.

How to find the small version

Ask: what is the one thing a user must be able to do for this to be worth anything? Build only that, end to end, and put it in front of real people. Everything else goes on a list.

The hard part

The hard part is not technical. It is accepting that the first release will look modest. Teams that can live with that usually end up building the big version faster, because they build the right one.

I'm Pratyush Shivam, CTO at Konfidio in Berlin, where we build TrustedTrucks. More about my work at pratyushshivam.com.

Top comments (0)