The Systemic Layer: What Organisations Quietly Teach

Introduction

The Systemic Layer: What Organisations Quietly Teach explores how everyday systems shape culture long before behaviour becomes visible. It examines how organisations quietly teach people what success, commitment and challenge really mean through the patterns they reward, preserve and normalise.

The Lessons Organisations Teach

Every organisation teaches people something about how to succeed. Very little of that learning comes from induction programmes, values statements or leadership presentations. It emerges through ordinary experience until certain behaviours begin to feel obvious, sensible and expected.

People notice who receives recognition, whose judgement carries influence and which behaviours attract opportunity. They also notice what carries a cost. Those observations are seldom dramatic. They accumulate through performance conversations, meetings, promotion decisions and everyday interactions until they become accepted without needing to be explained.

Written values still matter, but they compete with a more persuasive source of information: lived experience. An organisation speaks sincerely about collaboration, wellbeing or inclusion, but its credibility is shaped by what people see rewarded, protected and prioritised when difficult choices are made. It is within that comparison that the systemic layer comes into view.

What People Learn

Organisations develop their own definition of commitment. Very little of it is written down. People discover it by paying attention to what appears to matter once the working day begins. Before long, a question sits beneath countless everyday decisions.

What do I stand to lose if I behave differently?

The question is not usually asked aloud, and it doesn’t need to be. People notice what attracts attention, what passes without comment and what seems to require justification. Recognition communicates one set of priorities, while silence communicates another. Those observations become part of the judgement people bring to their own decisions, shaping what feels worthwhile, what feels risky and, eventually, what simply feels normal.

What Systems Reward

These expectations become particularly visible in what organisations reward, whether that recognition is deliberate or simply built into everyday working practices. In one organisation I worked with, the pattern was easy to see.

Long hours had become unremarkable. Emails sent late in the evening routinely generated replies that same night, creating an expectation that the working day extended well beyond contracted hours. Availability had become part of the organisation’s understanding of commitment.

Recognition settled around that expectation. Constant availability was never described as a performance measure, yet it consistently attracted attention. The behaviour that received recognition became the behaviour worth repeating.

Recognition Shapes Contribution

Performance conversations exposed the same pattern from another direction. I remember one colleague, who had spent the best part of a year mentoring new hires, reviewing other people’s work before it went out the door, and stepping in whenever the team was overloaded. None of it surfaced in their review. The conversation stayed on their individual metrics, and they left with an average score, because there was nowhere on the scorecard for what they’d actually been doing. I can still recall the exact sentence I heard used to explain it to them: “I can see a lot of how you contribute. I just can’t see enough of what you own.”

The following year, they started politely declining almost every request for help. They were protecting their own goals, which was entirely rational as the system had just taught them, clearly, what it was and wasn’t going to count. What nobody seemed to notice straight away was what their help had actually been doing for the team’s performance. It was like watching someone quietly remove the oil from a machine and only later wondering why everything had started running hotter.

The message carried well beyond that appraisal.

What Commitment Comes to Mean

Every boundary became an opportunity to explain the reasoning behind it, rather than simply insisting it be accepted. Over time, that created its own expectation. Setting a limit was rarely enough on its own; people learned that they also needed to make the limit understandable and acceptable to others.

The same pattern appeared when workloads became difficult to sustain. Requesting additional resource could be interpreted as a lack of resilience, even where the role had simply outgrown its original design. The signal was subtle, but people learned from it. Coping attracted less scrutiny than asking whether the workload itself was reasonable.

Recognition quietly answers a question that no performance framework ever asks directly.

What does commitment look like here?

What Systems Make Costly

Systems create trade-offs. Recognition encourages particular behaviours, while consequences discourage others. Together, they establish the boundaries within which people make decisions.
The cost is not always obvious. It may be measured in opportunities missed, invitations that stop arriving or the need to justify decisions that once required no explanation. Sometimes the cost is little more than attracting attention for the wrong reasons. That is enough.

Challenge illustrates the point well. Most organisations say they welcome it, particularly when it improves the quality of decision-making. Yet challenge carries a different weight when it delays progress, questions an established direction or exposes a flaw in work that others have already accepted. It can mean being left out of the next conversation, no longer being asked for an opinion or sensing that future challenge is less welcome than agreement. At that point, the discussion is no longer confined to the quality of the idea. It begins affecting the experience of the person raising it.

The same pattern appears in more ordinary decisions. Declining an evening meeting, for example, or disconnecting during annual leave. Maybe even explaining that a role has expanded beyond what one person can reasonably sustain. None of these actions should require courage, but in some environments, they do.

People adapt because adaptation makes sense. The behaviour changes first, then the explanation usually comes later.

When Adaptation Becomes the System

No single decision creates an organisational culture. Culture emerges as people make similar judgements until they no longer feel like judgements at all.

A leader responds to emails late into the evening because the work feels urgent, and a colleague does the same the following week, while another decides it would be unwise to disconnect completely during annual leave. Each decision is understandable in isolation. Taken together, they establish a new expectation without anyone consciously agreeing to it.

That is how systems evolve. They change through repetition as patterns of behaviour become patterns of expectation. Behaviour that once felt discretionary starts to feel expected. As a result, recognition establishes the baseline from which commitment is judged.

The consequence reaches beyond the behaviour itself. People stop asking whether the expectation still serves the organisation because it no longer appears to be an expectation. It has become part of the environment within which every decision is made.

The system is no longer reflecting behaviour. It is producing it.

What Systems Preserve

