1. The means and the ends

Iain M. Banks’s Use of Weapons is about a man who is very good at achieving objectives and very bad at living with the methods he uses. The book asks whether the organization we build shapes the outcome more than the plan we write. For the desktop, the answer is yes. A brilliant plan executed by a divided team will fail. A modest plan executed by a coherent team has a chance.

Entries 302 and 303 covered team and organization. This entry closes the arc.

2. What was learned

The arc covered:

  • Organization as design variable: structure, roles, and culture affect what the programme can do.
  • Core functions: systems engineering, mechanical, electrical, software, GNC, operations, regulatory, and business.
  • Engineering, operations, and business: the three tribes with different temptations and necessary checks.
  • Scaling: how the team grows without losing coherence.

These topics are less concrete than propulsion or insurance, but they are no less decisive.

3. The decided posture

The Resident will treat the team as a subsystem that is designed, not inherited. The practical posture is:

  • Start with a small core that spans engineering, operations, and business.
  • Hire for programme awareness, not only technical depth.
  • Document decisions and rationale from the beginning.
  • Hold regular cross-functional reviews where each tribe can challenge the others.
  • Use build/buy/partner decisions to control headcount and risk.
  • Build a culture where bad news travels fast and operational humility is valued.

This posture accepts that people, not plans, execute the programme.

4. What remains open

Specific team questions will be answered as the programme advances:

  • The exact founding team and their backgrounds.
  • Which functions are internal versus contracted.
  • The location and nationality structure of the team.
  • How export control affects hiring.
  • The balance between senior experience and young energy.

These are not idle questions. They affect funding, licensing, and customer trust.

5. Organization as memory

The most useful insight from this arc is that the organization is the programme’s memory. Years from now, when the original designers have moved on, the organization will still be making decisions. If it remembers why things were done, it can adapt. If it forgets, it will either stagnate or repeat mistakes.

What this changes

  • The team is now treated as a designed subsystem.
  • The core team must span engineering, operations, and business.
  • Cross-functional challenge and documentation discipline are required.
  • Build/buy/partner decisions control headcount and risk.
  • The team and organization arc is closed. The ledger has now covered the major programmatic arcs: attachments, integration, end-of-life, manufacturing, regulation, insurance, timeline, customers, and team.