Koji for Product Managers

The Bottom Line

Product managers are expected to be the voice of the customer, but most PMs talk to fewer than 10 customers per month. Koji gives PMs a superpower: the ability to run deep, structured customer conversations at scale — validating every major decision with real evidence rather than intuition and Slack polls.

The PM Research Gap

You know the feeling. You're in a roadmap review, advocating for a feature, and someone asks: "How many customers actually want this?" Your answer is some combination of support tickets, sales requests, and a handful of conversations. It's enough to have an opinion, but not enough to have confidence.

The math doesn't work for traditional research:

• 1:1 interviews: You can do maybe 5-8 per week alongside your other responsibilities. That's 20-30 per month at best — across all your research needs.
• Hiring a researcher: Great if your company has budget for one. Many product teams don't.
• Surveys: You can scale them, but "Rate this feature 1-5" doesn't tell you what to actually build.
• Customer advisory boards: 5-10 power users who don't represent your full market.

What This Means in Practice

Without sufficient customer evidence, PMs make decisions based on:

• The last 3 customer calls (recency bias)
• Sales team requests (squeaky wheel bias)
• Competitor feature launches (reactive roadmapping)
• Leadership opinions (HiPPO — Highest Paid Person's Opinion)
• Personal intuition (sometimes right, impossible to defend)

Koji closes this gap by letting you run 50-200+ structured interviews for any decision, without it consuming your entire week.

How PMs Use Koji Across the Product Lifecycle

Discovery: Understanding Problems Worth Solving

The scenario: You're exploring a new problem space and need to understand whether a pain point is real and widespread.

How Koji helps: Set up a 12-15 minute interview study targeting your user segment. The AI interviewer explores their current workflow, pain points, and workarounds. Launch to 50-75 participants and have synthesized insights within 3-5 days.

What you get: A clear picture of problem severity, frequency, and current solutions — with enough data points to identify patterns versus noise.

Validation: Testing Solutions Before Building

The scenario: You have a feature concept and need to know if it resonates before committing engineering resources.

How Koji helps: Create a concept testing study with your mockups or descriptions as stimulus materials. The AI interviewer captures initial reactions, explores fit with existing workflows, and probes willingness to change behavior.

What you get: Go/no-go confidence backed by 50+ customer reactions, plus specific refinement suggestions that improve the concept before a single line of code is written.

Prioritization: Building the Right Roadmap

The scenario: You have 15 features competing for 3 spots on the quarterly roadmap.

How Koji helps: Run a feature prioritization study across customer segments. Instead of abstract ranking, the AI captures workflow context that reveals which features solve the most painful problems for the most valuable customers.

What you get: An evidence-based priority stack with segment-level breakdowns, verbatim customer quotes for stakeholder alignment, and confidence that you're building what matters most.

Launch: Understanding Adoption and Satisfaction

The scenario: You've shipped a feature and need to know if it's landing.

How Koji helps: Run post-launch interviews with early adopters and non-adopters. Understand what's working, what's confusing, and why some users haven't engaged.

What you get: Actionable feedback for iteration and a leading indicator of feature success before you have enough quantitative data to be significant.

Retention: Preventing Churn

The scenario: Your churn rate is climbing and you need to understand why.

How Koji helps: Interview churned customers (they're more likely to participate in a 15-minute AI interview than schedule a call with your team). Explore the journey from consideration to cancellation.

What you get: A churn driver taxonomy that informs both product fixes and customer success interventions.

Setting Up Koji for Your Product Team

1. Create a Research Template Library

Build reusable discussion guides for common PM research needs:

• Problem discovery template: Workflow exploration → pain point identification → workaround mapping
• Concept testing template: Context setting → concept reaction → competitive comparison → intent signal
• Feature prioritization template: Current usage → unmet needs → feature reactions → priority ranking
• Post-launch template: Feature awareness → adoption barriers → satisfaction → improvement suggestions
• Churn analysis template: Initial expectations → usage history → decision point → competitive switch → win-back conditions

2. Integrate with Your Product Workflow

Embed Koji research into your existing processes:

• Sprint planning: Run a quick 30-interview validation study before committing to a major feature
• Quarterly planning: Run comprehensive 100+ interview studies to inform roadmap priorities
• Post-launch: Automatically trigger interview invitations when users engage (or don't engage) with new features
• Continuous discovery: Keep an always-on interview link for ongoing customer conversations

3. Build Stakeholder Buy-In

Share Koji insights in formats that resonate:

• For engineering: Customer verbatims that illustrate the problem, making requirements feel real rather than abstract
• For leadership: Quantified themes with segment breakdowns that connect to business metrics
• For sales: Competitive intelligence and feature positioning language straight from customer conversations
• For design: Workflow descriptions and pain point narratives that fuel empathy and ideation

The PM's Weekly Koji Workflow

Monday: Review completed interview analyses from previous week's studies. Flag key insights for team standup.

Tuesday-Wednesday: Launch any new studies needed for current sprint decisions. Design discussion guides for upcoming research needs.

Thursday: Share synthesized findings with stakeholders. Update prioritization based on new evidence.

Friday: Plan next week's research agenda. Review recruitment pipeline for ongoing studies.

This cadence means you're always operating with fresh customer evidence — not stale assumptions from last quarter's research sprint.

Koji vs. PM Research Alternatives

Common PM Objections (and Why They're Wrong)

"I already talk to customers enough"

If you're doing 5-10 calls a month, you're making roadmap decisions based on a sample size that wouldn't pass a high school statistics class. Koji doesn't replace your customer calls — it supplements them with the scale needed for confident decision-making.

"AI can't interview as well as I can"

You're right that your contextual knowledge adds value. But Koji's AI interviewer doesn't have your calendar constraints, scheduling headaches, or unconscious biases. Use Koji for systematic research and reserve your personal interviews for the highest-value strategic conversations.

"My team won't read research reports"

Koji's synthesis produces scannable, actionable outputs — not 40-page reports. Key themes with supporting quotes, segment breakdowns, and recommendation summaries. Share the 2-minute version in Slack and link to the full analysis for those who want depth.

"We can't afford another tool"

Calculate the cost of one wrong feature priority: engineering time, opportunity cost, and customer disappointment. A single Koji study that prevents a misguided feature investment pays for itself many times over.

Getting Started: Your First Koji Study as a PM

1. Pick your biggest open question: What decision are you making in the next 2 weeks that customer evidence would improve?
2. Create a 10-question discussion guide: Start with workflow context, then explore the specific question
3. Target 40-50 participants: Enough for reliable patterns, not so many that analysis overwhelms
4. Launch and wait 3-5 days: Let the interviews run asynchronously
5. Review the AI synthesis: Focus on surprise findings — the things customers said that you didn't expect
6. Share with your team: Use verbatim quotes to bring customer perspectives into your next planning session

The PMs who run their first Koji study rarely go back to gut-feel prioritization. Once you've experienced making a decision backed by 50 customer conversations instead of 5, the difference in confidence is visceral.

Frequently Asked Questions

How much time does Koji actually save a PM?

Most PMs report saving 8-12 hours per research cycle compared to scheduling, conducting, and synthesizing 1:1 interviews manually. The bigger value is volume: you get 10x more interviews in the same time, producing dramatically more reliable insights.

Can I use Koji if I've never done formal user research?

Absolutely. Koji's discussion guide templates and AI-powered synthesis make it accessible to PMs without research training. Start with a simple problem discovery study and expand your methodology as you get comfortable with the output.

How do I convince my manager to adopt Koji?

Run one study and share the results. The most effective pitch isn't theoretical — it's showing leadership a synthesis of 50 customer conversations alongside the current evidence base (usually a few anecdotes and a survey). The contrast sells itself.

Does Koji work for B2B and B2C product teams?

Yes. B2B teams particularly benefit from the async format that reaches busy executives. B2C teams benefit from the scale — running 200+ consumer interviews quickly. The discussion guide design differs, but the core workflow is the same.

How does Koji integrate with product management tools?

Koji's insights can be exported and shared via your existing tools — Notion, Confluence, Jira, Linear, or Slack. The synthesized themes and customer quotes integrate naturally into product specs, roadmap documents, and sprint planning artifacts.