Where Anti-Leaders Come From
Anti-leaders are produced, not born.
In a previous article, I described four types of anti-leaders:
- The "my way" leader
- The control freak
- The blame manager
- The "it's about me" leader
These patterns show up consistently and create measurable damage.
What that analysis did not address is cause.
These behaviors are not random. They are the direct result of how organizations define, reward, and assign leadership roles.
Most organizations promote based on:
- Individual output
- Reliability
- Tenure
They do not promote based on:
- Ability to develop others
- Ability to scale decision-making
- Ability to operate through systems instead of direct control
This creates a structural mismatch.
The individual is rewarded for one set of capabilities and then placed into a role that requires a different set entirely.
This is not primarily a leadership failure. It is a selection failure.
The Core Misalignment
A promotion into leadership is not a continuation of the same work. It is a different role.
- Individual contributors create value through execution
- Leaders create value through the performance of others
When this shift is not explicitly defined and validated, people default to what made them successful before.
That is where anti-leader behavior begins.
High standards become rigidity. Attention to detail becomes control. Ownership becomes centralization.
The behavior does not change. The context does.
Leadership Readiness Indicators
If leadership is a different role, readiness must be evaluated differently.
These are observable behaviors. If they are not present before promotion, the individual is not ready, regardless of performance.
1. Thinks in Systems, Not Tasks
They understand how work flows across people and steps. They identify where processes break down and how one decision impacts another.
They locate problems at the system level, not just at the point of failure.
2. Improves Others' Work Without Taking Control
They raise the quality of work around them without becoming the person doing the work.
Their involvement increases capability, not dependency.
3. Makes and Adjusts Decisions Under Uncertainty
They make decisions without complete information and adjust when those decisions prove wrong.
They can stop work, redirect effort, or reverse course, including their own prior decisions.
4. Communicates for Clarity, Not Activity
They reduce confusion.
After they communicate, people know what to do, what matters, and where the boundaries are. Fewer clarifications are needed, not more.
5. Reduces Dependency on Themselves
Work continues without them.
Decisions are made without escalation. Progress does not pause when they are unavailable.
They are not the system. They enable the system.
These are not personality traits. They are leverage behaviors.
Most promotion decisions ignore them.
These indicators predict whether someone should be promoted. The signals that follow show whether that decision was correct.
Scenario: When Strength Becomes Constraint
Employee A was a strong graphical designer and an effective leader within a small SCRUM team.
Her strengths were clear:
- She understood the work in detail
- She identified weaknesses quickly
- She helped define design standards
- She contributed directly while guiding a small group
She operated in a high-context, low-scale environment.
She was promoted to Creative Director to oversee design across multiple teams, covering 4 to 6 projects and roughly 30 people.
This role required a different mode of operation:
- From doing to enabling
- From team-level to system-level
- From direct control to distributed control
The role was clearly redefined. Expectations were set. She was coached and supported through the transition.
The shift still did not happen.
Failure Progression
Employee A continued to operate using the model that made her successful before.
She:
- Reviewed the visual aspects of every project
- Required approval on most deliverables
- Maintained direct control over design decisions
The results followed a predictable sequence.
Stage 1: Increased Control
Teams deferred decisions upward. Review cycles expanded.
Stage 2: Throughput Reduction
Work slowed to match her review capacity. Parallel work became sequential.
Stage 3: Capability Suppression
Designers stopped making independent decisions. Team leads lost authority.
Stage 4: System Bottleneck
The output of 30 people was constrained by one person's availability.
Nothing about her intent changed.
Her previous strengths became liabilities at scale.
She did not fail due to lack of support or clarity. She failed to make the role transition.
The Alternative
Employee B replaced her in the same role.
He inherited the same teams, workload, and constraints.
He started with diagnosis:
- Where is design slowing you down?
- Where are standards difficult to apply?
- Where is work taking longer than it should?
He focused on friction in the system, not errors in output.
His operating model was consistent:
- Teams identified problems
- He coached rather than corrected
- He spot-checked instead of reviewing everything
- He investigated system misalignment when productivity dropped
He did less direct work and produced more total output.
That is the definition of leadership leverage.
The constraint was removed from the leader and placed where it belongs: in the system.
Evaluating the Difference
The difference between Employee A and Employee B is clear when mapped against leadership readiness indicators.
| Indicator | Employee A | Employee B |
|---|---|---|
| Systems Thinking | Limited to team level | Operated at system level |
| Improves Others | Took control of work | Built capability in others |
| Decision Quality | Did not adjust approach | Adapted based on constraints |
| Communication | Created dependency | Created clarity |
| Dependency | Became bottleneck | Enabled independence |
Employee A was promoted based on performance.
Employee B operated based on leverage.
This Pattern Is Not Unique
This scenario is not specific to design, SCRUM, or this team.
The same pattern appears anywhere leadership is treated as a continuation of individual performance:
- Strong contributors extend control instead of distributing it
- Work scales to the leader's capacity instead of the team's capability
- Output stabilizes or declines as responsibility increases
The details change by domain. The failure pattern does not.
Leadership Effectiveness Signals
Leadership effectiveness shows up in outcomes.
There are three signals.
1. Team Trust
People feel heard and treated fairly. Information flows.
If trust is low, decision quality is compromised.
2. Performance Movement
Output improves or defects decrease.
If performance does not improve, the leader is not effective. The role is not being fulfilled.
3. System Independence
The team functions without constant oversight.
If the leader is absent and work stalls, the system is broken.
All three must be present.
A leader can be liked and ineffective. A leader can produce results and burn out a team. A leader can maintain control and block scale.
Effectiveness requires trust, performance, and independence together.
Closing
Anti-leaders are not rare. They are predictable.
They are created when organizations promote based on performance and fail to redefine how value is created in the role.
Once in place, they do not self-correct. The system reinforces the behavior that created them.
The question is not whether this happens. It will.
The question is whether you correct the system, or continue to produce the same result.