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:

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