Sun
The source illuminates everything else but cannot be looked at directly. Solar systems organize around a central energy source that defines orbital paths, seasonal cycles, and available energy budgets. Every element in the system exists in relation to this center—distance determines temperature, rotation determines day length, angle determines climate. Design systems structured around a central source inherit similar properties: everything references the core, but the core itself must remain stable or the entire system destabilizes. Centralized authority is efficient until the source fails.
A sun-centered system places all dependency on a single source. Planets orbit the star, derive warmth from it, organize their years around it. The sun does not depend on the planets; the planets cannot exist without the sun. This asymmetric dependency creates efficiency and fragility simultaneously.
Design systems with central repositories, single sources of truth, or master components exhibit solar structure. All other elements reference the core. A design token system where all color values derive from base tokens is heliocentric. Change the base and everything shifts. The efficiency is obvious: update once, propagate everywhere. The fragility is equally clear: corrupt the source and the entire system fails.
The alternative is distributed authority, where multiple sources provide redundancy but create coordination problems. Solar systems avoid coordination problems through dictatorial simplicity: the sun rules, everything else obeys gravitational law. But when the sun dies, the system dies. Distributed systems survive individual failures but require constant negotiation.
Solar energy follows inverse square law: double the distance, quarter the intensity. This creates habitable zones—regions where conditions permit complexity. Too close and everything burns. Too far and everything freezes. The gradient from center to periphery determines what can exist where.
Interface hierarchies exhibit similar gradients. Elements near the conceptual center (primary navigation, core actions, fundamental patterns) receive maximum attention and resources. Elements at the periphery (edge cases, advanced features, administrative functions) receive less. This is not arbitrary but structural: attention and development resources follow power law distributions.
The designer must recognize which features belong in the habitable zone and which can function in extreme regions. Core user flows need temperate conditions—well-tested, thoroughly documented, carefully maintained. Peripheral features can survive in harsh environments—minimal documentation, occasional bugs, deferred maintenance. Trying to provide solar-level resources to all features equally exhausts the budget.
The sun establishes time through its relationship to rotating bodies. Day and night, seasons, solar years—all emerge from geometric relationships between light source and illuminated objects. The sun itself is constant; periodicity arises from motion relative to the source.
Design systems create similar temporal structures. Release cycles orbit around version milestones. Sprint rhythms rotate through planning, execution, and review. Annual design audits mark complete revolutions. These cycles are not inherent to the work but imposed through organizational motion relative to fixed reference points.
The sun metaphor reveals that periodicity requires both a stable reference and relative motion. Without the stable reference (consistent milestones, recurring meetings, fixed deadlines), motion becomes drift. Without relative motion (actual progress, completed work, evolved understanding), the reference becomes meaningless. The cycle requires both elements: the fixed and the moving.
The sun makes everything else visible but blinds anyone who looks directly at it. This is not metaphorical but optical: the source of illumination cannot itself be clearly examined while it performs its function. Only during eclipse or through special filters can the sun be studied directly.
In organizational design, the foundational assumptions—the core beliefs that structure all subsequent decisions—often exhibit this property. They make all other work visible but resist direct examination. "User-centered design," "move fast and break things," "convention over configuration"—these solar principles illuminate practice but are rarely questioned while in effect.
Examining foundational assumptions requires special conditions: crisis moments when normal work stops, external perspectives that don't share the assumptions, or deliberate exercises that create safe distance. The working system cannot examine its own core while operating. The sun must set before it can be seen clearly.
The sun provides finite energy to its system. Total available energy is fixed by the star's output. Planets compete for this energy based on size and position. The system's total activity cannot exceed the source's capacity.
Design organizations operate under similar energy constraints. Available design hours, attention budget, processing capacity—all are ultimately bounded by team size and time. Features compete for this limited resource. A project that consumes excessive design energy starves other projects. The total system output cannot exceed the source's productive capacity.
Sustainable systems match energy consumption to available supply. They do not design as if resources were infinite. They prioritize, sequence, and occasionally say no. Unsustainable systems assume unlimited energy—that every feature can receive thorough design attention, that quality never requires trade-offs, that the sun will burn forever. It will not.
Suns are not eternal. They exhaust fuel, expand into red giants, collapse into white dwarfs or explode as supernovae. The timescale is long but the outcome is inevitable. Solar-dependent systems must either evolve before their sun dies or die with it.
Design systems built around individuals face this mortality directly. The designer who created the system, holds the vision, makes the decisions—this person is the sun. When they leave, the system often collapses. Knowledge scattered across multiple people is redundant but requires coordination overhead. Knowledge concentrated in one person is efficient but existentially vulnerable.
The mature system prepares for solar death. It documents principles so they outlive their originators. It distributes authority so no single departure causes collapse. It builds in redundancy even though redundancy is inefficient. The alternative is accepting that the system's lifespan is bounded by its sun's lifespan. Some systems choose this, trading longevity for intensity. They burn bright while their sun lives, then die cleanly when it doesn't.
The sun creates not only illumination but shadow. Every object blocks light, casting a dark region behind it. The shadow is as fundamental to the solar system as the light. Where light falls depends on what blocks it.
In design, what receives attention creates shadows of neglect. Features that receive intensive design work cast shadows on features that don't. User groups that receive research attention render other groups invisible. The design process itself creates these shadows not through malice but through geometry: attention is directional, resources are finite, focus creates blind spots.
Recognizing shadows allows deliberate management. If this feature receives solar attention, which features fall into shadow? Is that acceptable? Can we rotate to illuminate different areas sequentially? The sun cannot illuminate all sides of all objects simultaneously. Neither can design practice. The question is whether the shadow pattern serves the system's needs or creates unacknowledged gaps.