Here is something that almost every senior leader knows intuitively - and almost no culture programme accounts for.

Your sales team and your technology team are not the same kind of organisation. They do not operate on the same timescales. They do not define success in the same way. They do not relate to hierarchy, feedback, risk, or ambiguity in the same way. And the behaviours that make someone exceptional in one function would make them actively counterproductive in the other.

And yet most organisations design one culture - one set of values, one behavioural framework, one culture activation - and apply it uniformly across both.

The result is a culture programme that optimises for neither, resonates with few, and produces the quietly baffling pattern that most culture leads have encountered at some point: strong engagement scores in some functions, flat or declining scores in others, and no clear explanation for why the same programme produced such different results across the same organisation.

The explanation is sub-cultures. And until organisations design for them explicitly, culture investment will continue to underdeliver.

The question is not whether your organisation has sub-cultures. It does. Every organisation of any scale does. The question is whether you designed them - or whether they designed themselves.

What sub-cultures are and why they are inevitable

Organisational culture research has long recognised that culture is not monolithic. Edgar Schein's foundational work on organisational culture and leadership - first published in 1985 and still the most rigorous theoretical framework in the field - explicitly identified sub-cultures as a structural feature of all complex organisations, not a deviation from a unified culture.

Schein identified three types of sub-culture that reliably emerge in organisations:

1. Operator sub-cultures - formed by the people doing the core work of the organisation, shaped by the specific demands, timescales, and social dynamics of their function.
2. Engineering sub-cultures - formed by people who design and build systems, characterised by a different relationship to uncertainty, process, and problem-solving than operator cultures.
3. Executive sub-cultures - formed by senior leadership, often more aligned with financial performance and strategic narrative than with the day-to-day operational realities of either of the above.

These sub-cultures are not pathological. They are the predictable consequence of different functions facing different work demands, developing different norms for how to operate effectively, and rewarding different behaviours for good functional reasons.

The problem is not that sub-cultures exist. The problem is that most culture programmes are designed to override them with a uniform set of values and behaviours - which the research consistently shows does not work.

The Science

Schein, E.H. (1985, 2010). Organizational Culture and Leadership. Jossey-Bass. Martin, J. (1992). Cultures in Organizations: Three Perspectives. Oxford University Press — established that organisations contain multiple, sometimes contradictory cultural frameworks simultaneously. Trice, H.M. & Beyer, J.M. (1993). The Cultures of Work Organizations. Prentice Hall.

72%

of employees report that their immediate team's culture differs significantly

from the organisation's stated culture. The gap between the macro culture and

the functional reality is not the exception. It is the norm. (Deloitte Human Capital Trends, 2024)

Sales vs tech vs ops - why functional cultures are structurally different

The cultural differences between functions are not superficial preferences or personality variations. They are structurally determined by the nature of the work itself - the feedback loops, the performance metrics, the social dynamics, and the cognitive demands that each function places on the people within it.

Consider three of the most common functional pairings in the organisations talentX works with:

Sales culture

Sales functions are characterised by short feedback loops - performance is measured daily, weekly, monthly. Individual contribution is highly visible and directly linked to reward. The relationship with rejection is a core competency: salespeople who cannot tolerate a high ratio of no to yes will not survive. Speed and momentum are cultural values because pipeline velocity is a performance driver. The willingness to commit before having perfect information - to say yes to a client and work out the details later - is often rewarded.

Technology culture

Technology functions operate on longer timescales. The feedback loop between effort and output is extended - a product sprint may take weeks before its quality can be assessed. Individual contribution is often embedded in collective output, making attribution less direct. Ambiguity is a working condition, not an exception. The relationship with being wrong is different: debugging, iteration, and revision are not failures but fundamental parts of the process. Depth of analysis and rigour before commitment are valued precisely because the cost of errors in complex systems is high.

Operations culture

Operations functions are built for consistency, reliability, and process adherence. The cultural premium is on predictability - variance from the expected is rarely celebrated and often penalised. Hierarchy tends to be more explicit because clear accountability is a safety and quality requirement. The relationship with innovation is cautious: changes to established processes carry operational risk, and the culture reflects that.

Now consider what happens when a single behavioural framework - even a well-designed one - is applied uniformly across all three.

The sales team finds the culture too slow and compliance-heavy. The technology team finds it too loud, too short-termist, and too focused on individual output metrics. The operations team finds ambiguity-tolerant cultural norms genuinely threatening to the precision their work requires.

None of them are wrong. They are responding rationally to a culture that was not designed for the specific demands of their function.

The Science

Van Maanen, J. & Barley, S.R. (1984). Occupational Communities: Culture and Control in Organizations. Research in Organizational Behavior, 6. Gregory, K.L. (1983). Native-View Paradigms: Multiple Cultures and Culture Conflicts in Organizations. Administrative Science Quarterly, 28(3). Both establish that functional identity is a primary driver of sub-culture formation, independent of organisational culture design.

What happens when you apply a uniform culture - the data

The consequences of uniform culture design in functionally diverse organisations are well-documented and commercially significant.

34%

Higher voluntary attrition in functions whose cultural norms conflict with the organisation's stated values, compared to functions whose informal culture aligns more naturally with the macro culture. (McKinsey Organisational Health Index, 2023). The cultural mismatch tax is measurable - and it shows up first in the functions most different from the cultural template.

