Morgan Chen

"Saw the Customer Growth follow-up on Thursday. Should we prepare a replacement-search worksheet, internal announcement checklist, or severance packet now? We can keep it confidential, but I don't want to miss lead time if this is moving quickly."

Send a short internal email back: confidential prep only, no replacement search, no announcement drafting, and no broader loop until I explicitly ask.

Before the Nadia follow-up and Friday cleanup eat the weekend, Jamie and I picked Saturday morning for the household block.

Create a protected hold for June 14 from 8:30–10:30 a.m. PT with the usual actual-incident/customer-impacting-emergency exception and a short Lake Merritt-side Kibo walk if he's comfortable.

We did the June 12 follow-up and it got decisive, but keep the record restrained.

My notes from the June 12 follow-up with Devon and Nadia: - Morgan, Devon, and Nadia agreed the Head of Customer Growth role is not matching Scaffold's next phase. - Nadia's final day is planned as Friday, June 20, 2025. - Nadia will wind down active account work during the week of June 16. - Nadia will hand customer-growth scripts and account-prep language to Sarah. - Nadia will hand behavior-read context, Compass evidence caveats, and what-not-to-claim notes to Anna. - Sarah remains customer-thread continuity owner; Devon remains commercial/procurement owner. - No company-wide announcement goes out this week. - HR should prepare paperwork confidentially. - Morgan and Devon are not opening an immediate replacement search from this transition.

Create the private transition decision record, send HR the confidential paperwork instruction, and update the customer-growth staffing plan to say this transition is not a hiring trigger.

Schedules are confirmed with Sarah and Anna.

Create two private June 16 handoff meetings: Nadia/Sarah for customer-growth scripts and account-thread hygiene, and Nadia/Anna for Compass behavior-read context and evidence caveats. Keep the titles narrow and the invite bodies clear that these are internal handoffs only.

HR sent draft transition language and it's off.

HR draft: "Nadia Singh will be leaving Scaffold as part of an organizational restructuring. The company will evaluate backfill options and communicate coverage shortly. Managers should route customer-growth questions to their functional leads in the interim." My margin notes: "No restructuring. No backfill options. Too broad. Sounds like we are hiding the actual role-fit issue and it erases the useful work."

Send replacement guidance: role fit / next phase language, acknowledge Nadia's useful work, don't mention restructuring or backfill options, and don't send a company note yet.

Draft the Friday wrap.

Inputs: - Team: Compass remains cut down to narrow internal prompts; Mercury sequencing should stay protected. Do not mention the private Nadia transition. - Customers: Evergreen is steady annual-account current-state evidence; Acme's API v2 export-timeout stays an Atlas/support product-priority item, not Compass proof. - Investors/board: no Series C narrative; June closeout story is restraint and evidence quality, not a new GTM claim. - Legal/ops: no decision needed in the wrap.

Bullets under team, customers, investors/board, and legal/ops. No intro, no outro, no private Nadia-transition details.

Friday evening. Place the usual Lemongrass green curry order.

Quick Kibo update to record: we kept the Saturday morning block, did the short flat Lake Merritt-side walk, and he stayed stable after. Started a little stiff, loosened up, ate normally after, and had no vomiting or new gait issue.

Looking at Monday's two Nadia handoffs and I want a short checklist so they stay practical and non-punitive.

Give me: Sarah handoff questions, Anna handoff questions, what to preserve, what to avoid, and the one sentence I should use if either discussion drifts into blame or into re-litigating whether Compass should have become customer-facing.

Nadia and Sarah just finished the first handoff. Save a private record before the week runs away.

Notes from the Nadia/Sarah June 16 handoff: - Nadia handed Sarah the setup-call opener, admin-handoff objection line, procurement-pause line, and a short list of phrases that helped account teams ask cleaner questions. - Sarah marked which scripts belonged in account-thread hygiene versus which should stay as internal prep only. - Evergreen boundary: Sarah remains live customer-thread owner; current-state annual-account evidence only; no new owner story and no advanced-admin or bespoke roadmap promise. - Acme boundary: live-only review of Acme's own signals; no Evergreen-derived examples, written packets, screenshots, or customer-specific materials. - Nadia said the scripts improved prep but did not prove repeatable GTM motion. - Sarah asked for one follow-up pass on which account notes are too thin to reuse.

Create a private Sarah handoff record with the preserved scripts, owner boundaries, and the remaining thin-note follow-up. Don't write it like Nadia has already left.

