Capable by Designmap, hire structurally, translate, simultaneously

A culture that is capable by design does three things simultaneously.

Spelling out values specifically enough to predict capabilities. A ratified value without a defined mechanism and a defined capability is not yet usable, only a placeholder. The first discipline is the map-building work: the team knows what each of its values is supposed to produce, can say so in a sentence a new hire would recognise, and can test the prediction against observed work.

Hiring for the capabilities culture cannot grow. Three capabilities the framework identifies most clearly have no reliable culture-value driver: Strong Aesthetics, Systems Thinking, and Engineering Skills. No culture value activates a reliable mechanism for them at the pace roles require. A team that treats every capability gap as a growth opportunity will hire for culture fit and find itself, two years in, with capability gaps that culture work cannot close. The second discipline is structural hiring: clarity about which capabilities must come in through the front door.

Running performance conversations in the translation register (15.4). A team that has the map and structural hiring but treats the bridge as an audit instrument will lose the team’s willingness to engage with it. The values will start functioning defensively rather than productively. The third discipline is the register work: the bridge lives inside conversations about the translation between who the person is and what the role requires. It is not a verdict on whether the person holds the value.

The three are held simultaneously. A leader running only one or two produces a recognisable pattern.