✍️ 필사 모드: The Complete Leadership Guide — The Art of Leading People, The Wisdom of Growing Organizations

• Introduction: Why Leadership Matters
• 1. What Is Leadership
  • 1.1 Defining Leadership
  • 1.2 Management vs. Leadership
  • 1.3 Three Levels of Leadership
• 2. Leadership Styles
  • 2.1 Servant Leadership
  • 2.2 Transformational Leadership
  • 2.3 Situational Leadership
  • 2.4 Coaching Leadership
• 3. Psychological Safety
  • 3.1 Google's Project Aristotle
  • 3.2 How to Build Psychological Safety
• 4. Running Effective 1:1 Meetings
  • 4.1 The Purpose of 1:1 Meetings
  • 4.2 Effective 1:1 Agenda Structure
  • 4.3 Common 1:1 Mistakes to Avoid
• 5. The Art of Feedback
  • 5.1 The SBI Feedback Model
  • 5.2 Feedback Frequency and Timing
  • 5.3 Receiving Feedback as a Leader
• 6. Delegation
  • 6.1 Why Delegation Is Difficult
  • 6.2 An Effective Delegation Framework
• 7. Decision-Making Frameworks
  • 7.1 The RAPID Model
  • 7.2 Principles for Faster Decision-Making
• 8. Crisis Leadership
  • 8.1 Leadership Principles During a Crisis
  • 8.2 Incident Leadership
  • 8.3 The Leader's Role in Postmortems
• 9. Team Building: The Tuckman Model
  • 9.1 Five Stages of Team Development
  • 9.2 Why You Must Not Skip the Storming Stage
• 10. Self-Leadership
  • 10.1 What Is Self-Leadership
  • 10.2 Core Elements of Self-Leadership
  • 10.3 Energy Management
• 11. Tech Leadership: CTO, TL, and EM
  • 11.1 Three Tech Leader Roles
  • 11.2 Tech Lead Leadership
  • 11.3 Engineering Manager Leadership
  • 11.4 TL vs. EM: Which Path to Choose
• 12. Leadership Checklist
  • 12.1 Daily Checklist
  • 12.2 Weekly Checklist
  • 12.3 Monthly Checklist
• 13. Recommended Books and Resources
  • Essential Reading
  • By Leadership Style
• Conclusion: Leadership Is a Journey

Introduction: Why Leadership Matters

Leadership is not a title; it is behavior. Peter Drucker defined leadership as simply having followers. If no one follows you despite your title, you are not a leader. If people follow you without any title, you are.

The importance of leadership in modern organizations continues to grow. According to Google's Project Oxygen research, teams led by good managers had significantly lower turnover rates and noticeably higher performance scores. A single leader has a decisive impact on an entire team's performance and well-being.

Yet leadership training in many organizations remains superficial. Engineers become seniors and naturally assume leadership roles, but they rarely receive formal training in people skills. This article provides a comprehensive guide covering leadership definitions, diverse styles, core skills, and leadership unique to the tech industry.

1. What Is Leadership

1.1 Defining Leadership

There are hundreds of definitions of leadership, but the core can be summarized in three points:

1. Setting Direction: Presenting a vision of where to go
2. Motivating People: Getting people to move voluntarily
3. Enabling Execution: Removing obstacles and creating the right environment

John Maxwell said that leadership is influence, nothing more and nothing less. This definition is simple but profound. Regardless of rank, authority, or compensation, the ability to affect others' thoughts and actions is leadership.

1.2 Management vs. Leadership

Warren Bennis distinguished the two: managers do things right, while leaders do the right things. In practice, the two roles are inseparable, and good leaders need management skills as well.

1.3 Three Levels of Leadership

Level 1 - Self-Leadership

The ability to manage yourself. This includes time management, emotional regulation, continuous learning, and self-motivation. Before you can lead others, you must be able to lead yourself.

Level 2 - Team Leadership

The ability to lead a small group. Goal setting, role allocation, conflict resolution, and performance management are key. Most leadership discussions focus on this level.

