Priya Has Been Running the Product Roadmap for Fourteen Months. Manager OTG Has Presented It Five Times.

Priya has already read the Linear board, replied to four Slack threads, and cleared a blocker before 8:00 AM on Monday. The blocker involved a dependency on the payments team that Marcus had promised to own in the Q2 planning doc and then did not. She resolved it herself at 7:38 AM without mentioning it to anyone. There was no point.

At 8:06 AM, Manager OTG messages her: "Hope you had a restful weekend! Quick ping when you have a sec ๐Ÿ™"

She does not respond until 10:14 AM because she is running a standup with three engineers, a QA lead, and a product designer named Kira who is leaving in six weeks. Priya already knows she will need to backfill Kira. She knows she will be doing it with the same headcount. She has known both things since April. Manager OTG does not know Kira is leaving.

The roadmap

She has been at Lumenwave for fourteen months. In that time the product roadmap has lived in a shared Google Sheet, then a Confluence page, then a Notion database, then a Linear board โ€” each migration Priya's decision, because something was wrong with the previous system and she could name specifically what it was. Manager OTG was informed of each migration after the fact. He sent a ๐Ÿ™ each time.

He has presented the roadmap in five company all-hands โ€” the kind that run 52 minutes and end with no decisions. The slide deck always has the same title: "Product Vision: Q[N] and Beyond." It has a two-by-two matrix. Priya built the two-by-two. She also built the bullet points under it, the dependencies table on slide eleven, and the three-sentence executive summary at the top, which Manager OTG calls his "talking points."

He adds one thing to the deck before each all-hands. A quote. Q3 was Peter Drucker. Q4 was an Economist article he cannot locate now. Q1 was something from LinkedIn he is fairly certain is misattributed to Einstein. He sends each quote to Priya at 9:17 PM the night before the presentation with the subject line "Thoughts?"

She has never replied to the 9:17 PM email. The quote always appears on the slide.

The launch

The product launched April 9th. Not the full scope โ€” the scoped version Priya had argued for in November, in a 47-minute meeting that was supposed to be fifteen, in which she laid out the tradeoffs on a slide she built at 11:30 PM the night before because she'd realized, at 11:22 PM, that Manager OTG would need a slide to follow the argument. The scoped version shipped four weeks ahead of the original timeline. The original timeline had been Manager OTG's idea.

His green dot was on for the entire launch window because his mouse jiggler was plugged in. He was, in fact, at a Westin in Phoenix presenting a partnership deck that would not close. Priya ran the launch from a shared Notion war room doc she had set up at 7:58 AM. Fourteen people were in that doc at once.

Manager OTG was not one of them.

At the all-hands in May, he said: "We shipped. The team delivered. I'm really proud of what we built here."

The skip-level

Priya has a 1:1 with Dana every other Wednesday at 3:00 PM. Dana arrives on time. Priya pulls up her Notion doc. They talk about the roadmap, about capacity, about the three features that are three sprints behind because Marcus keeps requesting "scope adjustments" โ€” a phrase that, in this context, means rewrites.

Manager OTG is not in these meetings. He is aware they happen. He asked Priya once if she was "getting what she needs from them" โ€” which was, structurally, the most he had asked about her work since onboarding.

She said yes.

She was.

The thing about Priya โ€” and, for that matter, Greg โ€” is that she does not complain about any of this. Not to Dana, not to the #venting Slack channel that was archived in February, not in the kind of 360-review language that means something if you know the code. She rates things accurately. She leaves the comments field mostly blank. She moves on.

The LinkedIn post

The week of the launch, he posted: "Thrilled to share that we shipped [Product Name] this month at Lumenwave. Huge team effort. Proud of the work we're doing." Eighty-two people liked it. Three of them were on Priya's team. She could see their names in the notification.

She did not comment. She did not react. She updated the Linear board to mark Phase 2 planning as "In Progress" and sent the engineering team a Slack message at 7:51 AM the following Monday.

Numbered list. Eleven items.

The first was already done.