Test Your Idea on a Small Scale

The simplest useful test might just be on paper

A big idea can seem convincing until someone tries to use it. Before rolling it out widely, it makes sense to create the simplest possible version so you can check a key assumption. It doesn’t have to be a working product.

For example, you want to change a registration form. Instead of programming the whole thing, sketch two versions of the screen and ask someone to show you where they would enter the information. You’ll find out which field labels are unclear. A sketch like this won’t tell you everything about how the technology will work, but it can reveal problems with clarity.

Every test should answer a specific question. “Do you like the design?” often gets you only a general opinion. More useful questions include: “Could you find the option to change the date?” or “Where did you hesitate?” Pay attention to what people do, not just their praise.

Set boundaries for your test. What can you test safely? If it involves payments, sensitive data, or a safety-critical process, an informal trial without appropriate checks isn’t enough. Lower-risk situations allow for a simpler prototype; potentially serious consequences call for a more rigorous approach.

After the test, record what happened. One person’s opinion doesn’t automatically represent all users. But it can point to a need for further testing or changes, especially if you observed an obvious misunderstanding.

Try it out: Choose an idea. Write down the most important uncertainty and prepare the smallest safe test that can give you information about it. Then decide whether to revise or develop the proposal further.