Leadership Style: Style Is a Toolkit, Not a Personality
Topic: Leadership Style·4 Principles
"Leadership style is not a function of personality but a strategic choice." — Daniel Goleman
This week's thesis: Many people treat "leadership style" as personality — "I'm just a blunt person." That's the biggest misconception: style is a switchable toolkit, not a personality welded on at the factory. Goleman's data on 3,871 executives proves that leaders who use only one style perform worst, while those who fluidly switch among four or more perform best. Four things this week: switching the six styles by situation, adjusting your gear to people of different maturity, the dosage of vulnerability, and avoiding the "authenticity paradox." The core isn't "be yourself" — it's widening the bandwidth of "yourself."
PRINCIPLE 01
Switch the Six Styles by Situation: Don't Hit Every Nail With One Hammer
Six Styles, Switched by Situation
Style LibrarySituationGoleman
Principle in One Line
The worst leader uses one style for life and calls it "being authentic." The best leader is like a golfer — pulling the right club out of the bag for this particular shot. Each of the six styles has its use and its cost.
In Their Own Words
"Leaders who have mastered four or more—especially the authoritative, democratic, affiliative, and coaching styles—have the very best climate and business performance."— Daniel Goleman,《Leadership That Gets Results》HBR, 2000
Six Styles · When to Use · The Cost
Scene
Context: You're a tech lead manager. Monday, a production incident. Wednesday, a senior engineer is lost about an architecture direction. Same week, two events.
✗ One style for everything
You're an affiliative person, so during the incident you're still asking "Everyone okay? No pressure" — the fire is burning, the team needs someone to make the call. Three days later you switch to commanding with the lost engineer: "Just go with Plan A" — but he needed to think it through together, not be ordered. Both times you used the wrong club.
✓ Switch by situation
During the incident (commanding, time-boxed): "I'm making the call now. Roll back to the last version, Zhang watches monitoring, Li sends the customer notice, we sync in 15 minutes. Postmortem tomorrow." — In a crisis, democracy is a luxury; stop the bleeding first.
Three days later with the senior engineer (coaching): "Between Plan A and B, which long-term cost worries you more? Looking back three years from now, what would you want us to have decided today?" — Give thinking space, not the answer.
Checklist: Widen Your Style Bandwidth
Which is my "default style"? Did I use it 80% of the time over the past month?
Which two of the six do I almost never use? Those are exactly my blind spots.
Did I use commanding/pacesetting this week? Was it a real crisis, or just impatience?
When I switch styles, do I signal it to the team? ("I'll call this one" vs "I want to hear you all on this")
Common Mistakes
Treating your default style as a personality totem. "I'm just a straight-shooter" — that's not authenticity, it's not bothering to grow a second style.
Pacesetting as a staple. The trap newly-promoted high performers fall into: sprinting out front, burning the team out, calling it "leading by example."
Doing democracy in a crisis. Asking "what does everyone think" with the building on fire dumps the decision on the team — that's not empowerment.
Female Leader's Note
Style switching carries an extra tax for women: research (Heilman's "role congruity" experiments) shows women using commanding/pacesetting are labeled "aggressive" far more often than men, while affiliative gets them dismissed as "nice but not enough of a leader." The fix isn't to use only safe styles — it's, when switching to a forceful style, one extra line that attributes it to the situation, not your temperament: "The time window is narrow, so I'm calling this directly now." — it weakens the label's grip.
Key References
Daniel Goleman,《Primal Leadership》 — the systematic expansion of the six styles and emotional intelligence, building on《Leadership That Gets Results》(HBR, 2000).
PRINCIPLE 02
Adjust to the Person: Equal Treatment of Unequals Is the Deepest Inequality
Situational Leadership — Match the Person
SituationalBlanchardDelegation Gears
Principle in One Line
For the same task, a beginner needs directing (high guidance), a veteran needs delegating (low guidance). Treating people of vastly different ability the same way is the most hidden form of unfairness.
In Their Own Words
"There's nothing so unequal as the equal treatment of unequals."— Ken Blanchard,《Leadership and the One Minute Manager》(Situational Leadership SLII)
SLII Four Gears: Set by the Person's Maturity "On This Task"
Scene
Context: A senior backend engineer on your team (S4) is assigned a totally unfamiliar frontend rewrite (where she's really S1–S2 on this task).
✗ Setting the gear by the person's overall level
"She's senior, just delegate." — You gave S4 freedom, but she stumbled in unfamiliar territory for two weeks, afraid to ask for help (afraid of looking unworthy of "senior"). Mismatch: you delegated by title, but on this task she needed an S2 coach.
✓ Setting the gear by maturity "on this task"
"On backend you're fully S4, I stay out of it. But frontend is new terrain for you, so let's run S2 at first: for the first two weeks I'll go over it with you every couple of days — not to check on you, but to help you dodge the pits I've fallen into. Once you're steady, we switch right back to delegating."
Key: say explicitly "this is temporary, by task not by person" to protect her dignity — downshifting a gear is not a demotion.
Checklist: Before Setting the Gear, Ask Yourself
Am I setting the gear by "this person's overall level" or "this task's specific maturity"? (The former almost always mismatches.)
On this task, does the person lack skill (give guidance) or lack confidence (give support)? The remedies differ.
Have I confused "downshifting a gear" with "demoting," making them feel diminished?
For S4 (delegating) people, am I still doing unnecessary check-ins, manufacturing micromanagement?
Common Mistakes
Micromanaging a senior S4. The most hurtful — what they read is "you don't trust me," not "you care."
Hands-off delegating to an S1 beginner. "I trust you to figure it out" sounds empowering but is really dodging the duty to guide.
Mistaking "lacks confidence" for "lacks skill." Flooding a capable-but-nervous person with guidance only deflates them more. They need S3 support.
Key References
Ken Blanchard & Paul Hersey,《Situational Leadership II / SLII》 — the classic framework matching style S1–S4 to a person's "development level D1–D4." Pairs with this series' Day 13 "Delegation & Letting Go."
PRINCIPLE 03
The Dosage of Vulnerability: Vulnerable Is Not Oversharing
The Dosage of Vulnerability
VulnerabilityTrustBoundaries
Principle in One Line
Showing vulnerability builds trust — but vulnerability is "disclosure with boundaries," not "emotional dumping." At the right dose it's courage; at overdose it turns the team into your emotional trash can.
In Their Own Words
"Vulnerability is not oversharing, it's sharing with people who have earned the right to hear our stories... Vulnerability minus boundaries is not vulnerability."— Brené Brown,《Daring Greatly》/《Dare to Lead》
Scene: How to Say "I Don't Know"
Context: In an architecture review, a senior engineer asks a deep question you can't answer. The whole team is watching you.
✗ Both extremes are wrong
Extreme A (bluffing): mumble out something that sounds like an answer — the senior people hear it on the spot, and trust starts leaking. Extreme B (over-vulnerable): "Honestly I've been under so much stress lately, not sleeping, I really can't crack this, I even doubt whether I deserve to lead this team…" — vulnerability has become a plea for comfort, and now the team has to take care of you.
✓ Dosed vulnerability
"I can't answer that right now — and I don't want to make something up. Give me until tomorrow; I'll check the real cost of that RPC layer and give you an accurate answer. If anyone already knows, say it now — I'll learn."
The dosage formula: admit not knowing (builds trust) + give a next step (stays reliable) + invite others (removes self-centering). Three things in one line, under 20 seconds.
Checklist: Dosage Self-Check Before Being Vulnerable
Purpose test: Am I saying this vulnerable thing for the team (build trust / model learning), or for myself (seek comfort / offload pressure)? For the latter, find a mentor or friend, not the team.
Audience test: Have the people in this room earned the right to hear this disclosure? Or am I oversharing to people I just met?
Landing test: Is there a "next step" after my vulnerability? Pure dumping with no action = dumping.
Frequency test: Am I occasionally vulnerable (powerful), or venting every week (team is fatigued)?
Common Mistakes
Treating "vulnerable" as "weak," so never showing it. Lencioni says the root of team trust is exactly "vulnerability-based trust" — the leader admits mistakes first, then others dare to.
Using the same dose upward and downward. Modest vulnerability with your team builds trust; pouring out your troubles to a boss still evaluating you may read as "can't handle it."
Backpedaling right after. "I was wrong… though honestly it's not entirely my fault" — once the hedge appears, the vulnerability is wasted.
Female Leader's Note
Vulnerability is asymmetric for women: the same "I'm not sure" is read as "candid, secure" from a male leader and "see, lacks confidence" from a woman — another face of the likability/competence tradeoff. The fix isn't to stop being vulnerable, but to pair vulnerability with competence: "I need to double-check the details (vulnerable) — but I'm confident in the conclusion; last quarter's data points the same way (competence)." Be vulnerable first, then anchor; the dose is unchanged, but you've calibrated how it's received.
Key References
Brené Brown,《Dare to Lead》 — "vulnerability is not weakness, it's our most accurate measure of courage," and the relationship between vulnerability and boundaries. Patrick Lencioni,《The Five Dysfunctions of a Team》 — "vulnerability-based trust" is the first cornerstone of a healthy team.
PRINCIPLE 04
The Authenticity Paradox: Don't Use "That's Not Me" as an Excuse Not to Grow
The Authenticity Paradox
AuthenticityGrowthIbarra
Principle in One Line
"Be yourself" is good advice and a dangerous trap. When a new behavior makes you uncomfortable, "that's not me" is often not loyalty to self but a respectable excuse for refusing to grow. The authentic self isn't a fixed statue — it's a draft you can experiment with and expand.
In Their Own Words
"Because going against our natural inclinations can make us feel like impostors, we tend to latch on to authenticity as an excuse for sticking with what's comfortable."— Herminia Ibarra,《The Authenticity Paradox》HBR, 2015
Scene
Context: You're an introverted tech lead, newly promoted to manager. The most visible figure in the company is that charismatic VP who's effortless on stage. You're advised to "speak up more at all-hands, network more." Your first reaction: "That's not my style."
✗ Using "authenticity" to seal off growth
"I'm a technical person, my work speaks for me; all that networking and stage performance isn't me." — Sounds principled, but three years later you find: influence all went to the people who can express themselves, and no one knows your good work. You stayed loyal to an outdated version of yourself.
✓ Ibarra's "playful experimentation" + Susan Cain's introvert version
Not imitating that VP's extroverted style (that would be the truly fake thing), but finding the introvert's own version: swap "improvising at the all-hands" for "writing a crisp technical memo circulated company-wide"; swap "cocktail-party networking" for "one deep 1:1 coffee a week" — still speaking up and building relationships, just through your medium and at your pace.
The mindset: "I'll try this new behavior on for a while; the discomfort is normal and doesn't mean it's inauthentic."
Checklist: Tell "Truly Not Me" From "Just Not Used to It Yet"
When I say "that's not my style," is it because it violates my values, or just because it makes me uncomfortable? Guard the former, try the latter.
Does the new behavior I resist have a version that "achieves the same purpose through my strength"? (An introvert's way of speaking up ≠ an extrovert's.)
Am I staying loyal to "the me of now," or to "the me I thought I was five years ago"?
Is this stretch moving me toward the leader I want to be, or just pleasing others' expectations? (The latter isn't worth doing.)
Common Mistakes
"Authenticity" = staying in the comfort zone. Explaining every discomfort as "inauthentic," so you never grow a new capability.
The other extreme: fully playacting someone else. An introvert forcing a charismatic-VP act reads as plastic to the team — worse than not speaking up. The boundary of authenticity: you can borrow a move, you can't swap your personality.
Waiting until you "feel ready / confident" to act. Ibarra says it's backwards: act first, then grow new self-knowledge from acting (act like a leader, then think like one), not the reverse.
Female Leader's Note
The authenticity paradox has a special twist for women: Tomas Chamorro-Premuzic notes that organizations often mistake "displayed confidence" for "competence," and that display is more culturally encouraged in men. Women are asked to "be their authentic selves," yet penalized for displaying a forceful style (double bind). The pragmatic fix isn't either/or — it's to tie the new behavior you're trying on to a purpose you genuinely believe in: "I practice speaking at all-hands not to perform confidence, but because my team's work deserves to be seen." Authentic purpose makes the action un-fake, and more resistant to "she's changed" gossip.
Key References
Herminia Ibarra,《The Authenticity Paradox》 (HBR, 2015) /《Act Like a Leader, Think Like a Leader》— "act first, learn after" and "playful experimentation with the self." Susan Cain,《Quiet》 — introverted leadership, no need to playact extroversion. Tomas Chamorro-Premuzic,《Why Do So Many Incompetent Men Become Leaders?》 — confidence ≠ competence, and its gender asymmetry.
Go Deeper · Push to the Edge
1. Where's the line between "switching style by situation" and being a two-faced "tell-them-what-they-want-to-hear" operator?
The difference is intent and consistency. Situational switching changes the means while values stay fixed: command in a crisis, coach in calm times, but what you consider "right" is constant, and the team can predict your line. Two-faced means values shift with the audience — no stable core behind it. Test: if your different styles were seen by the same person at once (boss and report in the same meeting), would you be embarrassed? Switching, no; two-faced, yes. What's consistent is "who you are"; what varies is only "which club you use right now."
2. Are the "default staple" styles the same in East Asian and Western organizations?
Not entirely. Goleman's data comes mainly from Western organizations; democratic/coaching styles may not transplant well into high-context, strongly hierarchical East Asian organizations — reports may not dare to tell the truth when you "democratically seek input," and may read it as "the boss has no view." This doesn't negate the framework, only changes the dose: in hierarchical cultures, authoritative + affiliative may be the steadier staples, and democratic needs psychological safety (see Day 21) laid first to work. Don't copy the style ratios of American management books — tune to your organization's real power distance.
3. Does pursuing "all six styles" actually cost you a distinct identity?
There's tension. Expanding bandwidth has a marginal cost, and a leader who's "a bit of everything" may leave the team unable to remember what you stand for. The pragmatic balance: keep one clear primary style as your identity (your signature club), then deliberately fill in 2–3 key backup styles to cover your blind spots — they need not be equal. Jobs had an extremely strong identity (authoritative + pacesetting), at the cost of near-zero affiliative and democratic — a high-risk, high-reward bet most people shouldn't imitate.
This Week's Exercise · Your Day 37 Action
This week you do one concrete thing — not reflect, not read:
Step 1 (diagnose): Against Card 1's six styles, review your key interactions of the past two weeks and tally which you used and how many times. You'll likely find 1–2 "default styles" dominate, and 2 you almost never use.
Step 2 (stretch): This week pick one low-risk occasion and deliberately use one of your "blind-spot styles." If you're always commanding/pacesetting, take a non-urgent matter and use coaching once (only ask, don't answer); if you're always affiliative/democratic, take something you're confident about and use authoritative once (give clear direction, no more soliciting input).
Afterward, jot two lines: (1) how awkward it felt (1–10); (2) how far the team's reaction was from what you expected. Awkward = normal; that's bandwidth growing.