The pattern is consistent across the research: when a uniform culture is applied to functionally diverse workforces, the functions whose natural operating norms are furthest from the cultural template disengage most rapidly. They do not reject the values intellectually - they agree with them. They reject them behaviourally, because the values as stated are incompatible with the specific demands of their work.

The technology function in an organisation with a sales-driven culture template finds the emphasis on individual performance visibility and rapid iteration at odds with the collaborative, methodical norms their work requires. Their engagement drops. Their attrition rises. And the organisation, looking at the aggregate data, cannot identify why the culture programme is working for some teams and not others.

The answer is in the data that most organisations are not collecting: engagement and behavioural data broken down by function, not just by seniority or geography. When you map culture health at the functional level, the sub-culture gaps become visible - and the design implications become clear.

2.3x

Higher likelihood of culture programme success when sub-culture differences are explicitly mapped and accounted for in the design, versus uniform implementation across all functions. (Harvard Business Review analysis of 100 culture change initiatives, 2022)

The most dangerous assumption in culture design is that the same values activation will land the same way in every function. It won't. And the functions where it lands worst are usually the ones the organisation most needs to retain.

Designing at two levels - macro culture and functional sub-culture

The solution to the sub-culture problem is not to abandon the aspiration of a unified organisational culture. It is to design at two levels simultaneously - and to understand clearly what belongs at each level.

01  The macro culture - what applies everywhere.

The macro culture defines the organisation's non-negotiable values, standards, and identity - the things that are true regardless of function. How we treat people. The standards of honesty and accountability we hold across the organisation. The commitment to quality that defines our relationship with clients. The values that are genuinely universal - that a sales person and a software engineer and an operations manager would all recognise as real, regardless of how different their day-to-day work is. The macro culture is the organisation's character. It does not tell people how to work. It tells them what they stand for.

02  The functional sub-culture - what applies here.

The functional sub-culture translates the macro culture's values into the specific behaviours, norms, and leadership expectations that make sense in each function. Accountability in a sales team looks different from accountability in a technology team - not because the value is different, but because the work is different. Psychological safety in an operations context requires a different set of leadership behaviours than psychological safety in a creative function. The functional sub-culture design answers the question: given the specific demands of this function, what does living our values actually look like in practice here?

03  The translation layer - how the two connect.

The most practically important element of dual-level culture design is the translation layer: the explicit documentation of how macro values map to functional behaviours. This is not a values poster. It is a Leadership and Behaviour Framework specific to each function - built from the macro culture, translated through the lens of functional reality, and owned by the functional leadership team rather than imposed from the centre.

This design approach requires more diagnostic rigour and more localised design work than uniform culture implementation. It also produces significantly better outcomes - because it asks each function to live the organisation's values in a way that is genuinely compatible with how they work.

What this looks like in CultureX practice

Sub-culture mapping is embedded in the CultureX Audit as a non-negotiable component of every culture engagement.

The audit does not measure culture as a single organisational score. It maps culture health across functions, teams, and leadership layers - identifying where the macro culture is strong, where it is fragile, and where the gap between the stated culture and the functional reality is widest.

The data consistently reveals three patterns:

First, functions that are furthest from the cultural template - whose operational norms are most different from the values as written - show the highest disengagement and the most scepticism about culture programmes. They are not wrong to be sceptical. The programme, as designed, was not built for them.

Second, the gaps between functions are often wider than senior leadership believes. The executive sub-culture - which tends to be closest to the stated values because those values were often designed to reflect how the leadership team operates - systematically underestimates how differently those values land in frontline functions.

Third, the functions with the strongest informal sub-cultures - the ones that have developed the most coherent and distinctive norms for how to operate effectively - are often the most resistant to uniform culture overlays, and the most responsive to sub-culture-sensitive design that respects what they have built.

The Codify stage of CultureX produces two outputs: the macro Cultural Operating Playbook that defines the organisation's non-negotiable values and standards, and function-specific Leadership and Behaviour Frameworks that translate those values into the specific behavioural expectations of each major function.

The Activate, Train, and Brand stages are then designed with functional differentiation built in - not as an afterthought, but as a design requirement. 

Because the most precisely designed macro culture will always underdeliver if its activation treats every function as the same.

CultureX doesn't design one culture and hope it lands everywhere. It designs one culture and ensures it lands differently - in the specific way that each function needs - while remaining coherent as a whole.

Where to start

People & Culture Audit  ·  CultureX

If you want to understand how your culture is actually landing across different functions - and where the gaps between your stated culture and your functional reality are widest - the CultureX People & Culture Audit includes full sub-culture mapping as standard. Evidence-based, commercially grounded, function-level diagnostic.

→ Book your People & Culture Audit: talentx.global/cultureX

Conversations are with a Senior TalentX Advisor to gain clarity on what's possible.

Danielle Blizzard is the Founder and CEO of talentX, a people and culture consultancy operating across the UAE, KSA, and the wider GCC. talentX works with government entities, high-growth scale-ups, and global brands to build cultures and leadership capability that deliver measurable performance.

talentx.global  ·  hello@talentx.global