Translation Registerusing the bridge without making it an audit

The most common misuse of any framework is to use it as an audit. The bridge applied crudely reads as “you are failing to be Curious” or “your Humble score is low.” That framing shuts down the conversation before it starts. It also misdescribes what the bridge is for. The bridge does not evaluate whether a person holds a value. It describes the translation between the value and the capability the role requires, and that translation is where useful performance conversations live.

The bridge makes performance conversations about the translation, keeping the person out of it. Instead of “you are not Curious enough,” which is both unverifiable and insulting, the conversation becomes: “Your Curious value, which I see in how you investigate new tools outside work, is not yet translating into the Fast Learner behaviour the role now asks for in user-research methods. Here is what that translation looks like, and here is what a ninety-day plan to practise it could include.” The value is acknowledged, the capability gap is spelled out, the path is concrete, and neither party has to relitigate the designer’s character.

Three moves hold the translation register in place through conversations that would otherwise collapse back into audit.

• Anchor the observation to the capability; the value is not the point: The value is who the person is. The capability is what the role requires. The conversation is about the translation between the two. A manager who says “I don’t see enough Curious from you” is making a character claim that the designer can reasonably deflect or dispute. A manager who says “I don’t see Fast Learner behaviour in the research-method shifts we’ve introduced this quarter” is making an observation about work the designer can either recognise or point to counter-evidence for. The second conversation is productive. The first is almost always not.
• Distinguish value-to-capability gaps from hire-for gaps before the conversation begins: The distinction (15.3) matters here, because the two gaps require different conversations. A value-to-capability gap sounds like: “the value is there; the capability translation is not yet active at the scope we need; here is what coaching will do.” A hire-for gap sounds like: “this capability is one no culture value reliably produces in one performance cycle; the real conversation is about what role, inside or outside this team, lets your actual profile do its strongest work.” Pretending a hire-for gap is a growth conversation is the single most expensive pattern in performance management. It produces repeated cycles, repeated good-faith effort, and repeated non-closure, until an exit that could have been a redirection becomes an exit that was nobody’s good outcome.
• State the H3 axis, “This is a Head capability your Collaborative value should activate through Business Sense. Right now it isn’t active in the product-strategy conversations we’re running.” The axis vocabulary (Hand, Head, and Heart) gives both parties a shared frame without personalising the gap. It also connects the conversation to the rest of the book’s language, which the designer can use independently to read their own development, through T01, through the level architecture (Chapter 8), through the Branch vocabulary (Chapter 9). The conversation becomes part of the designer’s own H3 practice rather than an event imposed on them.