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:

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