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