An operating system does not run your applications. It provides the environment in which applications run. You can install any tool, any methodology, any process on top of it. H3 is the OS: the underlying logic of the practitioner that persists across every project, every role, every organisation. The applications change but the OS underneath them persists.

H3 describes what a process, a methodology, or a career ladder leaves out: the practitioner who runs them.

H3 is three dimensions of practice, whatever the project, role, or organisation. They are dimensions of a person. Over a career, the question is which dimension is most developed, which is most neglected, and which demands the most attention.

Most frameworks ask: how do I design better? H3 asks: what kind of designer am I becoming? Most of the chapters in the book are answers to that question, applied to a specific dimension of practice.

H3 is not an empirically validated instrument. The modes, the levels, the domains, and the regularities this book points out (the two-year reversal, the mid-career plateau, the fifteen-year arc) are distilled from practice that I observed across many designers over twenty-five years, not derived from controlled study. Where the book sounds like it is reporting a finding, read it as a pattern instead, concrete enough to act on, and open to revision as your own evidence comes in.

A note on scale. The framework is calibrated against mid-size product-organisation practice, the context most of its readers work in. For the solo practitioner there is no team or organisation to read (9.1). In very large organisations the six levels fragment into finer internal ladders, and the names matter less than the scope they describe (8.7). In distributed, async-first teams the Conduct cadence shifts from the room to the written record.

Operating Systemwhat H3 is, and what it is not