Mission Communications

Mission Goal

Design a mission identity that is meaningful and accurate: a mission patch (symbol + motto) and a capability star (what your team can do, proven by evidence).

Why This Matters

In real aerospace programs, identity is not decoration—it’s a shared language that aligns teams, communicates capability, and builds trust. A good patch is a promise you can keep.

Inputs From Other Teams

• All teams: confirmed capabilities and limits (what you can and cannot do yet).
• Command & Control: mission roles and responsibilities.
• Instrumentation: what data you collect (your “proof points”).

What You Must Produce (Deliverables)

1. Mission Patch: symbol + mission name + motto (one line).
2. Capability Star: 5–8 capability points with evidence links (or references to logs).
3. One paragraph rationale: what each element means and how it connects to mission truth.

Keep it honest: your capability star should reflect tested capability, not ambition.

Templates

Short tweet template (≤ 280 chars)

Meet [Mission Name] 🛰️ Our patch symbolises [meaning] and our motto is “[motto]”. Our capability star proves we can [3 key capabilities]. Evidence in our mission log.

Newsletter paragraph template

We’ve created a mission identity for [Mission Name]. Our patch uses [symbols] to represent [meaning], and our motto “[motto]” reflects our mission goal. Our capability star lists what we can prove today (with evidence), and what we’re still building next.

Assembly slide outline

1. Patch reveal (image + name)
2. What the symbols mean (3 bullets)
3. Motto (one line + what it commits to)
4. Capability star (5–8 points)
5. One capability we’ll add next (and how we’ll prove it)

Step-by-Step

1. Pick 3 mission values (e.g., “truth”, “resilience”, “curiosity”).
2. Choose 2–3 visual symbols that match your mission goal (not random space icons).
3. Write a motto that is specific and testable (avoid vague “to infinity” slogans).
4. Draft your capability list (5–8 items). Each item must link to evidence.
5. Reality filter: label anything unproven as “Next capability” (not on the star yet).
6. Publish: add patch + star + rationale to your team page.

Success Criteria

• Patch symbols and motto clearly connect to the real mission goal.
• Capability star contains only capabilities backed by evidence.
• Rationale explains meaning without hype or exaggeration.
• Identity is cohesive and recognisable (consistent name, colours, tone).

Evidence Checklist

• ✅ Patch graphic (or clean sketch) + name + motto
• ✅ Capability star (5–8 points) with evidence references
• ✅ 1 paragraph rationale
• ✅ “Next capability” (one item) + how you’ll prove it

Ethics (Truthfulness, Privacy)

• Truthfulness: your capability star is a public promise—do not include untested claims.
• Privacy: do not put student names/faces on patches without consent.
• Cultural respect: avoid symbols that borrow from cultures/religions you don’t understand.

Common Failure Modes

• Patch looks cool but has no meaning.
• Capability star lists ambitions (“will do”) instead of proof (“did do”).
• Too many symbols and tiny text—no one can read it.
• Using someone else’s logo/art without permission.

Stretch Goals

• Create 2 patch variations and run a team vote with reasons.
• Add a “verification stamp” for each capability (test date + run ID).
• Design a mission “badge” for each completed level (MC1–MC5).