Leadership styles and influence without authority

In one team’s delegation log, the lead took 9 of 14 decisions more tightly than needed, losing 3.0 of 10.5 decision-days to escalation and waiting. No single style fits every person: a newcomer needs direction, a learner coaching, a skilled but hesitant colleague support, and an expert a decision of their own.

Leadership styles are half of a project lead’s work. The other half is help from people who do not report to you, such as a security team or a busy sponsor. Influence without authorityinfluence without authority: The ability to move people who do not report to you by understanding their needs, building relationships, bringing data, and offering options rather than commands. wins that cooperation through the other team’s priorities, evidence and choices instead of pressure.

Readiness for the task decides the leadership style

Start with the log: the lead decided a banner colour, test folder names and the retrospective format, all decisions the team could own.

"""
Delegation log: 14 decisions from two weeks, each with the style the lead used, the
style the situation needed and the days the decision took, showing what deciding
too high up costs.

The four styles, from most to least directive: 1 direct (the lead decides and tells),
2 coach (the lead decides after discussing), 3 support (the person decides with the
lead's help), 4 delegate (the person decides within agreed limits).

Model (an assumption, stated so it can be changed): every step a decision sits above
the style it needed adds half a day of escalation and waiting, and no decision takes
less than a quarter of a day.
"""

NAMES = {1: "Direct", 2: "Coach", 3: "Support", 4: "Delegate"}

# Each decision: (day, description, style_used, days_to_decide, style_needed)
decisions = [
    (1, "Assign who debugs payment timeout", 1, 0.5, 1),
    (1, "Choose colour for error banner", 3, 0.25, 4),
    (2, "Rename folders in the shared test suite", 1, 0.5, 4),
    (2, "Pick date for code review workshop", 2, 1.0, 4),
    (3, "Accept a new dependency on vendor SDK", 2, 2.0, 2),
    (3, "Decide sprint goal wording", 1, 0.5, 3),
    (4, "Choose test framework version", 2, 1.0, 4),
    (5, "Accept a 2-day scope addition", 2, 1.5, 2),
    (5, "Reassign tasks after sickness absence", 1, 0.25, 3),
    (6, "Escalate blocked integration to vendor", 1, 0.5, 1),
    (8, "Set meeting times for new joiner onboarding", 1, 0.5, 4),
    (9, "Select interview panel for contractor", 2, 1.0, 3),
    (10, "Decide response to late API change", 1, 0.5, 1),
    (10, "Choose retrospective format", 2, 0.5, 4),
]

print("Delegation log: 14 decisions over two weeks")
print("=" * 70)
print(f"{'Day':<4} {'Decision':<44} {'Used':<9} {'Needed':<9} {'Days':>4}")
print("-" * 70)
for day, desc, used, days, needed in decisions:
    print(f"{day:<4} {desc:<44} {NAMES[used]:<9} {NAMES[needed]:<9} {days:>4.2f}")

total_days = sum(d[3] for d in decisions)

# A decision taken more directively than needed (used < needed) waits half a day per extra step.
right_days = []
for day, desc, used, days, needed in decisions:
    steps_too_high = needed - used
    right_days.append(max(0.25, days - 0.5 * steps_too_high) if steps_too_high > 0 else days)
total_right = sum(right_days)

too_directive = [d for d in decisions if d[2] < d[4]]
too_hands_off = [d for d in decisions if d[2] > d[4]]

print(f"\nDecision-days with the styles used:   {total_days:5.2f}")
print(f"Decision-days with the styles needed: {total_right:5.2f}")
print(f"Days lost to escalation and waiting:  {total_days - total_right:5.2f}")
print(f"\nDecisions taken too directively: {len(too_directive)} of {len(decisions)}")
print(f"Decisions taken too hands-off:   {len(too_hands_off)} of {len(decisions)}")

print("\n--- The decisions the team could have taken ---")
for day, desc, used, days, needed in too_directive:
    print(f"Day {day}: {desc} ({NAMES[used]}, needed {NAMES[needed]})")

Delegation log: 14 decisions over two weeks
======================================================================
Day  Decision                                     Used      Needed    Days
----------------------------------------------------------------------
1    Assign who debugs payment timeout            Direct    Direct    0.50
1    Choose colour for error banner               Support   Delegate  0.25
2    Rename folders in the shared test suite      Direct    Delegate  0.50
2    Pick date for code review workshop           Coach     Delegate  1.00
3    Accept a new dependency on vendor SDK        Coach     Coach     2.00
3    Decide sprint goal wording                   Direct    Support   0.50
4    Choose test framework version                Coach     Delegate  1.00
5    Accept a 2-day scope addition                Coach     Coach     1.50
5    Reassign tasks after sickness absence        Direct    Support   0.25
6    Escalate blocked integration to vendor       Direct    Direct    0.50
8    Set meeting times for new joiner onboarding  Direct    Delegate  0.50
9    Select interview panel for contractor        Coach     Support   1.00
10   Decide response to late API change           Direct    Direct    0.50
10   Choose retrospective format                  Coach     Delegate  0.50

