• Thoughts

Good intentions alone do not make a good team

Sharing, recording, and reviewing should not be left solely to diligence. It is about creating tools and environments where positive behaviors are naturally repeated.

Good tools and environments allow anyone to carry good practices forward.

To build a great team, you need great people. People who are responsible, people who are good at their jobs, people who share when problems arise, and people who listen to others' opinions to solve problems together. Naturally, it is great when such people gather.


However, simply gathering great people does not create a great team. An environment where great people can work in a great way is also necessary.

Rather than demanding good behavior, we must make it easy

There are things frequently said in teams. "Please share your progress often." "Please organize the meeting notes well." "Please document things properly." "Please do code reviews." "Please speak up quickly when a problem occurs." All of these are correct.


But can we continue to leave these things solely to a person's diligence? If someone has to ask for progress every time, it might be seen as a problem with the person who isn't sharing.


However, if we use a tool where everyone's progress is naturally visible, there is no need to ask.


If someone has to remember what was decided in a meeting, people will start to remember it differently over time. "I never heard it that way." "Didn't we agree to do it this way back then?"


It may seem like a problem of human memory or meticulousness, but it might be a problem that wouldn't have occurred in the first place if there had been an environment where decisions could be naturally recorded. Code reviews are similar.


Rather than asking, "Please look over each other's code when you have time," it lasts much longer to create a process where code naturally goes through a review to be merged.

It is more important to create an environment where it is easy to behave well than to constantly demand good behavior from people.

Good tools reduce what is required of people

That is why I believe good tools are important. A good tool is not simply a program that makes work convenient. It is a mechanism that reduces what must be demanded of people.


One should be able to know the current status without someone having to report diligently, find past decisions without someone having to remember everything, see what needs to be done without someone constantly checking, and know who to ask when a problem arises. Using good tools does not make people more diligent.


Instead, the team continues to function even on days when people are slightly less diligent. Humans are not always perfect. There are busy days, times when we forget, and times when we are not feeling our best. If a team only runs when one specific person takes care of everything, the team shakes the moment that person becomes busy.


Therefore, when building a team, one must consider the environment as much as the people.

Tools should not become the work

That said, more tools are not necessarily better. Introducing new tools is easy. You can create project management tools, messengers, wikis, document repositories, and dashboards.


But once you start worrying about where to write what, the tools themselves become the work. I believe the criterion for a good tool is not whether it has many features, but how naturally it enables us to work in the way we desire.


Information is shared without being told to share, records are kept without being told to record, and the necessary people check things without being told to check.


A good culture becomes part of how we work, rather than depending solely on people’s willpower.

Good tools make good methods repeatable

I believe the value of a good tool lies in enabling the entire team to repeat a method that a specific person is good at. When work that relied solely on someone's memory and diligence is moved into structure and flow, work can continue in the same way even when new people join.


Things that relied on human memory are changed to records, things that relied on reading the room are changed to shared information, and things that relied on human diligence are changed to systems.


That is why I believe that when starting a new team, we must consider not only what technology to use, but also how we will work and what tools and processes will make that method natural.


A great team is not maintained by the will of great people alone. Even if great people get a bit tired, someone makes a mistake, or a new person joins, the methods we value must be able to continue.

I believe a good tool is not a replacement for people, but an infrastructure that leaves those methods within the team so that great people can continue to work in a great way.

Comments 0

Share your thoughts on this article.

Comment inquiries

Loading comments…

A Trip to Suncheon and Yeosu, Day 3

The last day, ending with some studying and a run.

Seungmin Yang

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.

Seungmin Yang

A Trip to Suncheon and Yeosu

A trip to Suncheon and Yeosu.

SkyDive Team
See all