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:

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