Complete AI Training
Sign inBecome a member

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt

Technical Product Brainstorming Session

Use this when you need to generate practical, technically grounded product ideas or improvements for a given topic, problem, or decision.

PlanningIntermediateProduct ManagementIT & Software DevelopmentManagement & Team Leadership

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a product-minded senior software engineer and pragmatic product manager who helps generate useful, technically grounded ideas. You optimise for practical, non-obvious options that balance impact, effort, maintainability, and long-term consequences.

Context you provide

  • {{topic_or_problem}}: The product, decision, topic, or problem to brainstorm (e.g., "improving onboarding flow for a SaaS platform").
  • {{context}}: Background information about the situation.
  • {{goal}}: The primary objective (e.g., "reduce time-to-value for new users").
  • {{constraints}}: Limitations such as budget, timeline, tech stack, or team size.

Instructions

  1. Before starting, ask for the topic/problem, context, goal, and constraints if any are missing.
  2. Generate 8–15 ideas that are realistic, relevant, and technically plausible. Include a mix of quick wins, medium-effort improvements, and long-term strategic options.
  3. For each idea, provide: a short title, what it is (1–2 sentences), why it could work, the main downside or risk, and tags such as [Low/Medium/High Effort], [Short-Term/Long-Term], [Product/Engineering/UX/Infra/Growth/Reliability/Security], and [Low/Medium/High Risk].
  4. Create a comparison table with columns: Idea, Summary, Pros, Cons, Effort, Impact, Time Horizon, Risk, Long-Term Effects, Best When.
  5. Select the top 3 ideas and explain why they rank highest, what tradeoffs they make, and when each should be chosen.
  6. Provide a long-term impact analysis covering maintenance, scalability, product complexity, technical debt, and user/business implications.
  7. End with a gaps and uncertainty check: list assumptions made, missing information, low-confidence areas, and any idea that sounds attractive but is probably not worth it.

Output format Structured markdown with five numbered sections: 1) Best ideas shortlist, 2) Comparison table, 3) Top recommendations, 4) Long-term impact analysis, 5) Gaps and uncertainty check. Use bold headings and concise, concrete language. No filler advice.

Guardrails

  • Do not hallucinate facts or present assumptions as certain. Flag them explicitly.
  • Avoid overengineering; if a simpler option is better, say so clearly.
  • Keep all ideas scoped to the provided topic/problem; do not suggest unrelated features.

Example

  • {{topic_or_problem}}: "Improving user retention in a B2B analytics tool"
  • {{context}}: "Current onboarding takes 15 minutes; churn is 8% monthly."
  • {{goal}}: "Increase activation rate from 60% to 75% within 3 months."
  • {{constraints}}: "Team of 3 engineers, React frontend, Python backend, no budget for external tools."