PATTERN Cited by 1 source

Foundational principles with decentralized guidelines

Intent

Balance organizational consistency with domain-specific flexibility by establishing a small number of non-negotiable structural rules (principles) alongside advisory frameworks (guidelines) that teams apply to their own context.

How it works

1. Foundational principles (few, firm, non-negotiable) — provide the structural invariants that ensure system-wide consistency and interoperability
2. Modeling guidelines (many, advisory, context-dependent) — provide a shared set of considerations teams use to make domain-appropriate decisions

The combination ensures no matter which path a team chooses, the results are consistent, scalable, and comprehensible system-wide, while each team retains autonomy over decisions that depend on domain-specific knowledge (Source: sources/2026-06-09-airbnb-scaling-beyond-one-data-architecture).

When to use

• Large organizations where multiple teams contribute to a shared system
• Domains where one-size-fits-all design is suboptimal
• Any platform architecture balancing governance with velocity

Trade-offs

• Pro: Consistent where it matters (joins, naming, organization)
• Pro: Teams can move fast on domain-specific decisions
• Con: Requires buy-in from all teams on the foundational principles
• Con: Risk of guidelines being applied inconsistently

Seen in

• sources/2026-06-09-airbnb-scaling-beyond-one-data-architecture — Airbnb's three principles + set of decision criteria for multi-product data modeling