Make the product successful by keeping every meeting that decides it

Customer discovery call

What has to survive it is the problem in the customer's own words, verbatim, because that is what the PRD quotes and what a paraphrase destroys. You cannot run the interview and take verbatim notes at the same time, and every tool built for this assumes a video call, so an in-person interview is captured by nothing at all.

With Earkeep: mic and system audio are already recording, all day, so the interview in a room lands exactly the way a video call does, with nothing to invite and no button to hit before the customer starts talking. Audio is transcribed on your device and never written to disk, which is what makes it usable for the customer and pricing conversations you would not put through a vendor cloud at all. How always-on works →

Stakeholder sync

What has to survive it is the verbal commitment: sales agreeing to a scope tradeoff, support conceding a workaround is acceptable, legal drawing a line. None of it was scheduled as an interview, so nothing captured it, and the roadmap change it justifies has no evidence behind it a week later. Half of those commitments are not even in the meeting, they land in the huddle someone opens straight afterwards to check one thing.

With Earkeep: connect Google Calendar, Apple Calendar, Outlook or any ICS URL and the recurring syncs start, end and title their own spans, so the weekly load costs you no decisions at all. That follow-up huddle is on the same continuous timeline, and you select it as a span once you realise it mattered, which is usually the only moment you can tell. How calendar spans work →

Exec review

What has to survive it is the exact decision and who made it. Paraphrase is precisely what makes a settled decision re-litigable next quarter, and by the time you need the sentence, months have passed and the meeting was one of the five you had that day.

With Earkeep: you rarely know in advance which exchange will turn out to matter, so you mark the span afterwards, once you do. Transcripts are kept as plain dated files in a folder you own, so "what exactly did we decide, and who said it?" is a search on your own disk in year three, not an appeal to memory. From what was said to what you know →

The rest of the week

Those three are where the product is decided. They are not where the week goes: roughly half a PM's working day is meetings on Product Management Exercises' own rule of thumb, and Pragmatic Institute's survey of nearly 2,500 PMs put 27% of the time on strategy against 73% on tactics.

Earkeep does not ask you to choose between them. Every recurring row above starts, ends and titles its own span from your calendar, so a nine-meeting day ends as nine named transcripts with nothing left to file.

Writing them up is a separate job from keeping them, and the templates are free: templates for all five sprint ceremonies, and the planning and OKR template for the quarterly roadmap review, which records the sequence you rejected as well as the one you agreed.