Decision-days with the styles used:   10.50
Decision-days with the styles needed:  7.50
Days lost to escalation and waiting:   3.00

Decisions taken too directively: 9 of 14
Decisions taken too hands-off:   0 of 14

--- The decisions the team could have taken ---
Day 1: Choose colour for error banner (Support, needed Delegate)
Day 2: Rename folders in the shared test suite (Direct, needed Delegate)
Day 2: Pick date for code review workshop (Coach, needed Delegate)
Day 3: Decide sprint goal wording (Direct, needed Support)
Day 4: Choose test framework version (Coach, needed Delegate)
Day 5: Reassign tasks after sickness absence (Direct, needed Support)
Day 8: Set meeting times for new joiner onboarding (Direct, needed Delegate)
Day 9: Select interview panel for contractor (Coach, needed Support)
Day 10: Choose retrospective format (Coach, needed Delegate)

The docstring states the model: each step a decision sits above the style it needed adds half a day of waiting. The nine over-tight decisions cost 3.0 days, and none was handed over too early.

Read readiness before choosing how to lead. Readiness is how able and how willing a person is to do this task, so an expert at deployments can be a beginner at estimates. The four leadership styles differ in how much direction and encouragement the lead gives:

• Direct: the lead decides and gives clear steps. It fits someone new to the task, or a crisis with no time to discuss.
• Coach: the lead still decides but explains why and asks for ideas. It fits someone still learning the task.
• Support: the person decides while the lead encourages and clears obstacles. It fits someone skilled but unsure.
• Delegate: the person decides within agreed limits. It fits someone skilled, confident and committed.

These labels follow situational leadershipsituational leadership: A model that matches leadership approach (direct, coach, support, delegate) to the follower's readiness for the task: low readiness needs direction, high readiness allows delegation.: the lead’s behaviour follows the follower’s readiness, not the lead’s habit. PMI’s PMP Examination Content Outline lists “Determine an appropriate leadership style” under People task 3, Lead the project team.

Pick one person and one task, answer the table’s question, and see which styles it rules out:

Servant leadership serves growth, not every request

A team asks its lead to cancel the retrospective for three Sprints because it feels slow. Granting that looks like service, yet it removes the meeting where the team improves how it works; a servant leader keeps the purpose and changes the format.

Servant leadershipservant leadership: A leadership philosophy that puts the growth and well-being of those served first; the servant-leader serves, then leads, and tests success by whether those served grow as persons. puts the growth of the people served first. Robert K. Greenleaf coined the phrase in The Servant as Leader, an essay first published in 1970, writing that “The servant-leader is servant first”. His test begins “Do those served grow as persons?” and asks whether they become freer and more able to serve others in turn.

The 2020 Scrum Guide calls the people accountable for a Scrum Team’s effectiveness “true leaders who serve the Scrum Team and the larger organization.” Serving is not obeying: the PMP outline’s task 3 lists “Empower the team” and “Represent the voice of the team” beside “Establish expectations at the team level”. So a servant leader carries the team’s bad news upward and clears obstacles, yet holds the team to what it agreed.

Influence without authority, worked on a security review Pro: opens with a Pro, Premium or Ultimate pass

Delegation with written limits, and what a mismatch costs Pro: opens with a Pro, Premium or Ultimate pass

Practise

These questions cover matching styles to readiness and servant leadership; each wrong choice explains itself.

Interview questions

Warm-up (fresher to 2–5 years): how do you choose a leadership style for a new team member?

Judge their readiness for this task: how able and how willing they are. Someone new to the task starts with the direct style: clear steps, a worked example and an early look at the first result. After a few good attempts, coach and explain the reasons; once the skill is there, support their decisions, and delegate when they are skilled and confident. Judge readiness again whenever the task changes.

Three harder questions follow: a slow security review, a delegated tool choice and a team that calls you soft.

Key takeaways

• No single leadership style fits: read readiness for the task, then direct, coach, support or delegate; direct in a crisis.
• Leading more tightly than readiness needs costs time: nine over-tight decisions lost 3.0 of 10.5 decision-days.
• Servant leadership serves growth rather than every request, and the lead stays accountable for what the team agreed.
• Influence without authority wins help from teams you do not manage through their priorities, evidence and choices.