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:

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