1. The tower and the tribes

Arthur C. Clarke’s The Fountains of Paradise is about building a space elevator, a project that requires engineers, financiers, politicians, and believers to cooperate across generations. The tower is the goal, but the book is really about the tribes needed to build it. The desktop has three tribes: engineering, operations, and business. Each sees the platform differently. Each is necessary.

Entry 302 introduced team and organization. This entry focuses on the three core functions.

2. Engineering: making the object

Engineering turns requirements into hardware and software. For the desktop, engineering includes:

  • Systems engineering and architecture.
  • Mechanical, thermal, and structural design.
  • Electrical power and avionics.
  • Communications and RF.
  • Flight software and autonomy.
  • Guidance, navigation, and control.
  • Manufacturing engineering and test.

Engineering’s temptation is to optimize the object for elegance. The programme must remind engineering that the object is for sale and for operation.

3. Operations: keeping it alive

Operations is what happens after engineering hands over the keys. For the desktop, operations includes:

  • Mission planning and flight dynamics.
  • Ground segment and communications.
  • Command generation and execution.
  • Health monitoring and anomaly response.
  • Payload scheduling and data delivery.
  • End-of-life planning and disposal.

Operations’ temptation is to demand conservatism and redundancy. The programme must remind operations that the platform must be affordable and that risk is part of the business.

4. Business: finding the money

Business turns capability into revenue and capital. For the desktop, business includes:

  • Customer development and sales.
  • Pricing and contract negotiation.
  • Funding and investor relations.
  • Regulatory and insurance coordination.
  • Supplier and partnership management.
  • Programme planning and reporting.

Business’s temptation is to promise more than engineering can deliver. The programme must remind business that commitments become requirements.

5. The interfaces between tribes

The most dangerous places in a programme are the boundaries between functions. Misalignment appears as:

  • Engineering builds what operations cannot fly.
  • Operations refuses a design that customers need.
  • Business sells a capability that does not exist.
  • Engineering ignores a regulatory constraint.
  • Operations misses a contractual deadline.

Good organization designs these interfaces deliberately: regular cross-functional reviews, shared requirements, clear ownership of decisions, and escalation paths.

6. Scaling the team

A small team can design a concept. A larger team is needed to build and operate. Scaling requires:

  • Clear roles and responsibilities.
  • Documented processes that do not become bureaucracy.
  • Hiring for both technical depth and programme awareness.
  • Training that passes knowledge from early hires to later ones.
  • Retention of people who understand why decisions were made.

The desktop’s first hires matter disproportionately. They set the culture and the technical direction.

What this changes

  • Engineering, operations, and business are the three core functions.
  • Each has a healthy temptation that must be balanced by the others.
  • Interfaces between functions are where programmes fail.
  • Scaling the team requires clear roles, documented processes, and knowledge retention.
  • The next entry will close the team and organization arc with a contemplation.