Mission Communications

Mission Goal

Create a full exploration narrative that connects your mission to a bigger “why”, includes uncertainty honestly, and sets the stage for future missions. You’re not just reporting—you’re building a culture of exploration.

Why This Matters

The strongest space programs tell a long-term story: what we’re learning, how we respond to surprises, and what comes next. Exploration narratives build public trust, team pride, and disciplined ambition.

Inputs From Other Teams

• All teams: what was achieved, what failed, what is uncertain.
• Data / Instrumentation: 1–2 key results or patterns from real data.
• Risk & Safety (or C&C): top risks managed and how.
• Mission Design: the long-term purpose and next mission concept.

What You Must Produce (Deliverables)

1. Exploration narrative (450–650 words): past → present → next.
2. Mission timeline (5–8 bullet events): plan, test, launch/run, data, learning.
3. Three “learning commitments”: what you will do differently next time.
4. One public Q&A (5 questions with honest answers).

Templates

Short tweet template (≤ 280 chars)

Exploration update: [Mission Name] taught us [learning]. We proved [evidence], and we’re still uncertain about [uncertainty]. Next mission: [next step]. This is how exploration works.

Newsletter paragraph template

Our mission story is bigger than one run. We planned [goal], tested [method], and collected [data]. We learned [learning] and noticed [surprise]. Next we’ll change [commitment] and attempt [next mission] to go further—carefully.

Assembly slide outline

1. Our mission in one sentence
2. What happened (timeline)
3. What we learned (data-backed)
4. What we’re unsure about (honest uncertainty)
5. What we’ll do next (commitments + next mission)

Step-by-Step

1. Write the timeline first: 5–8 events from start to learning.
2. Pick 1–2 key results that are evidence-based (a chart, a pattern, a measurement).
3. Name the surprise: what didn’t match expectations?
4. State uncertainty professionally: what you don’t know yet and why.
5. Write 3 learning commitments: a process change, a technical change, a verification change.
6. Create the Q&A: anticipate tough questions and answer honestly.
7. Draft the 450–650 word narrative: past → present → next, grounded in the above.

Success Criteria

• Narrative includes evidence (not just feelings) and reflects real mission events.
• You state uncertainty without panic and without hiding it.
• Your “next steps” are specific, testable, and aligned with capabilities.
• Q&A answers are truthful, respectful, and privacy-safe.

Evidence Checklist

• ✅ 450–650 word exploration narrative
• ✅ Timeline (5–8 events)
• ✅ Three learning commitments
• ✅ Public Q&A (5 questions + answers)
• ✅ One supporting evidence item referenced (chart/table/log link)

Ethics (Truthfulness, Privacy)

• Truthfulness: don’t rewrite history to make it look perfect—learning is the point.
• Privacy: remove names, faces, and sensitive location/time details from public logs.
• Respect: describe failures as system issues and learning opportunities, not blame.

Common Failure Modes

• Story becomes marketing and loses evidence.
• Ignoring uncertainty (pretending everything is solved).
• Making future promises that don’t match capability.
• Q&A answers dodge questions or accidentally reveal private details.

Stretch Goals

• Create a “Season 1 / Season 2” roadmap of missions with increasing capability.
• Record a 2-minute narrative video (voiceover + timeline + one chart).
• Write a partner pitch: “What support would help our next mission succeed?”