Voice notes to CRM

A product design question from a product manager interview, set at Kahiye, a fictional b2b sales software company.

The question

Skills this case tests

A starting structure

Who writes vs who reads the CRM → pick one user → a rep's day between shops → which fields can be wrong and which cannot → ideas → v1 with a correction step → metrics, cost per note

How to approach this case

First ask what the customer is paying for: better data, more orders captured, or less time chasing reps. That tells you whose problem comes first. The people who enter CRM data and the people who read it are often different, so separate them and pick one to design for. Follow a rep through a real day of shop visits and notice where logging breaks down, and when. For an AI feature, ask how accurate the model is today and on which kinds of input, because not every field costs the same when it is wrong. Plan how users will spot and fix mistakes, what happens with no network, and what each processed note costs against what a seat earns. A strong close covers a narrow v1, a north star about complete and timely logs, a guardrail on errors, and the cost per user.

The full method for product design (product sense) questions · A worked example answer

After the mock interview you get scores on five skills, what to fix with quotes from your answers, and the ideal path for this case.