Turning a broad direction into a focused bet
Research surfaced more directions than one release could serve well. From here, the PM and I sat down to decide on high level product directions and shape the scope:
🌟
Prioritize meeting follow-ups
A mandatory job in every rep's workflow, the highest-frequency email tied directly to a meeting Sybill already captured.
🌟
In-app vs Gmail extension
Embedding email generation in the Meetings experience reps already lived in daily would reinforce the core workflow, and deepen stickiness in Sybill rather than in someone else's inbox.
🌟
Integrate with existing tools
Sending is high-stakes, and reps want full control in the tools they trust. So Sybill owns the drafting and hands off cleanly to the client they already send from.
🎯
Project goal
Establish Sybill as more than a notetaker, an AI assistant reps turn to for real deal work, by giving them a seamless email workflow inside the product, starting with meeting follow-ups.
Under the defined project goal and decisions, we also decided to solve the following pain points & needs to make sure this version brings true value to users:
📝
- Manual drafts miss what matters (pain)
Writing by hand, reps often left out the deal context or the prospect's open questions that made an email actually land. - No easy way to edit the draft with AI (need)
Reps almost always want to adjust a draft before sending, and without a way to refine it in place, they fell back to outside tools. - The draft was trapped outside the inbox (pain)
Even a strong draft had to be copied and pasted into Gmail or Outlook by hand, breaking the flow every time.
After aligning with the team, I mapped the end-to-end user flow and began ideating solutions and high-level requirements for each step, then make design mocks to visualize ideas.
With the designs ready and prototypes built, I ran user testing to pressure-test it against how reps actually work, and two refinements came out of it, both shaped the design that followed:
📝
- Follow-ups need to land in the right thread (need)
Whether a reply belongs in an existing thread or a fresh email changes how it reads, and reps needed that handled, not guessed. - No easy way to edit the draft with AI (need)
Reps almost always want to adjust a draft before sending, and without a way to refine it in place, they fell back to outside tools.