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:

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