Leadership Styles: Pick by Situation, Not by Personality
The worst leadership advice I ever absorbed was "find your style." It framed leadership as self-expression, as if the team existed to receive my authentic preferences. Years of running teams through incidents, growth phases, and reorgs taught me the opposite framing: styles are tools, situations pick the tool, and the leaders who struggle are usually not the ones with a bad style but the ones with only one.
The toolbox, honestly described
Directive leadership decides and instructs. It is unfashionable and sometimes exactly right: in a live incident with money burning, someone must call the shot now, a point I made in the conflict post. It is also right with a brand-new team that has no norms yet. Its expiry date is short: directive leadership past the emergency teaches capable people to stop thinking, and then you own every decision forever.
Democratic leadership decides with the group. It buys commitment, because people execute what they helped choose, and it surfaces information the leader does not have. Its cost is time, and its failure mode is fake democracy: asking for input on a decision already made. Teams detect that instantly, and the currency it burns, trust in being consulted, does not come back at par.
Coaching develops the person while the work happens: less "here's the answer," more "walk me through your thinking." This is the style that built every strong senior I have ever grown, and it is the first style sacrificed under deadline pressure, which is precisely backwards. The weeks I spent coaching instead of answering were the weeks that made the next crunch survivable, because more people could carry it.
Servant leadership treats the leader as the remover of obstacles: unblock, protect focus, get the team what it needs, absorb organizational noise. On experienced teams this outperforms everything else, and it maps almost one-to-one onto what good agile leadership looks like day to day. Its failure mode is under-direction, servant leading a team that actually needed a decision made.
Laissez-faire, real delegation with real distance, works exactly when the team is senior, aligned, and the domain is theirs. As a default it is neglect with better branding.
Mismatches have a signature
The diagnostic skill is recognizing style-situation mismatch from the team's behavior, because the team always signals it. Directive style on a mature team produces silent compliance and vanishing initiative. Democratic style in a crisis produces meetings while the fire spreads. Coaching a person who is drowning produces resentment; they needed a lifeline, not a question. Delegating to a forming team produces chaos wearing the word "empowerment." When a team behaves strangely, my first check is no longer the team. It is whether my style matches their stage, which is the same lesson as Tuckman's stages: the leader's job changes as the team changes.
Switching styles without whiplash
One caution from doing this wrong: style-switching confuses people unless the switch is narrated. A team used to consultation experiences a sudden directive call as an alarm bell. The fix costs one sentence: "this one's an emergency call, I'll own it, we'll debrief after." Or the reverse: "no crisis here, I want us deciding this together." Naming the mode keeps the switch legible, and the team learns the pattern behind it, which is itself a form of stability.
The uncomfortable summary
Leadership style is a decision you re-make per situation, not an identity you discover once. The self-expression framing flatters the leader; the situational framing serves the team. And the single question that most improves style choice costs nothing: what does this team, at this stage, in this situation, actually need from me right now? The answer is frequently not the style I would have preferred to give. That gap, between preferred and needed, is more or less the job.
Nguyễn Hải Nam
Project Management Lead. 16+ years from code to delivery. PMP®. Writing here about project management and engineering.