Product R&D Agent

Product R&D is the study type for product innovation work: market trends, user needs, and cross-domain inspiration, ending in ideas worth testing. It differs from User Research (which is about understanding specific people) and Fast Insight (which produces content, not innovation material).

What Product R&D produces

Product R&D runs a complete product-innovation workflow:

1. Market trend scan — what's happening in the category, what signals matter, what competitors are doing.
2. User need synthesis — what jobs users are hiring the product to do, what frustrates them, what they wish existed.
3. Cross-domain inspiration — patterns from other industries that could be applied here.
4. Idea generation — concrete product or feature concepts that emerge from the previous steps.
5. Validation prep — framing for how each idea could be tested.

The output is structured research material that feeds directly into product decisions, not a podcast or generic insight report.

How it differs from User Research

User Research asks "what do our users think and do?" Product R&D asks "what should we build?"

The methods overlap — both might use Scout, Interview, and Discussion — but the goal is different. User Research ends with insight about people. Product R&D ends with ideas worth prototyping.

If you find yourself saying "we need to understand this user group better," use User Research. If you're saying "we need a new product direction," use Product R&D.

How it differs from Fast Insight

Fast Insight produces content (a podcast) for an external audience. Product R&D produces research material for an internal product team.

What a typical run looks like

A Product R&D run typically goes through several phases:

• Discovery — Scout scans social and web for what's happening in the category.
• Synthesis — Interview or Discussion with personas to test emerging hypotheses about what users need.
• Cross-pollination — pulling patterns from other industries to suggest unconventional ideas.
• Idea clustering — organizing raw observations into 3–10 distinct concepts.
• Output — a structured document with market context, user needs, inspiration, and the idea set.

When Product R&D is the right tool

Use Product R&D when:

• You're entering a new category or repositioning an existing one.
• You need to convince stakeholders with both market context and concrete ideas.
• You want inspiration from other industries, not just optimization of what you already have.
• You're at the front end of an innovation cycle (1–2 years out from launch).

Skip Product R&D when:

• You already have specific user questions to answer — use User Research.
• You're optimizing an existing product — use User Research or Interview.
• You need shareable content for an external audience — use Fast Insight.

Limits

• Product R&D produces ideas, not validated concepts. You'll still need to test prototypes with real users before committing.
• The "cross-domain inspiration" step is the most variable in quality. Sometimes the AI surfaces genuinely useful patterns from unrelated industries; sometimes it stretches analogies too far. Treat the inspiration set as a starting point, not a final answer.
• A full Product R&D run is more expensive than a single Interview or Discussion. Use it when the decision is high-stakes enough to justify the cost.

A worked example

You say: "Help us think about what a meditation app for retirees should look like in 2026."

Product R&D scans the wellness space, researches retiree-specific needs (sleep, loneliness, cognitive maintenance), pulls inspiration from healthcare and community products, and produces 5–8 distinct product concepts. You pick 2 to prototype and validate through a separate User Research study.