Hourglasses
The hourglass is the primary structural container within Hourglass Architecture. It provides the framework through which missions move, the boundaries within which foci operate, and the alignment structures that maintain coherence across the organization. Every hourglass represents a stable, consequence-aware space where work can be framed, evaluated, aligned, executed, and carried into legacy.
An hourglass is not a department, team, or project. It is a structural unit that holds the full motion of the architecture from Situation to Legacy. Within an hourglass, missions are introduced, shaped, prioritized, aligned, executed, and sustained. This motion is supported by a set of foci that partition responsibility, a collection of pillars that maintain structural integrity, and a BEAM structure that provides alignment through shared analytical lenses.
Each hourglass has a defined scope and purpose. It exists to steward a specific domain of organizational responsibility, ensuring that work within that domain moves with clarity, stability, and consequence awareness. The boundaries of an hourglass are shaped by the organizational context in which it is instantiated, including the offices, domains, committees, and regulatory structures that define its authority and constraints.
Hourglasses operate in parallel across an organization. They provide a consistent architectural pattern that allows missions to move predictably, regardless of the domain in which they originate. This consistency enables cross-domain alignment, reduces structural drift, and ensures that work is evaluated and executed through a shared architectural lens.
The sections that follow describe the structural units that operate within an hourglass, including foci, missions, programs, pillars, and BEAM. Together, these units form the internal architecture that allows hourglasses to carry work from initial framing to long-term institutional learning.