Situational Leadership Styles

There are four main leadership styles: delegating, supporting, directing, and coaching. The styles are based on the scales of supportive behavior and directive behavior.

Directing style

“I am deciding based on MY own proposals”. Maintaining control over decisions. Can be good for new teams or unusual situations. The team is doing what is explicitly asked. Without team support, the leader decides based on his knowledge or with team support, where the team provides input for the decision.

Coaching style

“I am deciding based on OUR proposals”. The manager is making decisions considering the team’s opinions. Use in the development of the team, when the team has the know-how but lacks the experience to decide. It can be time-consuming and the leader may seem weak. A leader can share issues with the team individually or collectively.

Supporting style

“We are deciding based on OUR proposals”. Connecting the team to make decisions, support the involvement and responsibility. Adequate for teams of skilled professionals, when the spectrum of skills is needed. The disadvantage can be a weakened sense of leadership. This style can be either bossy or team. Bossy means the leader coordinates the discussion or the team is allowed to lead the discussion.

Delegating style

“YOU decide based on YOUR proposals”. Orientation on the individual responsibility of team members. It is supporting motivation and involvement. Team members are experts, the technical know-how of some individuals can exceed the managers’. The authority could be lost. The leader sets parameters and goals and is informed about progress or sets the parameters and fully supports the team’s solution.

Leadership model picture

Similar posters

RACI Matrix
RACI Matrix RACI Matrix/Chart is the type of responsibility assignment matrix for effective work organization, communicating the responsibilities.
CEDAR Feedback
CEDAR Feedback CEDAR is a structured feedback model providing coaching opportunities via repeated revisiting and readjusting of the feedback and the goals.
STATIK Kanban The Systems Thinking Approach To Introducing Kanban (STATIK) is a repeatable way to start with Kanban resulting in continuous improvement.
Data Model Canvas
Data Model Canvas The Data Product Canvas is a framework for developing data products based organized into 10 blocks within 3 domain areas.
Kanban Practices
Kanban Practices Visualize Visualizing your work provides transparency, identifying the bottlenecks. Create cards for the items you work on. Think of the workflow – statuses that work items go through to make implicit policies explicit, which enable learning how the work works. Limit Work In Process Stop starting, start finishing. Limit the number of items being worked...
Theory Of Constraints
Theory Of Constraints The Theory of constraints says the throughput of any system is limited by at least one constraint slowing it down.
Classes of Service (CoS)
Classes of Service (CoS) Classes of service (CoS) provide a transparent way of categorizing the incoming work items and ensuring they are properly prioritized and governed to lead to meeting customer expectations. They enable managing risk, priorities, and cost of delay. Expedite High-priority items that should be worked on as soon as possible. Expedite class work items have critical...
Seven wastes of software development
Seven wastes of software development Similar to what TPS identified as seven categories of waste in manufacturing, also software development has its own wastes.
Core Kanban Practices
Core Kanban Practices One of the few rules or practices which are the foundation of Kanban are its 3 core practices: Visualize, Limit WIP, and Manage flow.
The prime directive of agile software development
The prime directive of agile software development Acronymat poster: The prime directive of agile software development - Never be blocked, the system must work all the time.