Insights

Trust

Essays on how trust is built, spent and rebuilt in teams, institutions and the systems we depend on. The longer argument is the book: Rehumanizing Trust, out 15 September 2026.

Trust

The ‘edge case’ is a person.

Every system has people it treats as exceptions, the ones the form breaks on, the sensor misses, the chart won't hold, and calling them edge cases makes them sound rarer than they are. Design for the imagined average and you quietly encode who counts as a real user, but design for the person at the edge first and you usually design better for everyone, captions help the whole noisy room, not just deaf users. Treat the edge as the center of the lesson rather than the margin of the problem, and check who your own systems are quietly filing as a nuisance.

Trust

A small doubt, multiplied by a million users, is a storm no dashboard is named to catch.

A single person's hesitation is just wisdom, but multiply that same doubt by a million users and it becomes a systemic force arriving from a direction your instruments were never built to detect. Most monitoring is tuned only for the failures you've already imagined, so a million people quietly losing faith at once often never trips a single clean metric. Take small doubts seriously precisely because they scale, and assume the most dangerous signal is the one your dashboard was never designed to feel.

Trust

We confused being able to measure people with being able to understand them.

We built systems to make people legible, scoreable, sortable, then quietly assumed legibility was the same as understanding and compliance the same as trust. A population can be perfectly measured and wholly misunderstood, and a compliance dashboard glowing green tells you nothing about whether the people inside it actually trust you. Keep the unofficial, pencil-marked map alongside the official chart, the slower relational work of understanding people doesn't show up on a dashboard, but it's what keeps things afloat.

Trust

The bravest thing a leader says is not ‘I’ve got this.’

Leadership is sold as certainty, but the moments that actually test a leader are the foggy ones, thin data, no process left to lean on, everyone waiting for a confident answer that isn't true. When the process fails, presence is the only instrument left, and pretending to a clarity you don't feel serves no one, it just delays the moment someone has to say what's real. Practice saying 'I do not yet know, and I am not leaving' in the same breath, that combination is what moral courage looks like in practice.

Trust

You cannot rebuild what you will not admit you do not understand.

Most of us depend completely on systems we couldn't actually explain, the supply chain, the credit model, the code, and rebuilding trust starts with admitting that, not with a blueprint. Confident, invented detail is how most systems get built, filling the unknown with assumptions and letting the people downstream discover where the rocks really are. Ask what you cannot yet see before asking how to fix it, and mark the blanks honestly instead of papering over them.

Trust

Your best instincts are someone else’s attack surface.

The same openness that lets us trust each other is exactly what scammers, dark patterns and engagement loops are built to exploit, borrowing a trusted signal rather than breaking it. The lesson isn't to trust less, a harbor with no bell is only quieter on the way down, it's to notice which signals you're running on and who benefits when you respond on reflex. Build the parts of trust that live in real relationship rather than tone alone, since a forged signal is far harder to fake than a forged relationship.

Trust

Something is always lost in translation between a person and a database.

Every system translates human gestures into data, a nod becomes a checkbox, a whole grief becomes 'closed, resolved,' and something always leaks out in the translation. The danger isn't the translation itself but treating the record as the reality, mistaking the stored gesture for the gesture, which is how 'satisfied' ends up filed for someone who has simply given up expecting more. Ask what any system you run fails to carry, and keep a way back to the human behind the field.

Trust

The data captured everything except what mattered.

A dashboard can be completely full and a customer can still feel entirely unseen, because the things that actually make someone feel served, a pause, a judgment call, a sense something's wrong, never fit in a field. Completeness is a property of the record, presence is a property of the encounter, and mistaking one for the other is how a fully measured organization still leaves people feeling like a case number. Keep a driftlight burning beside your fixed metrics, a deliberate practice of attending to what the instruments miss.

Trust

Every harmful system was once someone’s good idea.

Almost no one designs a system to harm people; most harm comes from sincere devotion pointed at the wrong number, like a beacon built so bright it blinds the ships it meant to guide. A metric is only ever a proxy for the thing you actually care about, and the moment you start optimizing the proxy instead of the person, drift begins, one reasonable decision at a time. Ask what you're really optimizing and what it's quietly costing the person on the other side, not whether your intentions were good.