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:

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