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:

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