Require preparation now
May be skippable
Across 4 meetings
Overdue for outreach:
Vikram Sood, Siddharth Bose, Priya Sharma
Team Standup
9:00 AM · 15 min · 4 attendees
Design Review: Mobile Checkout
10:30 AM · 60 min · 3 attendees
Q3 Product Strategy Sync
1:00 PM · 30 min · 2 attendees
Weekly Status Update — Growth
2:30 PM · 60 min · 5 attendees
1:1 with Priya Sharma
4:00 PM · 30 min · 1 attendee
Engineering Incident Debrief
5:30 PM · 60 min · 3 attendees
Q3 Product Strategy Sync
Tuesday, June 2 · 1:00 PM – 1:30 PM · 30 minutes
Arjun
Priya
Generated at 12:42 PM
THE SITUATION
You're heading into a critical cross-functional review of the Q3 roadmap. Arjun last raised concerns about feature prioritisation three weeks ago, and Priya's team is currently blocked on two dependencies from your side — neither of which has had an update in 10 days. This meeting will either unblock them or escalate upward to leadership.
THE PEOPLE
Arjun Mehta
arjun@zepto.com
Context
Last spoke 3 weeks ago in a thread about Q2 retrospective findings. He flagged that the discovery feature shipped 2 weeks late and wants a tighter process going forward. Has not responded to your follow-up from May 15th.
Tone Hint
Data-driven and direct. Comes prepared with numbers. He prefers you lead with data, not narrative — open with metrics if you have them.
Previous Meetings (4)
Priya Sharma
priya.s@zepto.com
Context
Her last email (May 18th) asked for an update on the checkout API integration timeline. You haven't replied. She also CC'd her manager on the second follow-up — a sign of escalating urgency.
Tone Hint
Collaborative but will escalate quickly if she feels ignored. Acknowledging her pending ask before the agenda will defuse the tension immediately.
Previous Meetings (2)
OPEN THREADS
Checkout API integration timeline — Priya Sharma
You haven't replied to her email from May 18th. It has been 12 days. She CC'd her manager on May 22nd.
→ Address this in the first 5 minutes. Even a 'we're targeting June 10th' closes the loop and resets the tone.
Q2 retrospective action items — Arjun Mehta
Two process changes Arjun requested in the May 1st thread are unresolved. No formal response was sent.
→ Have a quick update ready on the two process changes — even 'still in progress, ETA next sprint' is enough.
Discovery feature post-mortem
No post-mortem has been published for the delayed discovery feature despite Arjun's May 3rd request.
→ Acknowledge this is overdue and commit to a date. Don't let it come up as a surprise.
Q3 roadmap draft shared on May 12th
You shared a draft roadmap 18 days ago. Neither Arjun nor Priya has commented on it in Docs.
→ Reference the specific sections you want their input on — they may not have read it yet.
HOW TO OPEN
"Before we go through the roadmap, I want to acknowledge Priya's question on the API timeline — we're targeting June 10th, and I'll send the detailed breakdown by end of day. Arjun, I also want to address the Q2 retro action items before we move forward."
— Suggested by Briefcase based on 4 email threads
MEETING ASSESSMENT
Purpose
Finalise Q3 roadmap priorities, unblock two pending engineering decisions, and resolve the checkout API integration timeline that has been escalating via email for 12 days.
Worth Having?
Four unresolved decisions require real-time alignment. Email has already failed twice.
Could Be An Email?
Active escalation in email thread suggests async has already broken down.