team-shinchan:brainstorm

Brainstorming a problem reframe involves exploring the underlying issue behind a request to surface clear objectives and alternatives. It generates 2–4 alternative approaches with pros, cons, and complexity estimates to guide early-stage planning and design workshops.

To generate alternative approaches with tradeoffs during product discovery, analyze the core problem to produce 2–4 viable options. Each option includes detailed pros, cons, and complexity estimates, enabling teams to compare solutions and select a recommended validation path before committing to requirements.

The best way to evaluate engineering complexity for different feature solutions is to generate multiple alternatives during brainstorming and assess each option with complexity estimates. Comparing these structured tradeoffs highlights the most practical recommended path for implementation.

Yes, you can save brainstorming results to avoid duplicating ideation sessions by checking for prior outputs and persisting new results. When a workflow state file exists, results are automatically saved to a designated docs directory to maintain session awareness and continuity.

You should use problem reframing instead of directly writing requirements when teams receive vague or solution-framed requests. Applying problem reframing early in product discovery exposes assumptions and clarifies objectives, ensuring you write requirements for the actual problem rather than a premature solution.