Design a multi-lens product plan review pipeline

The Problem

Product plans get reviewed by one person. Usually the PM's manager. Sometimes a tech lead. Occasionally a designer. The feedback comes from a single perspective, filtered through a single set of priorities and blind spots. The plan ships with those blind spots intact.

This is how teams build products that are strategically sound but technically fragile. Or technically elegant but commercially unviable. Or commercially strong but impossible to use. A Harvard Business School study on decision-making found that teams using multiple evaluative perspectives make decisions that are 45% more accurate than those relying on a single evaluator. The benefit comes not from averaging opinions but from surfacing blind spots that no single perspective can see.

The standard review process is also slow. Sequential reviews, where the CEO reviews, then engineering reviews, then design reviews, create a weeks-long feedback cycle. By the time all perspectives are incorporated, the market window has shifted or the team has lost momentum.

McKinsey's research on organizational decision-making shows that companies with structured multi-perspective review processes reach decisions 30% faster than those with ad-hoc review chains. Structure accelerates, it does not slow down.

One Lens Is a Blind Spot

Every functional perspective has a characteristic blind spot. CEOs over-index on ambition and under-index on execution complexity. Engineers over-index on technical elegance and under-index on market timing. Designers over-index on user experience and under-index on business model. None of these perspectives is wrong. Each is incomplete. A plan reviewed through all three is not a compromise. It is a plan that has been stress-tested from every angle that matters.

How This Prompt Works

This prompt creates a multi-lens product plan review pipeline that evaluates your plan through three distinct perspectives in parallel, then synthesizes the feedback into a unified assessment.

The three lenses:

• CEO/Founder Lens: Evaluates strategic ambition, market positioning, competitive differentiation, and whether the plan thinks big enough. This lens asks: "Is this the right bet for the company?" It challenges scope that is too conservative and flags strategic gaps.
• Engineering Lens: Evaluates technical architecture, data flow, dependencies, edge cases, and implementation risk. This lens asks: "Can we actually build this, and will it hold up?" It challenges vague requirements and flags technical debt risks.
• Design Lens: Evaluates user experience coherence, interaction patterns, accessibility, and whether the plan solves the user's problem in a way they will understand. This lens asks: "Will users succeed with this?" It challenges assumptions about user behavior and flags usability risks.

Each lens produces a structured review with scores across key dimensions and specific, actionable feedback. The pipeline then synthesizes the three reviews into a single report that highlights:

• Points of agreement (high-confidence areas)
• Points of tension (where perspectives conflict, revealing real tradeoffs)
• Critical gaps (blind spots that all three lenses surfaced)

When to Use It

• Before committing significant engineering resources to a product plan
• When you want to simulate the feedback you would get from a leadership team before presenting to them
• After writing a plan in isolation and wanting to stress-test it
• When your team is too small to have dedicated strategy, engineering, and design reviewers

Common Pitfalls

• Treating all feedback as equal: Not every piece of feedback requires action. The value is in surfacing perspectives, not in implementing every suggestion. Use judgment to decide which feedback to act on.
• Running it only once: The highest value comes from running the review pipeline iteratively: review, revise, review again. Two rounds typically catch 90% of issues.
• Ignoring the tensions: When the CEO lens says "go bigger" and the engineering lens says "reduce scope," that is not a bug. That is the most important conversation you need to have. Do not resolve tensions by averaging. Resolve them by deciding.

Further Reading

• Decision Quality in Organizations - Harvard Business Review
• Three Keys to Faster and Better Decisions - McKinsey & Company
• The Role of Design in Product Strategy - Nielsen Norman Group