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:

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