The smallest useful version of an idea

A young builder sketches an app for a school club. It has profiles, payments, maps, rewards and chat. The idea may be thoughtful, but the first version has become too large to learn from quickly.

The better question is sharper: what is the smallest thing we can make that would answer one important question?

Start with the riskiest assumption

Every idea rests on beliefs. People have the problem. They care enough to act. The proposed solution fits their routine. Someone may pay for it.

Pick the belief most likely to break the idea. The first version should test that assumption before polishing everything around it.

Let a person do the work once

Many services can be tested manually. Before building an automatic study planner, make one plan for one student by hand. Before coding a marketplace, help one buyer and seller complete the exchange.

Manual work is not the final product. It lets the builder observe what people ask for, ignore or find confusing.

Decide what evidence would count

"People liked it" is hard to use. Decide what action would count as evidence. Did five people complete the process? Did someone return without being reminded? Did a user exchange money, time or information?

The measure should match the assumption. Compliments do not prove willingness to pay.

Be honest about the rough edges

Explain that the version is a test. Do not pretend a manual process is automated or promise features that do not exist.

Honesty improves the feedback. Test users can respond to what is real instead of what they imagine the finished product might become.

The result should change the plan

After the test, choose one of three moves: continue, change or stop. Stopping a weak idea after a small test is not wasted work. It protects time for a stronger one.

A first version does not need to impress everyone. It needs to put one important assumption in contact with the real world.