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:

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