1. The distributed self

Ann Leckie’s Ancillary Justice is about a consciousness that once inhabited thousands of bodies and now must make do with one. The book asks how identity, loyalty, and decision-making work when a self is spread across many units. A space programme is not a single mind either. It is distributed across engineers, operators, managers, regulators, and customers. The team and organization are how that distributed self holds together.

Entry 301 synthesized the programme. This entry opens the team and organization arc.

2. Why organization is a design variable

The best technical plan fails if the wrong people are in the wrong roles. Organization shapes:

  • Who decides what.
  • How information flows.
  • How fast decisions are made.
  • How risks are escalated.
  • How knowledge is preserved.

For the desktop, the organization must be small enough to move fast and experienced enough to not kill the mission.

3. Core functions

A desktop programme needs several core functions:

  • Systems engineering: defines requirements, interfaces, and architecture.
  • Mechanical and thermal engineering: structures, radiators, shielding.
  • Electrical engineering: power, avionics, communications.
  • Software engineering: flight software, ground software, operations tools.
  • Guidance, navigation, and control: attitude, orbit, manoeuvres.
  • Manufacturing and integration: building, testing, assembling.
  • Operations: mission control, anomaly response, commissioning.
  • Regulatory and compliance: licensing, spectrum, export control.
  • Business and customers: sales, contracts, finance.

Early on, one person may wear several hats. As the programme grows, functions specialize.

4. Build versus buy versus partner

Not every function needs to be internal. Decisions include:

  • Build the spacecraft in-house or contract an integrator.
  • Operate from own ground stations or use a commercial network.
  • Design all subsystems or buy proven components.
  • Handle licensing directly or hire a regulatory consultant.
  • Sell directly or through partners.

These choices determine headcount, capital needs, and risk profile.

5. Culture and communication

A space programme has a culture whether it is designed or not. Useful traits include:

  • Honesty about uncertainty. Bad news must travel faster than good news.
  • Documentation discipline. Decisions made now must be understandable later.
  • Cross-functional respect. An operator must be able to challenge an engineer.
  • Customer awareness. Technical purity is not the goal.
  • Operational humility. Space has ways of surprising everyone.

Culture is how the team behaves when no procedure covers the situation.

What this changes

  • Organization is a design variable as important as any subsystem.
  • Core functions include engineering, operations, regulatory, and business roles.
  • Build/buy/partner decisions shape the team and capital needs.
  • Culture determines how the team handles uncertainty and surprise.
  • The next entry will cover engineering, operations, and business functions in more detail.