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:

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