9 Proven Mental Models for Scrum Masters
Use these to survive and thrive in a non cooperative team environment.
Welcome to the 🔥 free edition 🔥 of Winning Strategy: a newsletter focused on enhancing product, process, team, and career performance. This newsletter shares insights gained from real-world experiences that I gathered working at Twitter, Amazon, and now as an Executive Product Coach at one of North America's largest banks. If you’d like to become a paid member, see the benefits here, and feel free to use this expense template to ask your manager.
I still remember the exact moment I almost quit being a Scrum Master.
Three months into our switch to Agile, I walked into another messy planning meeting. Half the team was late again. Our Product Owner wasn't ready with the work list. And a senior stakeholder had just dumped five "urgent" tasks on us that nobody knew about.
I looked around the room and all I could think was: "What am I even doing here?"
FRUSTRATING! I know…
In case you haven’t discovered it already: A perfect Scrum environment DOES NOT exist.
Most Scrum Masters work in organizations where Agile principles constantly compete with deeply rooted cultures, political dynamics, and resistance to change.
What separates the Scrum Masters who eventually give up from those who succeed isn't better teams or supportive organizations.
No!
It is the armour that successful Scrum Masters create around their mind.
What am I talking about? The Mental Models.
The right mental model can turn a seemingly impossible situation into a solvable problem.
Today, I will share the 9 that helped me navigate the ugliest environments. I’ve used these models to not only survive but thrive in places where teamwork was low and resistance was high.
They serve 2 purposes:
giving you clarity in chaos
providing actionable steps forward
Nothing more. Nothing less.
Let’s get started.
If you’re new, here’s what you missed in the last few weeks
Product Ops — What Scrum Masters and Product Owners need to know about this role?
Certified Scrum Master (CSM) - Brutally Honest Review Of the Most Popular Certification
What are Mental Models?
I'm pretty sure you have (or will) at some point in your life (teach or) taught a kid how to tie their shoe laces?
At first, it seems impossible to explain.
The child gets frustrated, the laces get tangled, and you wonder if Velcro might be the better option.
Then someone shows you the "bunny ears" method.
Suddenly, everything in the world changes. The child gets it. What was complex becomes simple. A confusing process transforms into two bunny ears dancing around each other.
That right there? That's a mental model in action.
Mental Model, or MeMod in short, is a simplified way of understanding the world.
We all use mental models every day:
When you check the weather before deciding what to wear, you're using a mental model
When you avoid a restaurant because it was crowded last month, you're using a mental model
As Scrum Masters, we need mental models to help us navigate the complex human nature that no framework or methodology fully prepares us for.
Let’s talk about the 1st one.
MeMod #1: The Serenity Principle
You know that burning feeling in your gut?
The one that shows up when senior management announces another "brilliant" initiative that goes against everything Agile stands for, and you just can’t do anything about it?
Yeah. That one.
The Serenity Principle is effective in moments when you feel those feelings.
The fact is, you can't fix everything.
And you shouldn't try.
The Serenity Principle saved my sanity more times than I can count.
Here’s how it works:
Accept what you can't change
Find the courage to change what you can
Learn to know the difference
THAT'S IT!
Let me give you an example.
Once, as a Scrum Master, the organization I was working with decided to standardize all teams' sprint lengths to two weeks.
No exceptions. No discussion.
Did I like it? NO.
Did I have the power to change it? Also NO.
So instead of burning myself out fighting an impossible battle, I focused on what I COULD control:
Making those two-week sprints the best they could be
Protecting my team's engineering practices
Building trust within my circle of influence
Doing this gave me energy for battles I could win.
Less frustration. Better sleep at night.
Being a great Scrum Master IS NOT about winning every battle.
It's about choosing the right battle.
Spend your time where it matters. Protect your reputation. Attempt to change only what you can.
Let the rest… go!
That’s the Serenity Principle.
Learn it. Live it.
MeMod #2: The 10-10-10 Rule
A decision-making mental model.
How it works:
Ask yourself:
How will I feel about this decision in 10 minutes?
How will I feel about this decision in 10 months?
How will I feel about this decision in 10 years?
How it helps:
This model helps you evaluate the emotional and long-term impact of your rushed decisions.
Example:
Let’s say you’re facing discrimination in your client organization.
If you’re considering escalating discrimination to your parent organization, ask:
Will this feel satisfying in 10 minutes (short-term relief)?
Will this improve my situation in 10 months (professional growth)?
Will this decision affect my career in 10 years (reputation and relationships)?
Let me share a story.
Once, a senior developer publicly criticized the team’s Scrum practices in front of stakeholders.
My immediate instinct? Fight back. Hard.
But I played the 10-10-10 game:
10 minutes? Oh, it would feel GREAT to put him in his place
10 months? Probably a strained relationship with a key team member
10 years? Possibly known as the Scrum Master who couldn't handle criticism professionally
What did I do?
I scheduled a private conversation instead, and we found common ground.
Sometimes, the most satisfying immediate response is the worst long-term strategy.
Read that again.
This rule will help you avoid mistakes.
It will also help you make decisions that your future self will thank you for.
MeMod #3: Anti-Fragility
This is a resilience-building mental model.
Most Scrum Masters aim to be resilient and bounce back from setbacks. But what if you could go beyond resilience and become anti-fragile?
What if you don’t just navigate the storms? You become stronger because of the storms.
This concept, coined by Nassim Nicholas Taleb, represents systems that benefit from disorder. As Scrum Masters, it means viewing every obstacle not as something to merely survive, but as fuel for your growth.
How it works:
See every challenge you face as raw material for your growth. Instead of breaking under pressure, you become stronger because of it.
How it helps:
This mindset lets you reframe tough situations as opportunities
You stop feeling like a victim
You start using every mess, every setback, to build adaptability and grit
Example:
Let's say you're dealing with a team that resists every Scrum event.
Instead of seeing it as a problem, view it as:
A chance to master stakeholder management
An opportunity to improve your facilitation skills
A workshop on influence and persuasion
This mental model doesn't mean you enjoy dysfunction or stop working to improve situations. It means you extract maximum value from difficult circumstances while working to change them.
Instead of asking "Why is this happening?" you ask "What can this teach me that I couldn't learn any other way?"
That seemingly impossible situation? It makes you stronger.
MeMod #4: Hanlon’s Razor
A perspective-shifting mental model.
Ever caught yourself thinking something like: "They're deliberately sabotaging the Sprint!" when faced with uncooperative stakeholders or team members who consistently derail your Scrum practices?
Enter Hanlon's Razor.
What it says:
“Never attribute to malice that which can be adequately explained by ignorance or incompetence.”
In plain English: Most people ARE NOT out to get you. They’re just busy, distracted, or don’t know better.
How it helps:
This model saves you from unnecessary drama.
You stop taking things personally
You stop seeing enemies where there are only misunderstandings
It frees up emotional energy and helps you solve the real problems.
Example:
Let’s say you are a contract-based Scrum Master. Your client’s internal team always seems uncooperative.
Meetings get cancelled. Emails go unanswered.
It’s tempting to think: “They want us out.”
When this happens, apply Hanlon’s Razor and think:
Maybe they’re overworked
Maybe they’re disorganized
Perhaps they don’t realize the impact of their actions
Here’s my story:
Once, a Product Owner repeatedly changed sprint priorities mid-sprint.
Without Hanlon’s Razor, my thoughts were:
"She's trying to prove Agile doesn't work."
"She's out to get me."
With Hanlon’s Razor, my thoughts were:
Is she trained in Agile?
Does she understand sprint commitments?
Is she under pressure from above?
What did I discover?
She was new to the role. No one had explained sprint boundaries to her. Her boss was demanding daily changes.
(Your discovery may be different.)
And the solution?
A coffee chat. Some basic Agile training. Help escalate to her manager.
Lesson? Most people ARE NOT out to get you. They're just trying to get through THEIR day.
Don’t use Hanlon’s Razor to give every other person the benefit of the doubt.
No!
Use it to focus on solutions, not grudges.
MeMod #5: Cargo Cult Thinking
A mental model that saves you from mindlessly following rituals.
During World War II, indigenous islanders in the Pacific observed military forces building airstrips and control towers.
After the war ended, some tribes built wooden replicas of airplanes and control towers, believing that recreating these structures would summon cargo-bearing aircraft.
You might be thinking, "What does this have to do with being a Scrum Master?"
Everything.
Cargo Cult Thinking happens when we replicate practices without understanding their underlying purpose. You see it in:
the daily stand-up, where nobody stands up
the retrospective, where nothing changes
the Sprint Planning, where work is pre-assigned
As a Scrum Master, it's tempting to become the "process police" enforcing Scrum by the book regardless of context. After all, the “guide” says so.
But blindly implementing any framework without understanding why each element exists… well, that’s a recipe for failure.
For example:
Let’s say your team consistently struggles with two-week Sprints.
They often carry user stories over. With a Cargo Cult approach, you’d double down on Sprint discipline: "The Scrum Guide says to stick with a cadence."
A more effective approach is to step back and ask:
"What outcome are we trying to achieve with time-boxed Sprints?"
If the answer is predictable delivery and regular feedback, perhaps you need to adjust the Sprint length, improve story splitting, or consider Kanban, which better suits your team's context.
You don’t abandon Agile values. You thoughtfully apply them to your unique situation.
MeMod #6: The Circle of Control
A mental model that helps you focus your energy where it matters.
Few things are more frustrating than feeling responsible for outcomes you can't control. As Scrum Masters, you often find yourself in this position, i.e. accountable for team performance yet lacking formal authority to make necessary changes.
This is where the Circle of Control mental model guides you.
How it works:
When you find yourself in a situation like this, break it into three buckets:
things that you can control
things that you can influence
things that are completely outside your control
Then?
Zero in on the first two. Let go of the 3rd.
Example:
Recently, Rahul asked this question in the community chat:
You can access the chat conversation here.
If you can’t change how internal teams treat you? Don’t obsess over it.
Focus on:
How can you respond to the situation
Network with supportive team members
Escalate issues professionally, not emotionally
I once worked with a client whose leadership would ignore every suggestion I made.
I stopped trying to “fix” them, even though that was part of the job.
Instead, I built trust with the people who did listen because that’s what I could do then. Eventually, small wins got noticed, and the leaders finally paid attention.
The Circle of Control mental model directs your focus and effort where it counts.
Control what you can. Influence what you can reach.
And…let go of the rest.
MeMod #7: The Law of Diminishing Returns
A mental model that saves you from the trap of endless optimization.
Scrum Masters are natural problem-solvers.
When they see an issue, they instinctively attack it head-on, applying more and more effort until it is resolved. This determination is admirable… until… it becomes counterproductive.
How it works:
Understand this simple truth: After a certain point, putting in more effort doesn’t equal better results. In fact, each extra hour or tweak gives you less and less payoff.
Example:
Let’s say your team’s daily standups keep running longer than 15 minutes.
You’ve already introduced timeboxing and a speaking order, and you've even coached team members on being concise.
Yet, the standups still drag on.
The Law of Diminishing Returns mental model helps us recognize that further effort to tweak the standup process may not yield significant improvement.
Instead, focus on building trust within the team so they naturally self-organize during standups. For now, accept that some inefficiency is okay while the team matures.
This mental model is your permission to quit…strategically.
Don’t confuse persistence with productivity. Know when enough is enough.
Then, move on to what matters more.
MeMod #8: Entropy
This mental model teaches us that without continuous energy input, things fall apart. This fundamental law of physics applies to your Scrum team as it does to the universe.
As Scrum Masters, you expect that once good practices are established, they will continue running smoothly.
But entropy teaches us that disorder is the default state.
Without ongoing attention, even the most well-designed processes will deteriorate.
Consider your team's information radiators. Without regular updates, they become outdated
Your working agreements? Without reinforcement, they fade into forgotten documents
Your retrospective action items? Without follow-through, they become empty promises
That’s how nature works! Excellence requires continuous energy input.
Great Scrum Masters recognize that maintaining high performance is an active, ongoing process.
Years ago, when I embraced entropy as a mental model, I stopped being surprised when things slipped. I built regular "entropy-fighting" activities into my routine, like:
Periodic refreshers on core principles
Regular validation of working agreements
Continuous refinement of processes (yes, even Scrum)
Rather than viewing this maintenance as a sign of failure, I recognized it as an essential part of the job, like changing the oil in a car.
Entropy isn't your enemy.
It's simply a reality that effective Scrum Masters acknowledge and plan for.
MeMod #9: Multiply by Zero
No matter how large a number, multiplying it by zero always yields zero.
This principle applies with surprising accuracy to Scrum teams, and it's a lesson I learned the hard way.
Several years ago, I witnessed a team that excelled in nearly every aspect of Agile development. Their technical practices were outstanding. Their velocity was stable. Their code quality was excellent. Sprint after sprint, they delivered completed features exactly as planned.
Yet the product failed.
Why?
Because one critical factor was missing: They built features nobody wanted. All that brilliant effort multiplied by zero stakeholder validation equalled zero market value.
That’s "Multiply by Zero" mental model.
When a critical success factor is completely absent (zero), the exceptional quality of other elements becomes irrelevant, and the end result always…is zero.
Recognize your team's potential "zeros". Some common examples are:
Zero stakeholder engagement = zero market fit
Zero testing discipline = zero product reliability
Zero team psychological safety = zero innovation
Zero product owner availability = zero direction clarity
Zero technical excellence = zero sustainable delivery
Your role as a Scrum Master is to identify these potential zeros before they nullify your team's hard work.
This often means having uncomfortable conversations with your team.
For example, if your Product Owner rarely engages with stakeholders, you must ask your Product Owner:
"Are we confident we're building the right thing? What's our risk of multiplying all this development effort by zero user value?"
A chain is only as strong as its weakest link.
Don’t let your zero go unnoticed.
Got an urgent question?
Get a quick answer by joining the subscriber chat below.
Only available to Paid Subscribers.
The Journey Forward
You now have my 9 mental models.
These are real tools (not theory) to help you navigate the mess, uncertainty, and opportunities of your unique Scrum Master journey.
Remember: mastery has nothing to do with perfection, memorizing rules, or checking boxes. It’s about clarity. It’s about focus. It is about courage to do what matters, especially when things get tough.
You’ll have moments of doubt.
It is not just the Scrum Master role; life, in general, is tricky. It happens with all kinds of roles.
But with these models, you’ll catch yourself faster, reorient more easily, and avoid the traps that keep most people stuck.
So what’s next?
Pick one model and try it this week
Apply it deliberately
Document insights
Develop your variations (customize)
Create context-specific applications
Build your example library
Mentor others
The most powerful tool in leadership IS NOT the authority you possess, it is the mental models you use to understand and shape the world around you so you can INFLUENCE it the way you need.
Stay curious. Stay humble.
And keep moving.
Show your support
Every post on Winning Strategy takes 3 days of research and 1 full day of writing. You can show your support with small gestures.
Liked this post? Make sure to 💙 click the like button.
Feedback or addition? Make sure to 💬 comment.
Know someone who would find this helpful? Make sure to recommend it.
I strongly recommend that you download and use the Substack app. This will allow you to access our community chat, where you can get your questions answered and your doubts cleared promptly.
Research
https://www.frontiersin.org/journals/psychology/articles/10.3389/fpsyg.2022.873289/full
https://web.wpi.edu/Images/CMS/SSPS/06.pdf
https://github.com/AdrienLemaire/awesome-mental-models
https://www.pnas.org/doi/10.1073/pnas.1012933107
https://zapier.com/blog/mental-models/
https://www.reddit.com/r/coolguides/comments/1bgdmp9/a_cool_guide_cheatsheet_to_mental_models_with/
https://seagrant.oregonstate.edu/sites/seagrant.oregonstate.edu/files/h11002.pdf
https://thesystemsthinker.com/mental-models-and-systems-thinking-going-deeper-into-systemic-issues/
https://en.wikipedia.org/wiki/Mental_model
https://www.pnas.org/doi/10.1073/pnas.1012933107
https://www.goodreads.com/shelf/show/mental-models
https://fs.blog/mental-models/
Further Reading
Connect With Me
Winning Strategy provides insights from my experiences at Twitter, Amazon, and my current role as an Executive Product Coach at one of North America's largest banks.
Thanks a lot, Vibhor. This post is spot on and exactly what I needed based on the question I asked you last week. Really appreciate it !