Search
Close this search box.
Search
Close this search box.
Search
Close this search box.

The polarity in the life of a great Scrum Master and every manager- Useful tool for leaders

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

The complex reality presents many challenges and dilemmas that Scrum Masters and leaders at all levels try to solve using problem-solving techniques. Yet dilemmas are different from problems. While problems have a good answer or solution, dilemmas have more than a single good answer.
We are all familiar with dilemmas like Centralized vs. Decentralized, Cross-functional vs. Professional-focus, Quality vs. Speed, Individual improvement vs. Team improvement, Continuity vs. Transformation, Task-focus vs. relationship-focus, and many more.

In this article, I would like to present an easy and useful tool that managers at all levels can use to find a win-win answer. Scrum masters and managers that are required to lead in the complex VUCA (Volatility, Uncertainty, Complexity, and Ambiguity) world can use this tool to select the right stance to take.
To better understand this, let’s look at the following picture:
Some people see this picture of an old lady and some see a young lady, but both are there.
What do you see? Can you see both?

Not many people can see both at once.  In 1975 Barry Johnson developed the Polarity Map© as a way to understand and thrive in polarized situations.
Let’s discuss one common polarity dilemma SM’s and managers cope with and learn a tool that will help them improve the way they lead in this complex world.
“Make it Done” vs. “Empower others”  To map the polarity, we use two blocks each representing one approach (=pole), designated in the middle of the block, of the polarity.

The upper part of each block presents the respective benefits (+) which support achieving the goal of “Great Manager” (in this example). The bottom part of each block presents the negative consequences (-) of overusing that side of the polarity.
(see the picture below)

Let’s see how it works:

SM’s and managers understand that the “Make it Done” attitude is one of the reasons they were promoted to this position and therefore focus mainly on this side of the polarity as their style of leadership. By taking the “Make it Done” approach, they reduce discussions and sync meetings, have more control on the way things are done, and ensure they are done in the best way they believe it should be done.
the negative consequences (-) related to the “Empower Others” pole, convinces them to stick to the “Make it Done” approach to leadership.

However, by over-taking the “Make it Done” approach, managers get frustrated. They realize that they are firefighters, they need to be available at all times to solve ongoing issues, no one takes responsibility and they don’t have enough time to complete the work they need to do.
This is the disadvantage of overdoing “Make it Done”.
This frustration leads managers to look for different ways of leading people. Often, they overlook the “Empower others” side because they view it as the “Opposite” side of what they do today. However, if this is a dilemma and not a problem, they can consider both sides of the polarity and find a win-win way.

The “Empower others” side makes people “think” and find new innovative solutions, take more responsibility, and feel more commitment & engagement. This gives SM’s and managers free time to do their job, create vision and direction.

To move forward, with using the model managers can sake several “Action Items” that will help them gain the benefits of both sides while keeping in mind “Warning Indicators” that will prevent them from overusing one side. Following the Black arrow from the upper left side which represents understanding the benefits of “make it done” to the lower part with the negative consequences of overdoing it, shows managers to look for benefits of the upper right side of the polarity “Empower others” and avoid the negative consequences of overusing it.

Mapping the polarity alternatives and understanding the downside and the upside of each one of them will help leaders enjoy the benefits of both sides and reduce the consequences that are related to the over-usage of one side.

Subscribe for Email Updates:

Categories:

Tags:

Principles of Lean-Agile Leadership
Lean Agile
PI Planning
speed at scale
Keith Sawyer
ScrumMaster Tales
Operational Value Stream
AI
Covid19
Agile Outsourcing
Process Improvement
Hybrid Work
chatgpt
Scrum Guide
Continuous Integration
Nexus vs SAFe
Jira
Managing Projects
A Kanban System for Software Engineering
ALM Tools
Agile Techniques
Continuous Improvement
Value Streams
User stories
ROI
Certified SAFe
SAFe Release Planning
Agile Delivery
Agile Basics
Agile for Embedded Systems
Built-In Quality
Entrepreneurial Operating System®
Agile Release Management
Continuous Planning
Lean Agile Basics
Business Agility
Iterative Incremental Development
Rapid RTC
Managing Risk on Agile Projects
Test Driven Development
Nexus
An Appreciative Retrospective
Development Value Streams
speed @ scale
Continuous Delivery
Jira admin
SAFe DevOps
Software Development
Kaizen Workshop
ATDD vs. BDD
Implementing SAFe
Agile Mindset
Games and Exercises
Risk Management in Kanban
NIT
Self-organization
Quality Assurance
Risk Management on Agile Projects
Professional Scrum with Kanban
Kanban
What Is Kanban
Scrum Master
Agile Program
Slides
SAFe
Agile Israel Events
Advanced Roadmaps
Scrum and XP
AI Artificial Intelligence
TDD
Accelerate Value Delivery At Scale
Artificial Intelligence
Atlaassian
System Integration Environments
Agile Israel
Spotify
LPM
Lean Agile Leadership
lean agile change management
Agile Risk Management
Nexus and Kanban
Certification
Lean and Agile Techniques
DevOps
Program Increment
Scrum Master Role
Tools
Agility
Scrum Primer
Kanban Kickstart Example
Lean-Agile Software Development
RTE Role
Pomodoro Technique
GanttBan
LAB
QA
ARTs
Jira Cloud
Daily Scrum
Agile Marketing
Amdocs
Lean Budgeting
Sprint Iteration
Achieve Business Agility
Continuous Deployment
Portfolio for Jira
SPC
Reading List
Professional Scrum Master
Acceptance Test-Driven Development
Code
Planning
Change Management
WIP
Agile
Introduction to Test Driven Development
Agile Project
Release Train Engineer
ART Success
The Agile Coach
Effective Agile Retrospectives
EOS®
Agile Games
Large Scale Scrum
Kanban Basics
Lean-Agile Budgeting
System Team
Legacy Code
Product Ownership
Scrum With Kanban
Webinar
Presentation
PI Objectives
Story Slicing
Manage Budget Creation
BDD
predictability
Agile Contracts Best Practices
LeSS
Jira Plans
Frameworks
Perfection Game
Lean Startup
Agile Project Management
Applying Agile Methodology
Sprint Retrospectives
Coaching Agile Teams
Agile Assembly Architecture
POPM
Scrum.org
Agile Community
Scrum
Product Management
RTE
Team Flow
Kanban Game
Scrum Values
System Archetypes
Lean Agile Management
Agile Product Ownership
RSA
Tips
Sprint Planning
Agile India
Lean Software Development
SA
AgileSparks
Implementation of Lean and Agile
Agile Release Planning
The Kanban Method
Legacy Enterprise
Introduction to ATDD
Kaizen
Lean and Agile Principles and Practices
Nexus Integration Team
Scaled Agile Framework
Agile and DevOps Journey
Lean Risk Management
agileisrael
Lean Agile Organization
Agile in the Enterprise
Nexus and SAFe
Agile Games and Exercises
IT Operations
Enterprise DevOps
Engineering Practices
Agile Exercises
Professional Scrum Product Owner
Agile Product Development
Releases Using Lean
Systems Thinking
Kanban 101
Limiting Work in Progress
Risk-aware Product Development
Elastic Leadership
Agile Development
Agile Testing Practices
Software Development Estimation
Atlassian
Video
AgileSparks
Logo
Enable registration in settings - general

Contact Us

Request for additional information and prices

AgileSparks Newsletter

Subscribe to our newsletter, and stay updated on the latest Agile news and events

This website uses Cookies to provide a better experience
Shopping cart