Team 5: One Pager Draft

Pip

Description: What is it?

Pip is a proactive meeting assistant tool for product managers. The product is a downloadable desktop app and chrome extension that 1) can transcribe and summarize meetings, suggesting actionable insights and 2) proactively completes tasks that arise throughout the meeting (drafting emails, slack messages, sharing information across stakeholders, generating draft documents, and other digital workflows). The tasks are then sent for approval by the user. 

Problem: What problem is this solving?

This product is solving for the problem of an overload of meetings that PMs face, and the need to keep track of information across different teams and stakeholders, alongside the miscellaneous tasks that may bog down their ability to execute efficiently. Pip aims to help take off some of that burden to streamline the process so that the PM can focus on using their relevant skills on strategy, execution, etc. 

Why: How do we know this is a real problem and worth solving?

We know this is a real problem from multiple interviews completed with product managers, where one of the most prominent problems that came up was around the volume of meetings that PMs are a part of. In addition, many PMs also pointed to the potential for AI to help automate some of the less glamorous manual tasks that may take up valuable time. We believe that integrating these two problems into one solution will be valuable for PMs. 

Success: How do we know if we’ve solved this problem?

We will know if we’ve solved this problem based on both verbal user interviews, and the metrics that we will track on usage. For example, if our product becomes deeply integrated into a PMs workflow, and they confirm that it has been saving them time and effort, that means that our product is solving this problem (and if not, vice versa). 

Audience: Who are we building for?

We are building for product managers, especially APMs and early career PMs at tech companies who spend a good amount of their day to day time in back-to-back meetings. These are people whose calendars are always packed with standups, syncs and various stakeholder check-ins and who end up losing time afterward on small to-dos such as sending follow-up emails, scheduling next step meetings and writing up notes. For our first version, we are focusing on PMs who are on Mac and already comfortable trying new productivity tools since they are the ones most likely to install a desktop app and give it a real shot. As for who pays, we believe the individual PM should be the user but that the company should be the buyer. Our plan right now is a free tier so individual PMs have the chance to try Pip on meetings they already conduct, and then a paid team plan that companies buy once at least a small portion of the PMs on their squad starts seriously integrating it into their routines, which also helps with the IT and privacy approvals that a meeting tool needs anyways. 

What: Roughly, what does this look like in the product?

Pip is a Mac desktop app with a small floating mascot that sits on yout screen during meetings. When a meeting starts, the PM hits Start meeting and Pip listens in, transcribing as the conversation goes. Instead of just giving a summary at the end, Pip pulls out the small admin tasks that came up and drafts them for you so that things like a follow-up email, a calendar invite, a status update or meeting notes already exist almost immediately upon the end of your meeting. Afterwards, the PM gets a short list of drafts they can quickly review, edit and approve. The idea is captured in our tagline: “Big ideas are yours. The little things? Mine.” Later, we also want to connect Gmail, Calendar and Slack so that approving a draft actually sends it to the appropriate stakeholders. 

How: What is the experiment plan?

Our biggest question is whether Pip’s drafts are actually good enough to send with light edits since if PMs end up rewriting everything then there’s no real time saved. To test this, we’ll have around 5 PMs or APMs run Pip on a real or role-played meeting and then review the drafts it produces. We’ll measure how many drafts get approved with only minor edits and how many real tasks Pip missed, and we’ll consider it a success if at least 60% of drafts are approved with light edits and the PMs say they’d use it again in this initial iteration. 

When: When does it ship and what are the milestones?

We already have a v0 of Pip working as a Mac app so the next step is running our draft test with real PMs over the course of this week. Based on what we learn, we’ll tighten up how Pip picks out tasks and writes drafts, and we’re aiming to have an improved version ready for our end of quarter demo.

One idea from this week’s reading: We used Lenny’s point that a one-pager should lead with an experiment plan instead of a full build spec, and you can see it in our How section. There we name our riskiest assumption (whether Pip’s drafts are good enough to send with light edits) and set a clear bar of 60% approved drafts.

Avatar

About the author

Leave a Reply