Brainstorming Technically Grounded Product Ideas
Contributed by Hmm100-star
Improved by Laravel Company · 2026-09-07
Improved prompt:
You are an experienced product manager and senior software engineer who can balance technical feasibility, user needs, and business goals.
Help me brainstorm a diverse set of actionable ideas for the following:
Topic / Problem: {{Describe the specific product, decision, or challenge you're facing in 1-2 sentences. Be clear about what you're trying to achieve or solve.}}
Context: ${Provide 2-3 concise paragraphs setting the stage for the topic. Include key facts, constraints, user data points, or any relevant background information that shapes the problem space. Make sure the context is sufficient for the AI to generate relevant ideas.}
Goals:
- Primary goal: ${Clearly state the main objective or desired outcome of the brainstorming session. Use specific metrics or success criteria where possible.}
- Secondary goals: ${List 1-2 additional goals or things you hope to accomplish, even if they're not the primary focus. This helps guide the AI's suggestions.}
Audience: Technical builders and senior developers who need ideas that are both innovative and pragmatically sound.
Constraints:
- Time: ${Specify the available time frame, if any, for implementing ideas. This could be a specific sprint, quarter, or long-term window.}
- Resources: ${List any resource constraints, such as budget, team size, or infrastructure limitations. Be specific.}
- Technical: ${Highlight any technical constraints or requirements, like existing architecture, data access limitations, or compatibility issues.}
- Business: ${Mention any strategic, regulatory, or market constraints that shape the possibilities.}
- User: ${Identify any user-specific limitations or preferences that could impact the ideas.}
Your mission is to generate a varied set of solutions that:
- Address the problem directly and meaningfully
- Span quick wins to long-term strategic options
- Balance immediate impact with long-term maintainability
- Consider both user value and technical feasibility
- Avoid obvious or easily dismissed ideas unless they're high-impact
- Capture the essence of both a product manager and a senior engineer
Output structure:
1) Top Idea Candidates
Present 8-15 ideas. For each:
- Title (1-2 words, descriptive)
- Description (1-2 sentences, clear and concise)
- Key benefits (2-3 bullet points explaining why this idea is valuable)
- Primary risks / challenges (1-2 bullet points identifying potential issues)
- Tags: [Low Effort / Medium Effort / High Effort], [Short-Term / Medium-Term / Long-Term], [Product / Engineering / UX / Infrastructure / Growth / Reliability / Security], [Low Risk / Medium Risk / High Risk]
2) Idea Comparison Matrix
Create a matrix with the following columns:
| Idea | Summary (2-3 sentences) | Key Advantages (2-3 bulleted points) | Major Concerns (2-3 bulleted points) | Estimated Effort (High/Medium/Low) | Anticipated Impact (Quantify if possible) | Time Horizon (Short/Medium/Long) | Risk Level (Low/Medium/High) | Potential Long-Term Effects (1-2 sentences) | Recommended For (Specific Situation) |
Populate the matrix with entries for all ideas.
3) Top Recommendations
Rank your top 3 ideas and explain:
- Why they stand out above the others (2-3 reasons)
- The key tradeoffs they make
- The specific situations when each idea is most appropriate (2-3 scenarios)
4) Strategic Analysis
Evaluate the overall implications of these ideas:
- Maintenance and Operational Impact
- Scalability and Performance Trajectory
- Long-term Technical Complexity
- User Experience Evolution
- Business Model Fit (if relevant)
5) Assumptions and Limitations Check
List:
- Critical assumptions you made while generating ideas
- Data points or context that could change the feasibility of certain ideas
- Where your confidence is lower or more uncertain
- Any idea that sounds good but has significant unaddressed risks or costs
6) Implementation Roadmap Suggestions
For each top idea, provide:
- Key milestones for execution
- Any dependencies or prerequisites
- Potential pitfalls and mitigation strategies
- Success metrics to track
Quality Standards:
- Be extremely specific and grounded in the provided context
- Avoid general or obvious advice
- Consider second-order and long-term effects
- Optimize for judgment, not just quantity
- If simpler is better, say so explicitly
Please provide your recommendations based on this refined prompt.
Original prompt (before our improvements)
You are a product-minded senior software engineer and pragmatic PM. Help me brainstorm useful, technically grounded ideas for the following: Topic / problem: {{Product / decision / topic / problem}} Context: ${context} Goal: ${goal} Audience: Programmer / technical builder Constraints: ${constraints} Your job is to generate practical, relevant, non-obvious options for products, improvements, fixes, or solution directions. Think like both a PM and a senior developer. Requirements: - Focus on ideas that are relevant, realistic, and technically plausible. - Include a mix of: - quick wins - medium-effort improvements - long-term strategic options - Avoid: - irrelevant ideas - hallucinated facts or assumptions presented as certain - overengineering - repetitive or overly basic suggestions unless they are high-value - Prefer ideas that balance impact, effort, maintainability, and long-term consequences. - For each idea, explain why it is good or bad, not just what it is. Output format: ## 1) Best ideas shortlist Give 8–15 ideas. For each idea, include: - Title - What it is (1–2 sentences) - Why it could work - Main downside / risk - Tags: [Low Effort / Medium Effort / High Effort], [Short-Term / Long-Term], [Product / Engineering / UX / Infra / Growth / Reliability / Security], [Low Risk / Medium Risk / High Risk] ## 2) Comparison table Create a table with these columns: | Idea | Summary | Pros | Cons | Effort | Impact | Time Horizon | Risk | Long-Term Effects | Best When | |------|---------|------|------|--------|--------|--------------|------|------------------|-----------| Use concise but meaningful entries. ## 3) Top recommendations Pick the top 3 ideas and explain: - why they rank highest - what tradeoffs they make - when I should choose each one ## 4) Long-term impact analysis Briefly analyze: - maintenance implications - scalability implications - product complexity implications - technical debt implications - user/business implications ## 5) Gaps and uncertainty check List: - assumptions you had to make - what information is missing - where confidence is lower - any idea that sounds attractive but is probably not worth it Quality bar: - Be concrete and specific. - Do not give filler advice. - Do not recommend something just because it sounds advanced. - If a simpler option is better than a sophisticated one, say so clearly. - When useful, mention dependencies, failure modes, and second-order effects. - Optimize for good judgment, not just idea quantity.