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:

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