Scalability → Buildability

We’ve misunderstood scalability. Teams celebrate petabyte-scale data lakes and user count spikes, obsessing over metrics and load capacity. The teams that actually scale are building systems that simplify development. Scalability means making the next feature easier to ship than the last one.

Most teams handle analytics by building features first, then adding tracking later. Even with modern tooling, tracking stays separate from core functionality and creates a constant tax. Engineers write features, add tracking. Analysts specify events, wait for implementation.

Smart teams make tracking native to their components from the start. A well-designed button knows how to track itself. Engineers get analytics for free. Analysts can predict available data by looking at the component library. Product managers can spec features knowing the insights they’ll have access to.

Composability

When tracking moves from bolted-on to built-in, components carry behavior and intelligence alongside their UI. A “Subscribe” button maintains a contract about subscription behavior, tracking, and data insights. Design systems enforce consistent behavior. Data pipelines turn data into insights faster.

e/acc

This approach gets more powerful with AI tools. When developers structure components and define behaviors well, tools like Cursor understand and extend your patterns. Each suggestion builds on your existing primitives and maintains the composability that makes your system work.