A technical idea can look very convincing on paper. You know the application, have a picture of the product in mind and expect customers to benefit from it. The harder question is how much of that story has already been demonstrated.

My advice is to get into the field early. Let people try something, watch how they use it and investigate which assumptions hold up. Your product does not have to be finished for this. You do, however, need to know what you want to learn from a test and which conclusions the results can support.

A good initial test helps you decide where to invest next. Sometimes it confirms the direction. Sometimes it shows that a change is needed before further development work makes sense.

Choose the test that answers your question

Each test answers a different question. Clicks alone do not prove demand.

Choose the uncertainty that matters first

Technical and commercial questions overlap in a new product. Can the sensor take the required measurement? Does the user understand the application? Does the device fit into their daily routine? Is the problem important enough for someone to spend money on solving it?

These questions call for different tests. A conversation can help you understand a problem. Assessing measurement quality requires a technical experiment. To find out whether someone can install a product independently, you need to let them try.

Start by writing down what you do not yet know. Then decide which uncertainty has the greatest effect on your next investment. If the suitability of your sensing principle is in doubt, investigate that before spending much time on packaging.

Build enough to learn

An early test can use a limited version of the product. Development boards and a simple enclosure may be enough for a technical experiment. To investigate wearing comfort, a model without working electronics may be more useful.

The build needs to match the question. A large prototype might let you investigate an algorithm, but tell you little about the comfort of a small wristband. If a participant finds that prototype awkward, you need to understand whether their response concerns the concept or the temporary implementation.

Make the same distinction in your conclusions. Record what you tested, under which conditions and with what limitations. This prevents a successful demonstration from quietly becoming accepted as evidence that the whole product is ready.

Hand over the product and observe

If you want to know whether the controls make sense, give the product to someone in your target audience. Ask them to perform a specific task, such as installing it, pairing it or reading its data. Try not to step in every time they hesitate.

That is harder than it sounds. As the creator, you know where the button is and why a light is flashing. You want to explain that they should wait a moment or do something else first. Yet that hesitation is useful information. The eventual customer probably will not have you there to guide them either.

Watch where people get stuck, which steps they skip and when uncertainty arises. Afterwards, ask what they expected to happen. This gives you a clearer route to improvement than simply asking whether they like the product.

A design review is a starting point

A design review is a starting point. User testing needs people to try the product themselves.

Look at use in the real environment

A demonstration at a table reveals only a small part of reality. Daily use may show that someone forgets to charge the product, does not know where to mount it or interprets notifications differently from what you intended.

Where it is appropriate to do so, give trial users time to try the product in their own circumstances. Ask about specific moments: when did it help, when did it get in the way and when was it left unused? A short evaluation form can help you compare responses from different people.

Also gather observations about the value it delivers. What decision could someone make because of the product? Which task became easier? This helps you assess whether you are solving the right problem and whether the chosen features contribute to that.

Explore demand before building a large batch

Alongside user testing, you can test the proposition with a simple landing page and an advertising campaign, for example on Instagram. Show who the product is for and which problem it solves. You can compare different applications or messages to see what attracts interest.

Be clear when something is still a concept. An ad click is also only an initial signal. A conversation with someone who recognises the problem provides different information from a casual like. Ultimately, you want to understand whether that interest remains when people see a realistic price and specific terms.

A campaign like this helps you have more focused conversations with potential customers. You still need to investigate technical feasibility, everyday use and actual sales alongside it.

Use feedback to make decisions

Not every suggestion needs to become a new feature. Some comments relate to a different audience. Others stem from an unclear explanation. Entrepreneurial judgement is still needed to decide which feedback fits the value you want to deliver.

Look for recurring problems and behaviour that challenges your assumptions. If several relevant users get stuck at the same step, that deserves attention. When someone requests an extra feature, ask which problem they are trying to solve. There may be a simpler solution.

After a round of testing, record what you have learned and which decision follows. You can continue, make an adjustment, run another test or stop. Begin with a small test that answers an important question. Repeat the process when new uncertainties arise. This gives each subsequent investment a stronger foundation.

Discuss your next step

Bring us the assumption you need to test. Our rapid prototyping service helps define a useful first build. Already using a development board? Read when to move from breadboard to PCB.

How to test a hardware idea before investing heavily