have-you-considered

To surface alternative approaches during a design review, you need a structured exploration of existing solutions and prior art. This process broadens the solution space by proposing actionable alternatives with defined benefits, adoption costs, and contextual fit rather than just identifying flaws.

Exploring trade-offs in product decision-making requires evaluating alternative techniques and processes to broaden the solution space. You can generate defensible recommendations by assessing demonstrable benefits, adoption costs, and contextual fit for each suggested approach before committing to a final feature direction.

Structuring feature explorations with evidence involves mapping one suggested alternative per subject. This structured output ensures every proposed approach includes demonstrable benefits, adoption costs, fit analysis, and sources, shifting the focus from fixing bugs to opening doors for new product and design directions.

Yes, you can evaluate process alternatives across technique, product, design, and other domains. The exploration mechanism applies broadly to reviews, design sessions, and feature explorations, enforcing a structured output that includes benefits, costs, fit, and sources for each alternative proposed.

You should not use alternative surfacing when you need to fix bugs or identify what is wrong with a current implementation. This approach is designed specifically to suggest what could be different by opening doors and broadening the solution space, not to perform debugging or error correction tasks.