Northstar · Customer review
Tomorrow · 10:00
ProductProblem brief
Turn customer feedback into a problem brief
Give the team a clear problem, affected workflow and evidence to investigate.
See how it’s done.
Example walkthroughai.meetric.comProblem brief
Home
Ask Meetric
Upcoming meetings
Team review
Tomorrow · 14:00
Recent conversations
Northstar · Account review
7 Oct · 24 min
Northstar · Service call
11 Oct · 18 min
1 / 7Open New AI chat
Read narration
- Open New AI chat
Before choosing a feature, understand the work the customer wants to change. Open New AI chat to turn Maya’s reporting interview into a grounded problem brief.
- Choose the evidence
Start with the interview evidence available to you. You want Maya’s workflow, friction and desired outcome, with room for unanswered questions.
- Ask for a problem brief
Ask who is affected, what they do now and where the repeated work happens. Submit the question while leaving the solution choice open.
- Review the problem
Maya exports to a spreadsheet each Friday and rebuilds the same report. That repeated work is the problem to investigate. Open the source to check her desired outcome.
- Open the interview
Maya prepares the weekly support report and wants managers to receive a consistent view. Read the transcript to hear what she wants to change.
- Read the evidence
She wants the same weekly view without rebuilding it. The spreadsheet describes today’s workflow, but does not decide the solution. Return to the brief.
- Start discovery with a grounded problem
Give the team a problem grounded in Maya’s work. Explore solution options against the desired outcome, with the interview ready whenever someone needs the context.
Read the walkthrough
Illustrative product walkthrough using example conversations.
- Before choosing a feature, understand the work the customer wants to change. Open New AI chat to turn Maya’s reporting interview into a grounded problem brief.
- Start with the interview evidence available to you. You want Maya’s workflow, friction and desired outcome, with room for unanswered questions.
- Ask who is affected, what they do now and where the repeated work happens. Submit the question while leaving the solution choice open.
- Maya exports to a spreadsheet each Friday and rebuilds the same report. That repeated work is the problem to investigate. Open the source to check her desired outcome.
- Maya prepares the weekly support report and wants managers to receive a consistent view. Read the transcript to hear what she wants to change.
- She wants the same weekly view without rebuilding it. The spreadsheet describes today’s workflow, but does not decide the solution. Return to the brief.
- Give the team a problem grounded in Maya’s work. Explore solution options against the desired outcome, with the interview ready whenever someone needs the context.
When to use it
A feature request has reached Product without enough context to design a solution.
Start with
- Customer interviews or account conversations
How to do it
On Home, ask for a problem brief from the customer conversations behind the request.
Review the affected user, current workflow, friction and desired outcome.
Open the sources and check the brief with Design and Engineering before choosing a solution.
Ask Meetric
Write a problem brief from Northstar’s reporting conversations. Describe who is affected, their current workflow, friction and desired outcome. Cite the evidence and leave solution choices open.
Try it with your team’s conversations.
See the sources, the output and the steps that make this useful for your team.