Level 3 - Organizational Leadership

The ability to design culture, strategy, and systems for an entire organization. Vision creation, organizational structure design, and developing other leaders are the essentials.

2. Leadership Styles

2.1 Servant Leadership

Proposed by Robert Greenleaf in 1970, this philosophy holds that a leader's role is to "serve" their team members.

Core Principles:

• Listening: Genuinely paying attention to what others say
• Empathy: Understanding from the other person's perspective
• Healing: Resolving wounds and conflicts within the team
• Awareness: High awareness of self and environment
• Persuasion: Leading through persuasion rather than authority
• Growth: Helping team members grow personally and professionally

Practical Application:

A Servant Leader's Daily Routine Example:
- 09:00 Ask each team member: "Is there anything I can help with today?"
- 10:00 Focus on removing blockers for team members
- 14:00 Discuss team member career goals in 1:1 meetings
- 16:00 Share team achievements with upper leadership under team members' names

2.2 Transformational Leadership

Proposed by James MacGregor Burns, this style transforms team members' values and motivations to achieve performance beyond expectations.

Four Components (4I):

1. Idealized Influence: The leader becomes a role model and earns trust
2. Inspirational Motivation: Presenting a compelling vision and giving meaning
3. Intellectual Stimulation: Challenging existing assumptions and encouraging creative thinking
4. Individualized Consideration: Responding to each team member's unique needs

Characteristics of Transformational Leaders:

• They do not settle for the status quo and pursue continuous improvement
• They are not afraid to ask "Why are we doing it this way?"
• They turn failures into learning opportunities
• They identify and leverage each team member's strengths

2.3 Situational Leadership

Developed by Paul Hersey and Ken Blanchard, this model proposes that leaders should flexibly adjust their style based on team members' competence and motivation levels.

Practical Example:

For a junior developer, conduct thorough code reviews and provide specific guidance (S1/S2). For a senior developer, share only the goal and let them decide on the approach (S4). Even for the same person, S2 may be appropriate when learning new technologies, while S4 fits their area of expertise.

2.4 Coaching Leadership

Coaching leadership helps team members find their own answers through questions, rather than providing the answers directly.

The GROW Model:

1. Goal: "What do you want to achieve this quarter?"
2. Reality: "Where are things right now? How far along are you?"
3. Options: "What approaches could you take? Any alternatives?"
4. Will: "So what specifically will you do, and by when?"

The Power of Coaching Questions:

Bad example: "Fix this bug by doing it this way." Good example: "What do you think is the root cause of this bug? What approaches might work?"

Coaching leadership takes more time in the short term but builds the team's problem-solving ability and autonomy in the long run.

3. Psychological Safety

3.1 Google's Project Aristotle

From 2012 to 2015, Google analyzed 180 teams to uncover the secrets of high-performing teams. Surprisingly, the most important factor was not "who is on the team" but "how the team collaborates."

Five Factors of High-Performing Teams (by importance):

1. Psychological Safety: The belief that you will not be punished for making mistakes
2. Dependability: Trust that team members will deliver quality work on time
3. Structure and Clarity: Clear roles, plans, and goals
4. Meaning: The work itself is personally meaningful
5. Impact: The belief that your work makes a difference

The finding that psychological safety ranked first shocked many organizations. Even assembling the best talent yields poor results without psychological safety.

3.2 How to Build Psychological Safety

Based on research by Professor Amy Edmondson of Harvard Business School.

Leader Behaviors:

1. Show vulnerability first: Admit "I'm not sure about this either" before expecting others to do so
2. Welcome questions: Start with "That's a great question" for every inquiry
3. Learn from failure: Instead of blame, ask "How can we do better next time?"
4. Encourage diverse opinions: Ask silent members for their thoughts in meetings
5. Protect dissent: Make it a habit to say "If anyone disagrees, please speak up"

Self-Assessment Questions for Psychological Safety:

• What happens on our team when someone admits a mistake?
• Is it comfortable to express a dissenting opinion to a manager?
• Can people say "I don't know" without fear?
• When someone proposes a new idea, does the team listen?

