I watched Rachel Botsman's TED talk on the trust leap over the holidays. I've been thinking about it ever since.
The trust leap is that specific moment when people decide to trust something — or someone — new and unknown. Botsman uses a simple example: the first time you got into an Uber with a stranger. You didn't know that driver. You'd never met them. And yet you got in the car. Why?
Concept: Rachel Botsman — illustration adapted for vanhertum.management
This intrigued me. What exactly is that moment? And what is the "why" — what makes people trust a company, a platform, or a person they've never encountered before?
Giving Someone the Power to Disappoint You
Botsman offers a definition of trust that has stayed with me: "Trust is about giving someone the power to disappoint you."
Think about what that means in a digital context. Every time a user clicks "submit" on your platform — registering an account, entering payment details, uploading sensitive documents — that is exactly what they are doing. They are taking a leap. They are handing you power they cannot take back in that moment.
"Trust is a confident relationship with the unknown."
— Rachel Botsman
And here is the uncomfortable part: most product teams, most IT departments, most compliance officers are thinking about the technical side of that moment. The encryption. The two-factor authentication. The GDPR checkbox. All of that matters. But it is not the whole picture.
The Human Problem We Keep Ignoring
We obsess over compliance checkboxes and security requirements, and then forget that we are asking people to trust us with something precious. Their data, yes — but also their time, their money, and in many cases their livelihood.
The trust leap is not primarily a technical problem. It is a human one. People do not decide to trust a platform because of a privacy policy. They decide because of how the platform feels, how it behaves when things go wrong, whether the humans behind it seem real and reachable and honest.
I still need to get my head fully around these concepts — I have already ordered Botsman's books. But the direction is clear to me: digital trust has to be designed and practised at a human level, not just an engineering one. The technical layer supports the leap. It does not make it.
What This Means in Practice
If you are building a product or running a platform, the question to ask is not only "is this secure?" but "would I take this leap myself?" Would I enter my credit card here? Would I trust this company with my employees' HR data? Would I get in this car?
If your honest answer is "I'm not sure," that is where the work begins — and it is usually not a technical problem you need to solve first.
Want to explore what the Trust Leap means for your platform or organisation?
Get in Touch