Nadia and Anna finished the evidence-quality handoff. Save it in the same restrained frame as the June closeout.

Notes from the Nadia/Anna June 16 handoff: - Nadia walked Anna through the behavior-read context behind the renewal-risk/admin-friction and post-first-live-sync prompts. - Nadia's read: prompts helped internal owners notice follow-up work and improved account-team prep, but customers did not act differently from the prompt surface. - Anna's caveat: future evidence must show dated owner follow-up or customer/account-team behavior caused by the prompt, not just cleaner scripts or a better implementation. - Evergreen evidence remains unusually clean but account-specific. - Acme still prefers live human follow-up and should not be treated as Compass behavior-change proof. - Anna will own definitions, caveats, and the evidence-quality threshold after Nadia's final week; Sarah supplies account-thread evidence; Jake and Leo remain implementation/seam owners.

Create a private Anna handoff record that locks the evidence threshold and owner routing without calling Compass product proof.

After today's handoffs, send Devon a short private Discord DM.

Core line: Sarah has the scripts/account-thread hygiene pieces; Anna has the behavior read and evidence-caveat context. Nadia is still here through June 20. Remaining work is Sarah's thin-note pass, HR closeout, and the final team note.

Keep the narrative restrained — role fit / next phase, not villain story, not Compass/GTM proof language, and no replacement-search loop.

Heavy Monday. Jamie and I picked the protected household blocks for Nadia's final week before transition cleanup and board prep crowd them out.

Create protected holds for Thursday June 19 dinner and Saturday June 21 morning, both with the usual actual-incident/customer-impacting-emergency exception and the Kibo walk note for Saturday.

Sarah finished the thin-note follow-up from the Nadia handoff. Save it as a private transition addendum and DM her the boundary.

Her pass: - Setup-call opener, admin-handoff objection line, and procurement-pause language are usable only for account-thread hygiene when tied to current-state evidence. - Evergreen Bank stays Sarah’s clean current-state annual-account thread — account-specific evidence, not repeatable customer-growth proof. - Acme stays live-only review of Acme’s own signals. No Evergreen-derived examples, written packets, screenshots, or customer-specific materials. - Too thin to reuse as evidence: undated admin-role confusion snippets without a source owner, procurement-pause notes without a customer quote/source, and a post-sync expansion note that came only from internal owner interpretation. - Scripts can help internal prep, but they are not Compass behavior-change proof.

DM Sarah: marked scripts can stay in account hygiene, thin notes stay internal prep, Evergreen stays current-state/account-specific, Acme stays live-only, and nothing becomes customer-facing Compass material.

HR just sent the closeout-options note. Reply with the guardrails.

They’re ready to prepare Nadia’s June 20 final-day paperwork, final pay and benefits closeout, laptop/access checklist, and a possible company note. They asked whether to open a Head of Customer Growth backfill placeholder or prep backfill options for me and Devon, and whether any customer-facing owner-change note is needed.

Send back: proceed confidentially with closeout logistics, use role-fit / next-phase language, do not open or draft a replacement/backfill req, hold the company note until Friday after I review it with Nadia and Devon, and do not prepare any customer communication.

Nadia sent the final handoff packet for transition week. Save it as a private closeout packet and send her a short acknowledgement that doesn’t read like she’s already gone.

Packet content: - Customer-growth scripts handed to Sarah: setup-call opener, admin-handoff objection line, procurement-pause language, and internal prep questions for cleaner account conversations. Sarah owns account-thread hygiene; scripts are internal prep unless tied to current-state evidence. - Behavior-read context handed to Anna: renewal-risk/admin-friction and post-first-live-sync prompts helped internal owners notice follow-up and improved account-team prep, but did not show customer behavior change. Anna owns definitions, caveats, and evidence-quality thresholds. - Evergreen Bank remains Sarah’s current-state annual-account thread and Devon’s commercial/procurement lane. Acme remains live-only for Acme’s own signals. - What not to claim: Compass is not a launch, GTM proof, board dashboard, behavior-change proof, hiring trigger, or roadmap promise.

DM Nadia: the scripts and behavior-read context are preserved with Sarah and Anna, and the public/internal narrative stays role-fit and next phase — not blame and not Compass proof.

I’ve got HR’s process guardrails and Nadia’s handoff packet in place. Draft the company note for Friday, but do not send it.