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:

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