Insights

Product and technology decisions worth examining

Practical observations about customer needs, assumptions, engineering dependencies and evidence of value.

Product discovery · Working perspective

A feature request is a clue, not a product opportunity.

A customer may ask for a dashboard, an automated workflow or another integration. Before designing it, I want to know what is hard today, how often it happens and what it costs in time, effort or risk. Those answers may reveal an opportunity worth exploring—or a simpler fix.

Practical question: What would we observe if this need were real and important?

Try the Opportunity Discovery Canvas →
Delivery judgement

Small dependencies can have large consequences.

Delivery plans often capture visible activities more easily than uncertain dependencies. An early technical test may be more valuable than an extra status report when an untested assumption threatens the critical path.

Practical question: Which assumption would be most expensive to discover was wrong late in delivery?

Product judgement

The requested feature is not always the real need.

A stakeholder's proposed solution is useful evidence—but not necessarily the final problem definition. Before committing, look at the pain point, user journey, data and consequences of the design.

Practical question: What changes if we solve the underlying need with a different workflow?

Business value

Delivered technology is not the same as realised value.

Completion is a delivery milestone. Value depends on what improves for customers, operations, cost, resilience or risk—and whether someone owns those outcomes after launch.

Practical question: Who will know if the intended benefit actually occurred?

These are general professional observations, not disclosures of employer or client decisions.