What you don’t see sends everything

You can introduce a new way of working, hold people accountable for their behavior and adjust processes. And yet nothing essential changes. Recognizable? In agile organizations, the reflex is quick when something is not running: people’s behavior is the problem. Teams don’t take ownership. Decision-making drags. Cooperation runs stiffly. Yet the real cause is rarely in what you see.

Do you want to know how your organization is really being driven, without realizing it? Then you want to look below the waterline. And this article helps you do exactly that. With three layers, three concrete tips, 1 bonus and a free online tool.

Looking below the waterline

The iceberg model helps me understand what is really going on in an organization. Above the water you see behavior, what people do, say and fail to do. That is layer 1, the visible tip of the whole. But below the waterline are three layers that really guide that behavior and make it logical. When these layers align, it creates behavior that feels logical to everyone. Even if that behavior gets in the way of agility, learning and collaboration.

Layer 2: Patterns
What situations repeat themselves over and over again? Think of yet another sprint review where no one of consequence shows up. The retrospective where good intentions are made, but three weeks later everything is back to normal. And no one says anything about it, because that’s just the way it goes here. Patterns show that behavior is not a coincidence. It is a predictable response to the context, and the system rewards its repetition.

Layer 3: Structures and Systems
Sometimes structure says more than a thousand words. The Product Owner who doesn’t actually have a mandate. The planning session that is ticked off at the highest echelon, not even involving the team. Because yes, there is also a steering committee that has a say. A structure that promises autonomy but builds in control drives behavior more strongly than any plea for agility. Roles, agreements, metrics and sprint cycles, they tell people every day what really matters here.

Layer 4: Beliefs and mindset
This is the deepest layer. The unspoken assumptions that define what is normal here. What achieves status? What can you do wrong and what would rather not? In organizations that claim to work agile but don’t touch this layer, the form changes, but not the mind. And then the real question is: how psychologically safe is it really here? Because without safety no honesty, and without honesty no real change.

From explaining to changing

The power of the iceberg is not in naming problems, but in expanding your scope of action. Once you look below the waterline with your team, the conversation shifts. It’s no longer about who’s doing it wrong, but about what makes the system make sense. That’s also exactly where culture change begins. Culture is not a vague concept. It is the set of patterns and beliefs that drives daily behavior, visible or not.

Agility requires steering, not pushing

Agile organizations are not distinguished by people trying harder. They stand out because their structures and beliefs support desired behavior rather than thwart it. Those who only pull behavior get frustrated. Those who dare to look at patterns, structures and mindset discover that small shifts can have a big effect, without major reorganization.

TIPS: Three things you can do tomorrow

Stop solving behavior and start understanding it
Choose one situation that frustrates you and describe only what you see. Then find the pattern that repeats and the structure that makes it possible. The behavior follows naturally from that whole.
Change one structural incentive
Look at what is rewarded: speed, certainty, control. Adjust one appointment, consultation form or measurement point and observe what changes. Structures speak louder than words.
Discuss beliefs without judgment
Ask not why someone is doing something, but what is seen as logical here. “What makes this a wise choice here?” opens the conversation and brings up the undercurrent.

Bonus, for those who want to change the system and not the people

Leadership in an agile context is less in addressing individuals and more in monitoring the preconditions. Make room for learning. Slow down where reflection is needed. Let tension exist without immediately smoothing it out. In this way you invite others to take responsibility, rather than demanding it of them.

Finally, do the free Culture Scan

Does all this play out in your organization as well? With Scrum Academy’s free culture scan you’ll uncover in one go which culture types are dominant, what that means for the behavior you see, and where the real levers lie. No big analysis, just a clear starting point for the conversation you’ve been wanting to have for a while.

Get in touch, we’d love to think with you.