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:

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