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:

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