- Thoughts
Trust is our most important infrastructure: being trustworthy even when we are wrong
Trust does not eliminate review; it enables meaningful review. It is the foundation of a team, revealed in the attitude toward handling mistakes and opposing opinions.
There is a limit to what one person can do alone. That is why we divide the work. Someone designs, someone develops, and someone tests. Each person performs their assigned task and passes the result to the next person.
People work with the belief that the person in the previous stage has acted responsibly. Of course, believing does not mean not verifying. We review code written by people we trust and check test results.
The difference in trust is not whether you verify or not. It lies in what and how much you need to verify. If you cannot trust, you must doubt the entire process by which the result was created. Did they actually execute it? Did they find a problem but not mention it? Did they judge something they didn't know as if they did?
If you cannot trust, you end up doubting constantly.
Conversely, if you work with someone you can trust, you can begin your review on the premise that the basic necessary work has been done.
Therefore, you can spend your time looking at more important issues. Trust does not remove review; it allows us to review what is truly important.
That is why I want to be with people I can trust when I work. And before that, I think: Am I a person others can trust?
I cannot decide whether I am a trustworthy person. "I am working hard." "I am responsible." "I am working honestly." I may think so myself. However, trust is ultimately the other person's judgment.
So sometimes, it is necessary to look at myself not from my own perspective, but from the perspective of others. If I were to assign a task to myself, would I feel at ease entrusting it to me? When I say "I've checked it," can that statement be believed as is? When I say there is no problem, is the other person re-checking everything from the beginning?
Would they want to tell me when a problem arises? The answers to these questions may be more evident in how people actually behave toward me than in how I perceive myself.
If you listen to the sounds around you, you can discover various facets of trust. Why do people behave that way? Why does each person describe the same information differently?
Internal company surveys can be one example. At first, people spend time writing down their thoughts. They think about what is uncomfortable and leave opinions on what they wish would change.
But what happens if they continue to feel that nothing substantially changes after submitting their opinions? Of course, it is difficult for an organization to change something suddenly. Not all opinions can be accepted.
However, if change is difficult, at least an explanation can be provided: whether a suggestion is being reviewed, why it is difficult to act on, and how it will be handled in the future.
If there is no feedback, people gradually learn. "Nothing changes even if I speak up." From that moment, spending time on a survey becomes a meaningless act. Opinions become shorter, and eventually, they write nothing at all.
Similar things happen during the development process. You build a program. A program used by many cannot be perfect.
Therefore, user complaints are inevitable. But what happens if every request is rejected and opinions are consistently not accepted conservatively? No one suggests complaints or problems anymore. It's not because there are no problems or because they've been solved. It's because they have learned that nothing changes even if they speak.
If this situation persists, it becomes very dangerous. On the surface, it starts to look as if the program is operating very well. Requests for improvement have decreased. Complaints have decreased. Reported problems have decreased. The problems haven't disappeared; only the people who talk about the problems have disappeared.
So when it feels quiet, you must occasionally ask this question: "Are there really no problems, or are people just no longer talking about them?"
When trust collapses, people begin to be silent before they begin to lie.
And the longer that silence lasts, the harder it becomes for us to know the actual situation.
Have you ever noticed who someone asks when they first join a team? Have you thought about how the frequency of phone calls changes when a person in charge changes?
Of course, it could simply be because they are close. It could be due to rank or experience.
But if you look a bit closer, it's the person who listens without getting annoyed when asked; the person who, even if they don't know the answer immediately, looks into it and gets back to them; the person who, when saying something cannot be done, explains the reason and is believable. Through these experiences, even if things didn't go in the direction they wanted this time, they will naturally seek that person out again next time.
There is no need to accept every opinion. It doesn't mean you must accept every opinion to gain trust. In reality, there may be far more cases where you have to refuse. What matters more than acceptance is how the opinion was handled. The conclusion might be the same: "It is difficult to reflect this time."
But if you explain why it is difficult and show that you properly reviewed the other person's opinion, the story changes. "My opinion wasn't accepted, but it is being reviewed."
"They are aware of the problem I mentioned." "Even if I don't understand all the reasons, there is some reason for it." When these experiences accumulate, they can voice their opinion again next time, even if it didn't go their way this time.
Therefore, I believe trust is not created by granting the other person's requests, but by treating the other person's words seriously. Sometimes, showing that I did not take your words lightly can be more important than giving the desired answer.
How is trust created? Of course, there are basics. Keeping your word. Saying you don't know when you don't know. Not saying you checked something when you haven't. Speaking up without hiding it when a problem occurs.
But I believe it is difficult to explain all of trust with just these. I believe trust is also created in the process of reaching the level of responsibility that the other person expects of me. If someone entrusts me with a task, I must think about how much that person expects.
Whether simply finishing the requested task is enough, whether I should check the results one more time, whether I should notify them first when a problem occurs, or whether I should deliver it in a form that is easy for the next person to work with. It is about thinking of the 'sufficiency' the coworker expects, not the 'sufficiency' I imagine.
To do this, I must move away from viewing myself subjectively. Rather than whether I worked hard, I must think about whether others can trust me and start the next task.
Trust is not created by a resolution in the heart alone. It must be proven through actions that the other person can experience.
Not a person who is never wrong, but a person who is trustworthy even when they are wrong.
Does that mean a trusted person is always someone who does their job well and always makes the right judgment? I don't think so. It's okay to be unskilled. People grow. It's okay to be wrong. Anyone can misjudge. A person who admits their shortcomings when they fail and strives for a better version of themselves.
A person who admits their mistake rather than making excuses when they are wrong, and tries not to repeat the same mistake next time. A person who speaks up when a problem occurs rather than hiding it before it grows larger.
I believe such a person can be trusted. It's not because they are perfect. It's because I know how they will act not only when they do well but also when they do wrong. Trust is not built solely on a record of not making mistakes. It is built over a long time, including the image shown when mistakes were made.
Therefore, a trustworthy person is not someone who is never wrong, but someone who is trustworthy even when they are wrong.
To be trusted, you must first trust
And trust cannot be created alone. If I want to be trusted by others, I too must be able to trust them. I cannot doubt every action of the other person, verify every single thing, entrust them with nothing, and yet ask them to trust only me.
Of course, this doesn't mean trusting everything without any conditions. Verification is necessary for important tasks, and trust must also be built gradually through experience.
It can start by entrusting small tasks, respecting the other person's judgment, honestly sharing the information I have, and listening seriously when the other person voices an opinion.
By experiencing whether that person keeps their promises, whether they honestly admit what they don't know, and how they act when a problem occurs, we become able to entrust each other with larger things. Trust is not something obtained by demanding it, but something built by gradually offering it to one another.
The most important infrastructure is trust
Come to think of it, there isn't much we can do alone. No matter how outstanding a person is, they cannot know every field. They cannot do every task personally, nor can they verify every result from start to finish by themselves.
Ultimately, we accept the results of others and start our own work on top of that. If there is no trust in that process, everything must be doubted.
Conversely, if there is trust, it doesn't mean you don't verify. Because you know what can be trusted, you can verify what is truly important.
There must be trust to entrust work. There must be trust to connect each other's judgments. There must be trust to speak up when there is a problem. There must be trust for unpleasant stories to be delivered. And there must be trust for the abilities of different people to be connected as one.
Therefore, I do not think of trust simply as a good value for human relationships. Trust is the infrastructure that allows information to flow, enables work to be divided, and allows an organization to see its true self.
Ability increases the size of the work I can do. But trust increases the size of the work we can do together.
That is why I want to be a trustworthy person as much as I want to be a person who is good at their job. A person whose words others can believe. A person who allows others to let go of the tasks they've entrusted with peace of mind. A person people want to talk to when a problem arises, rather than hiding it.
And a person whose actions can be trusted even when they are wrong.
When such people trust and connect with each other, their individual abilities finally become the organization's ability. That is why the most important infrastructure, in my opinion, is trust.
A Trip to Suncheon and Yeosu, Day 3
The last day, ending with some studying and a run.

A Trip to Suncheon and Yeosu, Day 2
The second day of the trip, from a clear morning by the sea to sunset and dusk on Baekyado Island.

A Trip to Suncheon and Yeosu
A trip to Suncheon and Yeosu.


Comments 0
Share your thoughts on this article.
Loading comments…