Function (Head + Hand)the infrastructure of design delivery

The third domain is Function: the infrastructure of design delivery, the operational systems that let the team ship reliably at the quality Direction has established. Where Vision and Direction sit at the strategic and qualitative ends of design leadership, Function is the middle, the operational layer built to serve the work Vision points to and Direction shapes.

The H3 axis of Function is Head + Hand. The leadership craft here is systemic thinking (Head) applied to production infrastructure (Hand at scale). This is where Chapter 4.5’s DesignOps-as-infrastructure framing applies most directly: every artefact a design function produces that another designer uses (the design system, the research repository, the critique ritual, the delivery template, the quality gate) is a Function decision made visible. A leader strong in Function builds a team whose output is consistent even when composition changes. A leader weak in Function leaves a team whose quality depends on who happens to be available that sprint.

Function’s territory:

• Design system governance, naming, structure, contribution model, versioning.
• Process design, how work enters the team, moves through it, and leaves it.
• Tool selection and sustainment, which platforms the team commits to, which it consciously does not.
• Handoff rituals with engineering, what gets shipped, in what form, at what fidelity.
• Quality gates, the conditions work must meet before it ships.
• Workload management, how capacity is allocated across simultaneous demands.
• Delivery rhythms, how the team’s cadence synchronises with the product development rhythm around it.

Most design organisations underbuild them, and the underbuilding shows up as chronic delivery instability the team blames on external factors.