[태그:] team management

  • When a Kind Leader Starts Hurting the Team: Team-Control Lessons from Takmin Oh

    When a Kind Leader Starts Hurting the Team: Team-Control Lessons from Takmin Oh

    Does a good leader always have to be kind? This question is more difficult than you think in the workplace. A kind tone is clearly necessary, but if a leader cannot express uncomfortable standards, team members will actually become more anxious.

    In the Career Day video, author Takmin Oh explains this issue with the idea that “having a bad personality does not make someone a bad leader.” The key is not personality, but standards. If team members do not know what the leader wants, what they reward, or what behavior they want to repeat, the team will not move.

    An interview scene explaining the meaning of leadership that helps the team
    Leadership is closer to creating standards that allow the team to move than to using kind language.

    The moment a kind leader becomes dangerous

    Being a kind leader is not always bad. The problem arises when kindness becomes conflict avoidance. If a leader cannot say what needs to be said, blurs performance standards, and makes team members guess, kindness is closer to neglect than leadership.

    Team members want predictable standards rather than a leader’s mood. They want to know what to do first, how much to do, and what behavior is good. If the leader does not express those standards, team members will continue to guess.

    Author Ohtakmin talking about leadership that treats members kindly
    Kindness is necessary, but without standards, team members may actually feel anxious about the leader.

    The problem is not personality, but the “absence of one’s own thoughts”

    One impressive point in the video is the criticism that many leaders do not know their own thoughts well. If a leader does not know what they want, feedback will also be unclear. Saying “let’s do well” is gentle, but it is not an execution standard.

    Therefore, leaders must first organize their thoughts into sentences. They must be able to say what results are important in this team, what behaviors create those results, and what habits they should stop now.

    The state of the leaderWhat team members feelThe result that occurs in the organization
    Kind but has no standardsIt’s hard to know what’s done wellGuessing and speculation increase
    Strict but lacks explanationOnly the reason for scolding remainsA defensive atmosphere is created
    Speak the standards and act on themIt’s clear what to repeatThe team’s learning speed accelerates

    The 3 layers of a leader: thought, speech, action

    Leadership is not determined by a single tone of speech. Thoughts, words, and actions must be consistent. If you have high standards in your mind but don’t express them, your team won’t know. On the other hand, if your words are great but the actual rewards are different, the team will follow the rewards, not the words.

    Interview scene explaining what leaders should say and the standards they should have
    A good leader expresses their thoughts and standards in words so that team members do not have to guess.
    • Thoughts: What results does our team truly value?
    • Words: Were those standards conveyed to team members in understandable sentences?
    • Actions: Were those standards consistently applied in actual meetings, feedback, and rewards?

    If these three are inconsistent, a leader’s reputation can be easily shaken. A reputation for being a good person can remain, but it’s difficult to earn trust as a leader who grows the team.

    Why behavior should be rewarded, not results

    Results are important. However, if only results are rewarded, luck, market conditions, and differences in existing resources are mixed in. It’s difficult for team members to learn what they should repeat. Therefore, author Ok-tak Min emphasizes that behavior should be rewarded.

    Focusing on behavior does not mean ignoring results. It means finding the process that creates good results and converting that process into repeatable language. For example, ‘We increased sales’ is less learnable feedback than ‘We recorded customer questions and reflected them in the next proposal.’

    An interview scene in the context that behavior, not results, should be rewarded
    When an organization focuses on repeatable behavior rather than results, it grows more stably.
    Reward CriteriaLeader’s QuestionTeam’s Remaining Learning
    Performance-BasedWere this month’s numbers good?Interpreted as a mix of luck and skill
    Action-BasedWhat actions contributed to the performance?Can be repeated next time
    Learning-BasedWhat was changed from the failure?Attempts and improvements accumulate

    5 Checklists That Team Leaders Can Apply Immediately

    • This week, I will tell you the top priority that team members must know in one sentence.
    • Instead of saying “let’s do our best”, I suggest observable behavioral standards.
    • For those who have achieved good results, I ask not only about the outcome but also about repeatable behaviors.
    • I don’t delay feedback, and I deliver it in short, small units of behavior.
    • I bring both kind tone and clear standards together, without choosing just one.

    A growing organization moves based on standards, not a leader’s personal preference.

    A team member liking their leader and a team growing are different things. Of course, if the relationship is bad, work becomes difficult. However, if the relationship is good but there are no standards, the team can become complacent and stagnant.

    A good leader is not someone who pushes people, but someone who prevents team members from having to guess. A good leader tells team members what to do, observes good behavior, and creates a structure that allows for retrying. Therefore, leadership is closer to a design problem than a personality problem.

    A scene of an interview explaining the role of growing organizations and leaders
    The leadership that moves a team is the power to design structures and repeatable behaviors, rather than personal preference.

    Recommended reading

    FAQ

    Are Nice Leaders Really Bad Leaders?

    No, being nice is not the problem. However, if niceness is used as a way to avoid conflict and fail to set standards, it can confuse team members even more.

    What should the team leader change first?

    Organizing their thoughts into clear sentences. We must be able to articulate the important results and actions that produce those results in our team.

    Does saying to reward behavior rather than performance mean to ignore performance?

    No, it means to find the repeatable behaviors that produce the performance. That way, team members can improve in the same way next time.

    What is more important, kindness or strictness?

    It’s not a matter of choosing one over the other. Both a kind attitude and clear standards are necessary for team members to challenge themselves safely.

    Where can I watch the original video of this article?

    The Career Day YouTube video “Having a bad personality doesn’t make you a bad leader”can be found in

    Reference

    Image source: The capture image used in the text is from the original YouTube videoand was used as a quoted image for review, commentary, and educational purposes. The image copyright belongs to the original author and the channel.

    Original Korean article: https://www.thinknote.co.kr/leadership-kind-leader-team-management/

  • Your Teammate May Not Be Slow: The Difference Between Method and Speed That Leaders Miss

    # Your Teammate May Not Be Slow: The Difference Between Method and Speed That Leaders Miss

    “Why are you so slow?”

    It is one of the easiest things for a leader to say. But it is not always the right diagnosis. The teammate may not be slow; the leader may be reading the problem incorrectly.

    Imagine cooking ramen. The leader says, “Make ramen quickly.” The teammate puts the noodles in first. The leader immediately says, “Why did you put the noodles first? The seasoning should go in first.”

    The issue here is not speed. It is method: noodles first or seasoning first, how much water, what texture is desired. If the leader only says “faster,” the teammate is confused. Should they move faster, change the sequence, or ask for the standard again?

    The small metaphor shows a core leadership point: do not interpret a difference in method as a difference in speed.

    ## The first problem leaders miss: there may be no shared standard

    When work differs from expectations, leaders often see only the result: late, insufficient, frustrating. So they press for speed. But the teammate may not know what to prioritize, whether the output is a draft or final version, what quality is enough, whose opinion must be reflected, or whether it is safe to ask again after a failed attempt.

    In that situation, “do it quickly” hides the real problem. People move faster, but not in the direction the leader wanted, and rework grows.

    ## Situational leadership: different people need different leadership

    Situational leadership argues that effective leaders do not insist on one style. They adjust directing, coaching, supporting, and delegating based on task difficulty, skill, and confidence.

    A beginner cooking ramen needs concrete sequence, water amount, heat level, and timing. “Just do it quickly” is close to neglect. A skilled person, however, may not need micromanagement about seasoning order. They need outcome standards and autonomy.

    A good leader asks: “Does this person need pressure for speed, explanation of method, alignment on standards, or delegated authority?”

    ## Transformational leadership: people move longer for meaning than speed

    Transformational leadership connects people to purpose and vision. “Make ramen quickly” is a task instruction. “We have five minutes before the meeting, so speed matters more than taste” explains purpose. “This is for a guest, so texture and broth matter even if it takes one more minute” shares a standard.

    When purpose changes, the right method changes. In organizations, if leaders do not explain purpose, people defend methods. When purpose is shared, methods can be discussed.

    ## Servant leadership: remove blockers before blaming people

    Servant leadership sees leaders as people who help others grow and perform. The better question before “Why couldn’t you do it?” is “What is blocking you?”

    • Was the necessary information available?
    • Was the decision-maker clear?
    • Were tools and materials ready?
    • Were priorities conflicting?
    • Was there room to ask questions midway?

    A leader who pushes people can create momentary speed. A leader who removes obstacles improves the quality of the next execution.

    ## Psychological safety: teams get faster when people can speak

    Psychological safety is the belief that questions, concerns, mistakes, and dissent can be voiced without punishment or humiliation. Fast teams need this safety.

    People should be able to say, “I thought putting noodles in first was better, and here is why,” or “If seasoning first was the standard, I wish I had known at the start.” Teams that can have this conversation learn quickly. Teams that cannot speak quietly repeat the same mistakes.

    ## Decision leadership: if nobody knows who decides, everyone slows down

    Repeated speed problems often come from unclear decision roles. Frameworks such as Atlassian’s DACI separate driver, approver, contributor, and informed parties.

    Even ramen has roles: who cooks, who defines taste, who eats, and who decides it is good enough. In work, unclear authority creates safe choices, late approvals, and rework.

    ## In the AI era, faster creation requires more precise questions

    AI tools make drafts, summaries, reports, code, images, and slides faster. But faster creation does not guarantee good outcomes. “Do it quickly with AI” sounds powerful, but it demands more judgment from leaders.

    • Which 60–80 point work can AI handle?
    • Which 20–40 point judgment must remain human?
    • What is the quality standard?
    • How will sources and results be verified?
    • Who has final responsibility?

    ## Five questions good leaders ask first

    • Purpose: is speed, quality, or learning most important?
    • Method: what problem is this method trying to solve?
    • Standard: what counts as done and good enough?
    • Role: who decides, advises, and executes?
    • Obstacle: is the blocker willpower, tools, information, authority, or standards?

    ## Related reading

    ## Conclusion: leadership aligns judgment before it raises speed

    Cooking ramen quickly and deciding how ramen should be cooked are different problems. Teamwork is the same. If leaders mistake method differences for speed differences, teammates may move faster without making better judgments.

    Good leaders do not deny speed. They ask about purpose first, discuss method, align standards, define roles, and remove blockers. Then the team does not merely move faster; it starts moving in the same direction.

    ## FAQ
    ### How can I tell whether a teammate is slow or simply using a different method?
    If goals and standards are clear and time still stretches, it may be speed. If goals, sequence, roles, or quality standards are unclear, treat it first as a method problem.
    ### Is it wrong for leaders to say “do it quickly”?
    No, but they should also explain why speed matters, what level is enough, and what may be omitted.
    ### How does situational leadership connect to this metaphor?
    Beginners may need concrete methods; experienced people may need standards and delegated authority.
    ### Why is this more important in the AI era?
    AI can create fast drafts, but without purpose and criteria those drafts create faster confusion. Leaders must design judgment standards and verification loops.
    ## References

    Original Korean article