RESF Internal Comms — Slack Post Not AMA

Situation

Decided to announce RESF engineering support via a Slack post (not company-wide AMA) to control narrative without signaling alarm. Nathan follows up with team Q&A for project impacts.

Reasoning

Managing two audiences: broader engineering org needs calm controlled tone, while affected engineers need real answers about timeline impacts. AMA elevates to crisis optics. Layered approach (Peter Slack post → Nathan team Q&A) gives Nathan ownership of engineering impact conversation. Must communicate before Lewis can set external narrative.

Additional Context

2-4 engineers being seconded to RESF for indeterminate period, impacting project timelines. Need to control narrative before external sources do.

Observed Evidence

Nathan 1:1 Fathom summary — explicit discussion of comms format (Slack vs AMA), rationale for controlled tone, Nathan follow-up Q&A plan.

Matching Patterns

Confidence Breakdown

Reasoning Depth Analysis