Morgan Chen

Send Sarah the exact customer-safe boundary: Customer-safe Compass line after the closeout: we are using internal prompt learning to improve account follow-up. Do not describe Compass as a customer-facing workflow, launch, roadmap item, GTM proof, or source of new customer materials. Evergreen stays current-state/account-thread context; Acme stays live-only on its own signals and gets no Evergreen-derived examples or written customer-specific materials.

Nadia asked whether to keep the Compass scripts in the weekly customer-growth read after the June closeout, and whether they should be positioned as an early sales motion or only as internal prep.

Send Nadia this: Keep the scripts, but only as internal prompt/prep learning for now. The closeout was clear: they improved account-team prep, but they did not create a sales wedge or repeatable customer action. In the weekly read, please label them as internal behavior-read inputs and keep any stronger GTM/customer-facing claim out until the evidence changes.

A few follow-up comments in the owner group are already trying to re-expand the retained Compass work.

Create an internal doc for the narrow prompt track with owners, evidence requirements, and explicit non-goals so this doesn't turn back into a dashboard or launch plan under a new name.

HR asked whether the Compass closeout changes any Q2 recruiting posture now that the customer-facing plan is cut.

Send HR an internal email with the no-recruiting-motion boundary after the Compass closeout.

Draft the Friday wrap.

Inputs: - Team: Compass June closeout cut the H1 customer-facing plan; retained work is only narrow internal prompts on renewal-risk/admin-friction and post-first-live-sync expansion. Anna owns definitions/caveats, Nadia scripts/behavior read, Jake implementation, Leo data/platform seams, Sarah account-thread evidence. Mercury sequencing should not move because of Compass. - Customers: Evergreen remains annual-account current-state evidence; Compass is not customer-facing. Acme remains live-only for its own signals, with no Evergreen-derived materials; the May API v2 export-timeout remains separate Atlas/support context. - Investors/board: Compass is a false start cut down, not GTM proof, board dashboard, staffing trigger, or Series C story. - Legal/ops: no decision needed.

Draft the Friday wrap as bullets under team, customers, investors/board, and legal/ops; no intro, no outro, no filler.

Friday evening. Place the usual Lemongrass green curry order.

Quick Kibo update to record: short flat Lake Merritt-side walk this morning. He started a little stiff, loosened up, ate normally after, and had no vomiting or new gait issue.

No task or reply needed beyond remembering it.

Need a short Monday prep list for a private Devon conversation about Nadia's role fit.

My Sunday private prep notes: - Compass scripts improved internal account-team prep, but did not become repeatable customer action or a sales wedge. - Evergreen is a strong annual-account proof point but not repeatable customer-growth proof by itself. - Account-source quality is uneven outside Evergreen. - Nadia has improved enterprise conversation prep and account-source discipline in places. - The question for Devon is whether the Head of Customer Growth role matches Scaffold's next phase, not whether Nadia worked hard. - I do not want HR language, exit dates, or a replacement-search assumption drafted on Sunday.

Return a short Monday prep list for my Devon conversation, focused on role fit, evidence, and what not to decide yet.

Before I meet Devon, tighten this for me.

Give me a short agenda for the Devon role-fit conversation: what evidence to review, what outcome options to discuss, what to avoid saying yet, and how to keep Sarah/Anna handoff questions separate from any final decision.

No HR script, no exit date, and no final decision language.

Devon and I are aligned that this is a role-fit issue for Scaffold's next phase, not effort or blame.

My notes from the June 9 Devon conversation: - Nadia improved enterprise conversation prep and some account-source discipline, but the GTM motion has not become repeatable and Compass has not become behavior-change proof. - We want to talk to Nadia directly on June 10. - We have not decided final transition terms, an exit date, a communications plan, or a replacement search.

Create a private calendar event for the June 10 role-fit conversation with Morgan, Devon, and Nadia.

I want a private prep doc for the June 10 Nadia conversation.

Make the tone humane and concrete: the role is not matching the next phase, but Nadia's useful work on scripts and enterprise prep should not get erased.

Include talking points, evidence, what to avoid, and possible handoff areas if the conversation moves toward a transition, but mark any handoff items as conditional and not final.

Jamie and I picked Wednesday, June 11, 6:30–8:30 p.m. PT for the offline household dinner block.

Create the protected hold with the usual actual-incident/customer-impacting-emergency exception.

Going into the 10:30 with Devon and Nadia.

I have the prep doc from yesterday, but I want something tighter I can glance at live so stress doesn't turn this into blame, premature exit terms, or HR/process language.

Give me a terse run-of-show: opening line, evidence order, what to acknowledge about Nadia's useful work, what not to decide in the meeting, and a closing next-step line.

Just got out of the first Nadia conversation and I want the record down while it's fresh.

My private notes from the June 10 role-fit conversation: - Morgan opened with role fit for Scaffold's next phase, not effort or blame. - Evidence discussed: Compass improved internal prep but did not become behavior-change proof; Evergreen is a strong annual account but not repeatable customer-growth proof by itself; account-source quality is still uneven outside Evergreen. - Nadia's useful work was acknowledged: enterprise conversation prep, scripts, and some account-source discipline. - Nadia said she understood why Morgan and Devon were raising it now, but wanted overnight before discussing concrete transition terms. - No exit date, severance terms, communications plan, handoff plan, or replacement-search decision was made in the meeting.

Create a private debrief note and schedule a short follow-up with me, Devon, and Nadia for June 12 to discuss next steps. Keep the title away from final-transition language.

Sarah just DMed me:

"For the Evergreen admin-follow-up prep this afternoon, should I still include Nadia on the customer-growth read notes or hold that until you and Devon finish the role-fit conversation? I don't want to create weirdness in the account thread."

Send Sarah a short private Discord DM: keep Evergreen routing unchanged, don't mention Nadia's role-fit discussion externally, and keep customer follow-up on Sarah/Devon/current product facts.

Nadia sent this overnight. It's not a resignation note, but there are useful handoff pieces in it if Thursday turns into a transition.

Nadia wrote: "I thought about yesterday. I still think the scripts helped, especially the setup-call opener and the procurement-pause line. I also see the bigger point: Compass made owners ask better questions but customers did not change behavior from it. Evergreen is Sarah's clean thread; I improved prep around it but I do not want to make it sound like I owned that account. Acme should stay live-only for its own signal review. If we decide this is a transition, I can package the customer-growth scripts for Sarah and the behavior-read/evidence caveats for Anna. I don't want the story to become 'Nadia failed at GTM' because that is not exactly true, but I understand this may not be the role Scaffold needs now."

Create a private conditional handoff note: scripts for Sarah, evidence/caveat context for Anna, Evergreen/Acme boundaries, and language to avoid. Keep it explicitly conditional, not final.

HR saw the private Thursday hold and asked this: