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