4. Running Effective 1:1 Meetings

4.1 The Purpose of 1:1 Meetings

1:1 meetings are the most important communication channel between a leader and their team members. Andy Grove emphasized the 1:1 as a manager's core tool in High Output Management.

The 1:1 belongs to the team member. The team member drives the agenda, and the leader listens and supports.

4.2 Effective 1:1 Agenda Structure

1:1 Meeting Agenda Template (30 minutes)
-----------------------------------------
[0-5 min]   Check-in / rapport building
[5-15 min]  Team member agenda (concerns, blockers, ideas)
[15-25 min] Feedback exchange or career discussion
[25-30 min] Action items and next meeting prep

4.3 Common 1:1 Mistakes to Avoid

1. Devolving into status reports: Share project progress through async tools
2. Repeating the same questions: Prepare a diverse question pool
3. Leader dominating the conversation: Keep leader talk-time under 30%
4. Ending without action items: Define at least one concrete action per meeting
5. Repeatedly canceling: Never cancel a 1:1. If unavoidable, always reschedule

5. The Art of Feedback

5.1 The SBI Feedback Model

Developed by the Center for Creative Leadership (CCL), the SBI model is the most practical feedback framework.

• S (Situation): When and where (specific context)
• B (Behavior): What was done (observable behavior)
• I (Impact): What effect that behavior had

Good Feedback Example:

"In yesterday's architecture review (S: Situation),
you presented data-backed counterarguments against the new design (B: Behavior),
which helped the team identify potential risks early
and make a better decision. (I: Impact)"

Bad Feedback Example:

"I wish you'd work harder lately."
-> No specific situation, no observed behavior, no impact

5.2 Feedback Frequency and Timing

• Immediate feedback: Deliver within 24 hours of the behavior
• Regular feedback: Exchange at least one piece of feedback bi-weekly in 1:1 meetings
• Positive-to-improvement ratio: Research suggests a ratio of approximately 5:1 between positive and improvement feedback is most effective

5.3 Receiving Feedback as a Leader

Leaders must also receive feedback. To encourage upward feedback:

1. Regularly ask "What is one thing I could improve?"
2. Respond without defensiveness: "Thank you. Can you tell me more?"
3. Share actions taken on feedback to show that input is valued and acted upon

6. Delegation

6.1 Why Delegation Is Difficult

The most common reasons leaders fail to delegate:

• "It's faster if I do it myself"
• "Teaching takes too much time"
• "What if they make mistakes?"
• "I feel like I'm losing my purpose"

But without delegation, the leader becomes a bottleneck and team members stop growing.

6.2 An Effective Delegation Framework

Five Steps of Delegation:

1. Define the outcome: Clarify what needs to be achieved (the result, not the method)
2. Set guidelines: Explain constraints and degrees of freedom
3. Secure resources: Provide necessary authority, budget, and tools
4. Agree on checkpoints: Set intermediate review points in advance
5. Evaluate results: Assess based on outcomes, not process

Delegation Level Matrix:

7. Decision-Making Frameworks

7.1 The RAPID Model

Developed by Bain and Company, the RAPID model clarifies decision-making roles in organizations.

• R (Recommend): The person who analyzes options and makes a recommendation
• A (Agree): The person who must agree before execution (holds veto power)
• P (Perform): The person who carries out the decision
• I (Input): The person who provides opinions and information
• D (Decide): The person who makes the final call

RAPID Model Example: Selecting a New Tech Stack
-----------------------------------------
R (Recommend): Senior Engineer - technical evaluation and proposal
A (Agree): Security Team - confirming security requirements are met
P (Perform): Development Team - executing the migration
I (Input): DevOps, QA Teams - operational and testing perspectives
D (Decide): CTO - final decision

7.2 Principles for Faster Decision-Making

Drawing from Jeff Bezos' decision-making principles at Amazon:

