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:

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