The second distinction: H3 builds career level in as a structural element, where most frameworks leave it a background assumption.

Most frameworks are written for a designer at a specific point in their career, without stating that assumption. The language implies mid-level. The examples assume access to users and a product team. The challenges described belong to someone past their first years but not yet managing people. The career context is implicit and usually wrong for the reader holding the book.

H3 makes career level explicit from the beginning. The three layers of H3 (Model, Structure, Conduct) correspond to three phases of a design career: becoming excellent at the work, building a path through it, and taking responsibility for others doing it, each phase extending the last.

A designer at year two and a design director at year fifteen are both inside the same framework. What differs is which layer is most active and which requires the most sustained investment. For the junior designer, the Model layer (Hand, Head, and Heart) is the primary development site. For the director, Conduct is where most of the accountability lives. But the director still needs Hand: the ability to read a piece of design work and know whether it is good. And the junior designer needs to know that Structure and Conduct exist, because decisions made without any picture of the present and future are decisions made without information, which is risky.

H3 applies at every stage of the career, from the first year to the last.

Do

Look at your recent work. Describe what most of it was aimed at: improving what you make, building where your career goes, or shaping how your team works. That sentence identifies your current layer. For example, “Getting better at the work itself” is Model. “Developing my team” is Conduct.

Check

Describe one thing your current role formally expects of you that belongs to a different layer than the one you just identified. That gap is where H3 tells you to look first.

Levela structure of capability