a builder's codex
codex · operators · Becky Kennedy · ins_repair-as-primary-relationship-strategy

Secure relationships are built by repair after rupture, not by avoiding rupture

By Becky Kennedy · Clinical psychologist; founder, Good Inside · 2026-04-28 · podcast · Good Inside leadership, repair, MGI, behavior vs identity

Tier A · TL;DR
Secure relationships are built by repair after rupture, not by avoiding rupture

Claim

Trust between humans — including in working relationships — is not built by getting it right every time. It is built by an explicit repair after the inevitable misstep. "Perfect is creepy" optimisation prevents repair muscle from developing; high-frequency repair compounds trust faster than low-frequency near-perfection.

Mechanism

Ruptures are inevitable in any relationship under pressure. A repair signals that the relationship is durable enough to survive misstep, that the leader is capable of self-observation, and that the team can raise concerns without the relationship breaking. Without repair, ruptures accumulate as quiet resentment. With repair, the same ruptures become evidence that the team can survive hard moments. The verbal pattern: name what you did, take responsibility, name what was happening for you, commit to working on it.

Conditions

Holds when:

Fails when:

Evidence

"Secure attachment isn't defined by getting it right all the time. It's defined by an adult who's willing to repair."

"Perfect is creepy."

Becky's verbatim repair model: "Earlier in the meeting I cut you off and used a harsh tone. Stuff was going on before the meeting. I'm sorry. I'm working on that."

— Becky Kennedy on Lenny's Podcast, 2026-04-28

Signals

Counter-evidence

For some leaders, frequent repair without behaviour change becomes its own corrosive pattern — the team learns the leader will rupture, apologise, and rupture again. Repair is a complement to behaviour change, not a substitute. Cultures that prize stoicism may also resist explicit repair as performative weakness.

Cross-references

Open the interactive view → View original source → Markdown source →