Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.getcore.me/llms.txt

Use this file to discover all available pages before exploring further.

Synthesize ideas from product, design, and engineering perspectives to identify high-impact opportunities aligned with business objectives.

​
Tools Required

This skill runs using CORE memory only. No integrations required.

​
Step 1: Clarify the Opportunity

Confirm with your team:
  • Which product or product area are you ideating for?
  • What is the specific objective? (e.g., increase retention, reduce churn, expand to new segment)
  • Which customer segment or user type are you targeting?
  • What are the desired outcomes or success metrics?
Request clarification on ambiguous elements. Review provided research, personas, user interviews, or product URLs for context.

​
Step 2: Generate Ideas from Three Perspectives

Each team member generates 5 ideas from their distinct lens. Encourage divergent thinking; prioritization comes later.
  • Product Manager lens: Business value, strategic fit, competitive positioning, customer segment fit, revenue impact
  • Designer lens: User experience improvements, new interaction patterns, delight and retention mechanics, onboarding enhancements
  • Engineer lens: Technical capabilities to unlock, data leverage, platform or infrastructure improvements, third-party integration opportunities
Capture all 15 ideas without filtering. Title and briefly describe each.

​
Step 3: Prioritize the Top Five Ideas

Evaluate all ideas using these criteria:
  • Strategic alignment: Does this support the stated objective and product strategy?
  • Potential impact: How significantly could this move the needle on desired outcomes?
  • Feasibility: Can this be built with available resources in a reasonable timeframe?
  • Differentiation: Does this create competitive advantage or unique value?
Collectively rank and select the five strongest ideas for deeper analysis.

​
Step 4: Detail Each Finalist

For all five prioritized ideas, document:
  • Name and one-sentence description
  • Selection rationale: Why this idea won
  • Key assumptions requiring validation: What needs to be true for this to succeed?
  • Rough implementation approach or complexity level

​
Output Format

Ideation Session Results Opportunity
  • Product area: [Which product/feature area]
  • Objective: [What we’re trying to achieve]
  • Target segment: [Who we’re building for]
  • Success metric: [How we’ll measure success]
🎯 Top 5 Prioritized Ideas Idea 1: [Name]
  • Description: [One-sentence summary]
  • Rationale: [Why this scored highest]
  • Key assumptions: [What needs to be true]
  • Feasibility: [Quick complexity assessment - Small/Medium/Large]
Idea 2: [Name] [Same structure] Idea 3: [Name] [Same structure] Idea 4: [Name] [Same structure] Idea 5: [Name] [Same structure] Next Steps
  • Validation experiments for top 2 ideas
  • Detailed design exploration
  • Engineering feasibility assessment

​
Edge Cases

  • Dominant perspective: Ideas from one discipline consistently win. Actively ensure cross-functional perspectives are valued equally.
  • Incremental vs. breakthrough ideas: Designers and engineers may lean radical; PMs often anchor to incremental. Both are valuable for different reasons.
  • Constraint awareness mismatch: Engineers identify barriers others miss; PMs may underestimate effort. Use disagreement as a signal to dig deeper.
  • Missing user research: Ideating without customer insight often produces self-referential ideas. Return to user data to ground prioritization.
  • Revisiting ideas: Good ideas killed in previous rounds may deserve another look if circumstances changed. Maintain an archive.