Smoke Tests: Learn Before You Build

One of the most expensive mistakes in product management is building something customers never wanted.

It sounds obvious, but it happens more often than we like to admit.

A team can spend weeks designing a feature, months developing it, and significant effort launching it, only to discover that customer interest is far lower than expected.

This is where smoke tests can be incredibly useful.

A smoke test lets you test customer interest before investing heavily in building the actual product or feature.

You essentially create the appearance of the experience without necessarily building the underlying capability.

The goal isn’t to trick customers.

It’s to learn whether the problem is important enough for them to take action.

What Is a Smoke Test?

Imagine you’re considering launching a new premium feature.

Instead of building it immediately, you add the feature to the product interface.

A user clicks it.

Instead of accessing the finished functionality, they might see:

“This feature is coming soon. Join the waitlist.”

Now you can measure how many users show interest.

You haven’t built the feature.

But you’ve learned something about demand.

That’s the basic idea behind a smoke test.

Why Clicks Matter More Than Opinions

One reason I like smoke tests is that they move us beyond hypothetical feedback.

During interviews, customers might say:

“That sounds useful.”

That’s interesting.

But it’s still an opinion.

A smoke test asks the customer to take action.

Click the button.

Join the waitlist.

Request access.

Start a trial.

That behavioural signal is usually stronger than someone saying they might use the product.

A Real Example

Suppose you’re considering building an automated reporting capability.

You could spend three months building the entire system.

Or you could add a “Generate Report Automatically” option to the existing product.

When users click it, explain that the capability is currently in development and ask whether they’d like early access.

Now you can measure:

How many users discover it
How many click
Which customer segments show interest
How often they return to the feature
Whether they request access

You haven’t proven Product-Market Fit.

But you’ve reduced uncertainty.

Smoke Tests Are Not Proof

This is where Product Managers need to be careful.

A click doesn’t mean someone will pay.

A waitlist signup doesn’t guarantee adoption.

Even repeated interest doesn’t prove that the final product will solve the problem effectively.

A smoke test answers a narrower question:

“Is there enough initial interest to justify learning more?”

That’s it.

You still need customer research, usability testing, prototyping, and eventually a real product.

Don’t Fake the Value

There’s an important ethical distinction here.

A smoke test should test interest without misleading customers.

Don’t pretend a feature exists if it doesn’t.

Don’t charge customers for something you can’t deliver.

Don’t create false urgency.

Be transparent.

For example:

“We’re exploring automated reporting and would like to understand whether this is valuable to you. Request early access.”

That’s honest.

You’re inviting customers to participate in discovery.

Test the Right Audience

Another lesson I’ve learned is that overall click-through rates can be misleading.

Suppose only 3% of your users click the feature.

That might sound poor.

But what if 25% of your highest-value customers show interest?

Suddenly, the opportunity looks very different.

Segment the results.

Look at customer type, use case, frequency of usage, company size, or other characteristics that matter to your product.

The goal isn’t just to know whether people clicked.

It’s to understand who cared and why.

Smoke Tests Can Save More Than Development Time

The biggest benefit isn’t simply saving engineering effort.

It’s creating a culture where teams test assumptions before committing resources.

Instead of:

Idea → Build → Launch → Learn

You can sometimes do:

Idea → Test Interest → Learn → Decide → Build

That small change can dramatically reduce the risk of building the wrong thing.

Final Thought

I’ve come to see smoke tests as a simple but powerful discovery tool.

They don’t replace customer interviews.

They don’t replace prototypes.

They don’t guarantee success.

What they do is give you an early behavioural signal before you’ve made a large investment.

And that’s often exactly what a Product Manager needs.

Because the question isn’t always:

“Can we build this?”

The more important question is:

“Is this worth building?”

A good smoke test helps you answer that question before the expensive part begins.