Designing for Trust

One lesson I keep returning to: engineering problems are often easier than human problems.

When an engineering system fails, we search the logs, collect evidence, reproduce the issue, find the root cause, and ship a fix. Given enough data, uncertainty goes down.

Human systems do not work that way. When information is incomplete, our minds do not wait patiently for the missing data; we fill the gaps ourselves. Sometimes those stories protect us. Sometimes they mislead us. I have had moments when something small took up far more space in my mind than it deserved, until I realized I was not solving a problem anymore. I was trying to eliminate uncertainty.

Those are two different goals.

When uncertainty becomes the problem

An engineer can keep debugging until the defect is found. Life does not always hand you the final log file. Sometimes the missing information never arrives.

Negative emotions — uncertainty, frustration, embarrassment, fear — are useful signals. They tell us to pay attention, reassess, and protect ourselves. But when the signal keeps firing long after there is nothing left to solve, analysis quietly turns into rumination.

This is where one idea from positive psychology has stuck with me: the Red Cape and Green Cape.

The Red Cape looks for danger. What went wrong? What should I protect myself from? What could happen next?

The Green Cape asks different questions. What else could explain this? What can I learn? What is still in my control? How do I move forward?

Neither cape is better. The Red Cape protects us. The Green Cape widens our view. Good judgment is knowing which one a situation calls for, and when it is time to switch.

Consistency is the pipeline

Angela Duckworth's work on grit — passion and perseverance toward long-term goals gave me another way to think about this.

About three years ago, I started running three or four kilometers, three or four times a week, mostly for my physical and mental health. I started small. There was soreness, fatigue, and a lot of internal negotiation about whether I actually wanted to run. Nothing changed dramatically. I just kept going.

Difficult became familiar. Familiar became routine. Routine became part of how I live.

Now I can put on my shoes and head out the door without thinking twice.

As an engineer, the closest analogy I have is a CI/CD pipeline. We rarely ship a complex system perfectly in one release. We build, test, deploy, observe, improve, and repeat.

Personal development works the same way.

Running was one iteration. Now I am up around 5 a.m. doing HIIT four mornings a week: strength, mobility, cardio, and capacity. I am still learning. Some mornings are hard. Some muscles file complaints the next day.

But the goal was never a perfect workout.

The goal is to ship a slightly better version, over and over.

Consistency is the pipeline.

From emotions to trust

The link between grit, emotions, and continuous improvement became clearer to me over time.

Grit is not just tolerating discomfort. Perseverance means feeling the difficulty without letting it dictate every decision. Negative emotions flag problems; positive ones — curiosity, gratitude, hope, confidence — widen our view and keep us moving.

The same holds for relationships and communities.

Trust does not require people to make no mistakes. It requires clarity about what happens when mistakes happen.

People need feedback. Questions need answers. Mistakes need acknowledgment. Loops need closing.

When information is missing, people start writing their own explanations. A small gap in communication can produce uncertainty far bigger than the original problem, which makes it as much a design problem as a human one.

Designing for trust

Good engineering does not stop when the software technically works.

A well-designed system reduces unnecessary ambiguity. It acknowledges the action, communicates failure clearly, explains what happens next, and closes the loop.

A missing confirmation message looks insignificant from an infrastructure view. To the person waiting on the other side, that silence becomes uncertainty, and uncertainty invites the imagination to start writing its own story.

This is where positive psychology, grit, engineering, and trust meet for me. Running taught me that improvement compounds through consistency. Duckworth gave me language for sustained effort. Software engineering gave me a model for incremental improvement. Positive psychology showed me that both negative and positive emotions have a job to do. And life keeps reminding me that not every uncertainty can be debugged away.

As a founder, I want to build technology around that: systems that make the next step clearer, products that reduce unnecessary uncertainty instead of amplifying it, and tools that encourage curiosity without removing caution.

The goal was never one perfect release, one perfect workout, or one perfect decision.

It is continuous improvement: one run, one workout, one deployment, one conversation, one small step at a time.

Technology should not make us less human.

It should help us get better at being human.