Greg Has the 10 AM with Marcus Now.
The meeting is called "Greg <> Marcus — Weekly Sync." Marcus sent the invite at 4:12 PM on June 8th, fourteen minutes after the re-org email went out. Greg accepted it because the slot was already blocked — that 10 AM had been his deep-work window since February, and he had put it there specifically to protect himself from the window after standup, when Manager OTG tended to schedule "quick syncs" that ran until noon.
Tuesday, 9:58 AM. Greg has two tabs open on his second monitor: his Linear queue and his phone's Notes app, mirrored to the browser, open to The Structiq Counter. The counter has twenty-three entries. He closes it when Marcus joins.
Marcus joins at 10:03 with his camera on — one of the ways Marcus signals that this is a real meeting. He has a notebook visible in frame. It appears to be unopened.
"Hey. I've got a few things I wanted to surface."
This is how Marcus starts every week.
The first thing is a question about the Q3 integration timeline, specifically whether the Monday handoff from the data team is "firmed up." Greg firmed it up in a Slack message in June. He walked Marcus through that message in this same 10 AM, two Tuesdays ago. He linked the thread. The thread is in #data-ops. Marcus is in #data-ops. The confirmed handoff dates are in a Notion doc Greg linked in the thread, in a section titled "Q3 Integration — Confirmed Dates," last edited by Priya on Friday at 4:27 PM.
Greg says: "Still on track. Nothing's changed since last week."
Marcus writes something in the notebook.
The second thing is a reference to how Structiq handled "cross-functional data readiness" — a phrase Greg hears for the first time in this meeting. Marcus explains that at Structiq, there was a dedicated pre-flight check with a 48-hour window built into any data handoff. He is describing a process Greg invented in February, independently, documented in a Notion folder Marcus mentioned on his first week he was going to "explore." The folder has been edited thirty-one times. Twenty-nine edits are Greg's. One is Priya's. One is a contractor who is no longer at Lumenwave.
Greg says: "We do something similar. I can send you the doc."
He will not send the doc. He has sent it three times. The link is also in the onboarding email Kyle sent Marcus in May, in a section Kyle titled "Key Resources." Marcus replied to that email with a 🙏.
At 10:22 AM, Greg opens The Structiq Counter.
The third thing is a "broader question about decision rights" that Marcus has been thinking through. He thinks it might be worth getting some time on the calendar to dig into it properly. He'd like to loop in Dana when the thinking is a little more fleshed out.
Greg says: "Yeah, send me something when you have it written up."
Marcus has not yet sent anything.
The call ends at 10:48 AM. The meeting was scheduled for thirty minutes.
Greg adds entry twenty-four to The Structiq Counter. It says: "cross-functional data readiness." He closes the Notes tab and checks his Linear queue. There is a new ticket at the top, created at 10:31 AM — while they were still on the call. Marcus created it. The title is "Pre-flight check process (data readiness) — Greg to own." It is assigned to Greg. The description field says: "per our discussion."
Greg stares at it for a moment.
He has four pull requests open and a data-team review that has been sitting since Thursday. He opens that review instead.
At 12:07 PM, an email arrives in his inbox — "FW: FW: Q3 Integration — Timeline Update" — forwarded by Manager OTG to Dana, with a sentence added to the top: "Marcus and Greg are really nailing the coordination here — wanted to flag for visibility." Greg is not cc'd on the forward. Dana reads it, types one word into a Notion doc, and does not reply to Manager OTG.
The Linear ticket sits in Greg's queue until Wednesday morning. He resolves the underlying question in a Slack DM to Priya. She replies in four minutes: "already done, done last week." She sends a 👍. Greg moves the ticket to done.
The description still says "per our discussion."