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