1. Reversible vs. Irreversible decisions: Reversible decisions (Type 2) should be made quickly; irreversible decisions (Type 1) require careful deliberation
2. The 70% rule: Decide when you have 70% of the information you need. Waiting for 90% means you are too late
3. Disagree and Commit: After discussion, once a decision is made, everyone commits fully to execution even if they initially disagreed

8. Crisis Leadership

8.1 Leadership Principles During a Crisis

Whether facing outages, reorgs, or major attrition, a leader's behavior during a crisis has a far greater impact than during normal times.

Five Principles of Crisis Leadership:

1. Communicate quickly: Even under uncertainty, communicate fast. Silence amplifies anxiety
2. Fact-based transparency: Clearly distinguish between what you know, what you do not know, and what you suspect
3. Acknowledge emotions: Validate feelings: "It's completely natural to feel anxious right now"
4. Clarify priorities: You cannot do everything during a crisis. Focus on the one or two most important things
5. Care and recovery: After the crisis, watch for burnout and give the team time to recover

8.2 Incident Leadership

Leader's Incident Response Checklist:
-----------------------------------------
[ ] Designate an Incident Commander (or take the role)
[ ] Establish a communication channel (Slack channel, video call)
[ ] Assess the current situation (blast radius, severity)
[ ] Assign roles (investigation, communication, decision-making)
[ ] Provide periodic status updates (internal + external)
[ ] Schedule a postmortem after resolution
[ ] Express gratitude to the responding team members

8.3 The Leader's Role in Postmortems

In postmortems, the leader must focus on "Why did the system fail?" rather than "Who was at fault?" To build a blameless postmortem culture:

• Ask "What structural conditions made this mistake possible?" instead of "Why did you make this mistake?"
• Look for improvements in processes, tools, and systems rather than blaming individuals
• Every action item must include an owner and a deadline

9. Team Building: The Tuckman Model

Bruce Tuckman's 1965 team development model remains the most widely used.

9.1 Five Stages of Team Development

9.2 Why You Must Not Skip the Storming Stage

Many leaders fear the Storming stage, but teams that do not properly go through it cannot reach the true Performing stage. Surfacing and resolving differences during Storming builds the foundation of trust.

How to Navigate Storming Healthily:

1. Communicate to the team that conflict is a normal process
2. Clearly distinguish between disagreement on ideas and personal attacks
3. Co-create team norms (a Team Agreement)
4. Agree in advance on "How will we handle disagreements?"

10. Self-Leadership

10.1 What Is Self-Leadership

It is the ability to lead yourself before leading others. Daniel Goleman, in his work on Emotional Intelligence, identified self-awareness and self-management as the foundation of leadership.

10.2 Core Elements of Self-Leadership

Self-Awareness:

• Can you recognize your emotional state in real time?
• Do you honestly know your strengths and weaknesses?
• Are you aware of your behavioral patterns under stress?

Self-Regulation:

• Can you pause before reacting when angry?
• Can you remain calm and make sound judgments in ambiguous situations?
• When you fail, can you shift from self-blame to learning?

Motivation:

• Can you maintain consistent motivation without external rewards?
• Can you endure short-term discomfort for a long-term goal?
• Do you have an answer to "Why do I do this work?"

10.3 Energy Management

A leader's most important resource is not time but energy.

Energy Management Matrix:
-----------------------------------------
Energy-Giving Activities       | Energy-Draining Activities
-----------------------------------------
Deep focused work              | Endless meetings
Meaningful 1:1 conversations   | Political conversations
Exercise and walking           | Multitasking
Witnessing team growth         | Repetitive report writing
Learning and reading           | Unnecessary email processing

11. Tech Leadership: CTO, TL, and EM

11.1 Three Tech Leader Roles

In the tech industry, "leader" can mean several different roles. Understanding each clearly is essential.

11.2 Tech Lead Leadership

A Tech Lead writes code while simultaneously guiding the team's technical direction.

Core TL Competencies:

