New Products and New Technology: Challenge the Initiative Before Commitment

Review the whole proposition

New-product and new-technology reviews are most useful before design choices, supplier contracts, or launch dates become difficult to unwind. They should not be treated as a compliance form completed after commercial approval. The review asks whether the proposition is understood end to end: who will use it, how value is created, what can fail, and which people or systems bear the consequence.

For a product, examine target users, eligibility, disclosures, servicing, complaints, pricing logic, distribution, and exit. For technology, understand architecture, data flows, access, dependencies, resilience, support, and change pathways. The same initiative may require both lenses. Record what is unknown and what evidence is needed; do not fill gaps with optimistic assumptions.

Use staged review with real decision points

• Concept: State the objective, alternatives, affected groups, expected outcomes, and initial risk hypotheses. Decide whether further exploration is justified.
• Design: Map customer and operational journeys, data and vendor dependencies, control owners, failure modes, and safeguards. Ask independent functions to challenge the design before it is locked.
• Readiness: Test representative scenarios, support and escalation capacity, access arrangements, recovery options, and staff understanding. Define the evidence required to proceed.
• Post-launch: Monitor outcomes, incidents, complaints, exceptions, service performance, and emerging dependencies. Set review triggers and a practical pause or rollback route.

Evidence and challenge prompts

Keep the proposal, assessments, design decisions, test outcomes, approvals, conditions, launch scope, and post-launch reviews together. Identify who may accept residual risk, who verifies conditions, and who can halt expansion. Record material dissent and how it was addressed.

• Which assumptions are essential to the business case, and how have they been tested?
• What could create harm even when the technology performs as designed?
• Are service, support, and incident response capabilities ready for the intended scale?
• What signal would cause us to delay, limit, or reverse the launch?

Proportionate review need not slow every experiment. It makes the boundary between a controlled test and broader use explicit, so that a small pilot does not quietly become an unreviewed production service.