Systems do not defend themselves through deliberate intent. Their strength lies in familiarity. Processes introduced for good reasons outlive the circumstances that made them necessary because they still appear reasonable. Attention shifts towards operating the system effectively, while the purpose it was originally designed to serve gradually receives less scrutiny.

Structural drift develops through a succession of sensible decisions. Each adjustment responds to an immediate need. Viewed together, they can carry an organisation somewhere nobody consciously intended to go.

A weekly report is often a good example. It usually started as a genuine response to something specific; a project that needed closer tracking, or a deadline that had been missed. The problem it was built to solve was resolved months ago, but the report was never switched off. Nobody actively defends it anymore, and nobody has time to ask whether it still earns its place either, so it survives on inertia rather than value, quietly teaching people that producing the report is the work, when the report was only ever meant to protect the work.

Attention turns towards improving the existing design. When problems emerge, the instinct is often to add something rather than question what is already there. Additional meetings are scheduled, reporting requirements expand and new measures promise greater oversight, each introduced to solve a genuine problem. The system itself, however, remains untouched because it has not yet become the object of enquiry.

Over time, this changes the question being asked. Instead of returning to the purpose the system was meant to serve, attention stays focused on making the existing design work better.

Systems answer questions whether designed to or not. Few organisations stop to ask whether they are still asking the right one.

What Leaders Need to See

The question for leaders is whether the conditions surrounding commitment, collaboration and challenge allow those behaviours to be sustained.

A behaviour that depends upon exceptional courage is unlikely to become an organisational norm, no matter how strongly it is encouraged.

Leadership therefore extends beyond improving individual performance or strengthening relationships. It also requires examining the structures that shape both. Performance measures, governance arrangements, decision rights and resource allocation deserve the same scrutiny as behaviour because each contributes to the environment within which behaviour takes place.

Seeing behaviour as the visible expression of something deeper changes where leadership attention is directed. The conditions beneath it are often slower to become apparent, emerging through patterns across decisions, relationships and everyday organisational life. By the time behaviour has become visible enough to demand attention, those conditions have usually been shaping the organisation for much longer.

The task is not to prevent organisations from evolving. It is to recognise when the conditions surrounding work begin creating distance between behaviour and the organisation’s stated intentions.

Why Good Intentions Are Not Enough

Many organisations genuinely want to build healthier cultures. They invest in leadership development, revisit their values and encourage more open conversations. None of those efforts is misplaced. Each reflects a sincere commitment to improving the experience of work.

The difficulty arises when those aspirations encounter conditions that continue rewarding different conclusions about how work succeeds. For example, a leader encourages healthy boundaries, yet recognition still flows towards constant availability. Similarly, collaboration is celebrated in principle while performance systems continue rewarding individual visibility. Speaking up is encouraged yet challenge still carries an uneven cost depending upon who raises it and when.

Culture does not resolve those tensions through intention alone. People look for consistency between what an organisation says, what leaders do and what its systems reinforce. When those signals align, confidence grows because experience continually confirms what the organisation claims to value. When they diverge, experience becomes the more persuasive teacher. Behaviour continues responding to the conditions people encounter each day, regardless of the aspirations that surround them.

Culture change therefore follows a different timescale from organisational change. Values can be revised quickly, and leadership expectations can be communicated immediately. However, conditions change only when the ordinary experience of work begins reinforcing different conclusions about what is expected, what is rewarded and what is possible. Until then, people continue making decisions that are entirely consistent with the environment they know rather than the aspirations they have been asked to embrace.

Culture begins changing when those lessons begin changing.

Interpreting Behaviour

Interpreting behaviour requires a much deeper understanding of the environment from which it has emerged.

This is where diagnosis becomes more demanding. The question is no longer “What are people doing?” It becomes “What has made this response the sensible one?” That’s the shift that prevents behaviour from being treated as the problem itself. Instead, it becomes evidence that points towards the organisational environment in which it developed.

The difficulty is that organisations don’t often look there first. Their attention is drawn towards the immediate people and circumstances involved: the manager, the team, the relationship or the decision that appears to have triggered the problem in the first place. While those factors matter, they do not always explain why similar tensions continue to emerge elsewhere.

When familiar patterns surface across different teams, despite different leaders and personalities, the focus begins to shift. The question is no longer “Who created this?” It becomes “What keeps creating this?” That is where diagnosis moves beyond individual behaviour and towards the organisational environment shaping it.

Every culture leaves clues. The challenge is recognising them before they become accepted as inevitable.

Diagnosing Culture

Most organisations have become highly effective at measuring outcomes. They track engagement, retention, performance, absence and customer satisfaction with increasing sophistication. Those measures are important because they reveal how an organisation is functioning at a particular point in time. However, they reveal considerably less about why those outcomes have emerged.

When outcomes become the starting point, improvement efforts naturally focus on changing behaviour. Diagnosis begins somewhere else. It asks what people have learned from the organisation that has made those behaviours the sensible response.

That is the difference between describing culture and understanding it. The question is no longer how to increase engagement, improve collaboration or strengthen trust. It becomes:

What has this organisation been teaching people without ever intending to?

The answer is unlikely to be found in a values statement, an engagement survey or a leadership programme. It is more likely to be found in the ordinary decisions people no longer question because they have come to feel entirely normal.

That is where understanding starts. What it feels like to live inside it is a different question entirely.
The ideas explored throughout this series so far have been shaped by many years of working within organisations. But one experience, more than any other, fundamentally changed how I came to understand culture, leadership and organisational life.

The next piece steps inside that experience.