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.

Categories:

Tags:

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

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