1. Technical judgment: Analyzing tradeoffs and making sound technology choices
2. Design ability: Decomposing complex problems into simple structures
3. Code review: Setting standards for code quality and consistency
4. Tech debt management: Balancing business demands with technical quality
5. Mentoring: Providing technical growth support for junior developers

Common TL Pitfalls:

• Trying to own all design decisions (under-delegating)
• Getting absorbed in coding and losing sight of the team's overall direction
• Imposing personal technical preferences on the team

11.3 Engineering Manager Leadership

An Engineering Manager focuses on people and processes.

Core EM Competencies:

1. Hiring and onboarding: Finding great talent and helping them ramp up quickly
2. Performance management: Setting expectations, providing feedback, and evaluating performance
3. Team culture: Fostering psychological safety, collaboration, and learning
4. Stakeholder management: Managing relationships with upper leadership and other teams
5. Process design: Optimizing sprint planning, retrospectives, and code review processes

11.4 TL vs. EM: Which Path to Choose

Charity Majors (Honeycomb CTO) proposed the pendulum theory for IC and manager tracks. Rather than staying on one track, alternating between IC and manager roles to understand both perspectives creates the strongest leaders.

Questions to Help You Decide:

• What excites you most in the morning: solving technical problems or watching people grow?
• What is the best moment of your day: completing clean code or witnessing a team member's growth?
• Does dealing with ambiguous interpersonal issues give you energy or drain it?

12. Leadership Checklist

A leadership checklist you can use daily, weekly, and monthly.

12.1 Daily Checklist

Daily Leadership Check:
-----------------------------------------
[ ] Did I greet team members and ask how they are doing?
[ ] Did I help a team member with a blocker?
[ ] Did I deliver at least one piece of positive feedback?
[ ] Did I seek team input on an important decision?
[ ] Was I a bottleneck anywhere today?

12.2 Weekly Checklist

Weekly Leadership Check:
-----------------------------------------
[ ] Did I have a 1:1 with every direct report?
[ ] Did I deliver at least one specific SBI feedback?
[ ] Am I aware of the team's progress and blockers?
[ ] Did I delegate tasks that could be delegated?
[ ] Did I check the team's morale and energy level?

12.3 Monthly Checklist

Monthly Leadership Check:
-----------------------------------------
[ ] Did I have a career development conversation with each team member?
[ ] Did I review the team's goal achievement rate?
[ ] Did I assess the team's culture and psychological safety?
[ ] Did I check my own energy level and burnout signals?
[ ] Did I ask for feedback from my peers or manager?
[ ] Did I invest in leadership learning (books, articles, podcasts)?

13. Recommended Books and Resources

Recommended resources for deepening your leadership knowledge.

Essential Reading

1. The Manager's Path (Camille Fournier) - The leadership journey from engineer to CTO
2. Radical Candor (Kim Scott) - The art of direct yet caring feedback
3. An Elegant Puzzle (Will Larson) - A systems approach to engineering management
4. High Output Management (Andy Grove) - Optimizing managerial output
5. The Five Dysfunctions of a Team (Patrick Lencioni) - The five causes of team failure

By Leadership Style

• Servant Leadership: The Servant Leader (James Autry)
• Coaching Leadership: The Coaching Habit (Michael Bungay Stanier)
• Emotional Leadership: Primal Leadership (Daniel Goleman)
• Situational Leadership: Leadership and the One Minute Manager (Ken Blanchard)

Conclusion: Leadership Is a Journey

Leadership is a journey, not a destination. There is no perfect leader; every leader learns and grows every day.

The common trait of the greatest leaders is the humility to acknowledge that they still have room to grow. Jim Collins, in Good to Great, identified the "paradoxical combination of humility and will" as the hallmark of Level 5 leaders. Leaders who combine personal humility with professional determination build great organizations.

The ultimate measure of leadership is not the leader's own success but the growth of their team members. If the team thrives after you leave, you are a great leader. If the team only functions when you are present, you are not yet a leader but a bottleneck.

Start with just one thing today. Sincerely ask a team member, "Is there anything I can help you with?" That is the first step of leadership.