Which Product Ideas Deserve Development? | Build What Wins
BBiernath Consulting
Focused conversation · No obligation Book a conversation

Build What Wins™ · Evidence Before Investment

Which product ideas deserve development—before capital is committed?

If your team has more ideas than capacity, this 5-minute briefing shows how Rolf Biernath, PhD., pressure-tests a product investment before momentum makes the decision expensive.

The question that comes firstDoes this deserve development?

For CEOs and leadership teams at product-driven manufacturers.

Watch firstA 5-minute decision briefing for industrial product CEOs
Video not loading? Watch it directly ↗
30+years leading innovation at 3M
58issued U.S. patents
50+product programs analyzed
$75Kpreserved in one documented STOP

The signals

Which of these are showing up inside your product pipeline?

Individually, each issue can look manageable. Together, they often mean conviction is moving faster than the evidence.

01

Too many product ideas are competing for limited engineering capacity.

02

A prototype is being discussed before the core assumptions are tested.

03

A customer request is being treated as proof of market demand.

04

Technically impressive products have struggled to gain traction.

05

Momentum, politics or enthusiasm are starting to replace evidence.

06

Leadership needs a decision the team can explain and defend.

The hidden cost

The expensive part is discovering the flaw after development begins.

Late answers consume more than budget. They consume engineering capacity, leadership attention, production options and the confidence to make the next decision.

01

Engineering capacity

Your best people spend months proving that something can be built before the business case is proven.

02

Tooling and capital

Once prototypes, tooling and line time are committed, weak assumptions become more expensive to challenge.

03

Time and momentum

The longer an initiative survives, the harder it becomes to question—even when the evidence has not improved.

Pressure-test the decision while change is still cheap.

Discuss the decision

The Build What Wins™ Screen

Four investment questions. One defensible decision.

Every answer must be supported by evidence, not confidence alone.

V

Viability

Is there real customer pull and economic value?

D

Defensibility

Can the company sustain advantage and margin over time?

F

Feasibility

Can the organization build and scale it under real constraints?

T

Timing

Is the market ready, and are the critical conditions in place now?

GOProceed with development.
PIVOTAdjust the concept, evidence or approach.
STOPPreserve resources until the idea earns the next dollar.

A documented STOP

The Audit that paid for itself on day three.

A roughly $20M contract manufacturer brought in a customer-requested product. The Pressure-Test Audit surfaced the fatal flaw on day three: no end buyer had confirmed willingness to pay, and no industry benchmark supported the required price.

A customer request does not equal market validation.
Tooling and capacity preserved$75,000

The initiative stopped while the decision was still inexpensive to reverse.

Your conversation

Bring the product decision that is already on your desk.

1

Frame the decision

Discuss the specific idea, portfolio choice or customer request your team is weighing.

2

Examine the evidence

See how the Screen surfaces the assumptions that decide viability, defensibility, feasibility and timing.

3

Clarify the next move

Leave with a clearer view of whether the idea deserves a GO, PIVOT, STOP or further pressure-testing.

Rolf is paid the same whether the answer is GO, PIVOT or STOP. That independence is what makes the recommendation worth trusting.

Built for a specific decision

This is a fit when a wrong product bet costs real money and real quarters.

Best fit: Product-driven manufacturers evaluating a new physical product, major update, growth initiative or portfolio choice.

Especially useful when: Engineering capacity is constrained, evidence is incomplete and leadership needs a decision the team can defend.

Not designed for: Pre-revenue startups, pure SaaS products or teams looking only for more brainstorming.

Independent perspective

What experienced product leaders say about Rolf.

“I can always trust Rolf to give me an unbiased view of technology and its potential for success.”Alan Hulme-Lowe · Executive, 3M
“Rolf is one of 3M's most versatile innovators. He elevates every team he works with, both as an inventor and a leader.”John Wheatley · Division Scientist, 3M

Common questions

Before you book, you probably want to know…

Is this actually a sales pitch?

It is a genuine business-development conversation, but it is not designed as a pressure-based sales call. Rolf will discuss the product decision in front of you, show how the Build What Wins Screen applies, and recommend further work only if it is useful and you want to continue.

What if the idea is not fully formed yet?

That is normal. The conversation can focus on one early idea, several competing initiatives or a customer-requested product that has not yet earned development investment.

Do we need to share confidential technical details?

No. The first conversation can stay at the decision, evidence and business-risk level. You can avoid disclosing proprietary technical information until the scope and confidentiality expectations are clear.

What happens after the call?

You will have a clearer view of whether the initiative deserves further pressure-testing. If an Audit, Sprint or prioritization workshop makes sense, Rolf will explain why. If it does not, that is a useful answer too.

Evidence before investment

Bring one real product decision. Leave with a clearer view of what it has earned.

A focused conversation about your situation, with no obligation to continue.