October 23, 2026

Team receptiveness: understanding the subcultures that shape change

I’ve argued before that some organisations are systemically more change-receptive than others. The same holds at the team level. 

Functions end up with their own levels of change receptiveness, and for much the same reasons. The work shapes who it attracts, the professional communities those people belong to reinforce a particular set of assumptions, and the reward structures make some attitudes sensible and others expensive. What you get are functional subcultures that look remarkably similar from one organisation to the next.

To understand some of what’s going on, start by asking what incentives are built into the role. The obvious examples are Risk & Compliance and Finance. They’re consistently found to be risk-averse and more change-avoidant than other functions. Managing risk is their whole purpose, so we wouldn’t expect them to welcome change, unless it’s specifically aimed at reducing risk. 

Conversely, Sales and Marketing tend to be the opposite: their job is to engage with a world outside the organisation that keeps moving, and their rewards pull them towards opportunity rather than risk reduction. They’re the closest thing most organisations have to a built-in pioneer function. That’s all fairly intuitive where the incentives are obvious – but what about everyone else?

The most influential framework here is Edgar Schein’s ‘Three Cultures of Management’, which argues that every organisation holds three deep occupational subcultures1:

  1. The executive culture: CEOs and their immediate teams.
    This is shaped by the global community of senior leaders, by capital markets and by financial accountability. It’s rewarded for strategic flexibility and is generally comfortable using change as a tool. Which explains something I see constantly: senior leaders find it genuinely hard to grasp why staff aren’t as keen on the latest initiative as they are, and change workstreams end up chronically underfunded as a result.
  2. The engineering culture: the technical professionals who design and build the organisation’s products and processes.
    This culture takes its cues from the global community of engineers, scientists and technologists. It’s innovation-minded about technical things, but inclined towards what Schein called ‘people-free’ solutions. 
  3. The operator culture: everyone doing the day-to-day work.
    It’s shaped by the particular organisation and its history. It’s usually the most sceptical about change that’s been imposed, because when operational change goes wrong, these are the people it impacts first.

Anderson and colleagues tested the model with a psychometric tool called the Instinctive Drives System, across nearly 4,000 employees in several international companies. Executives scored significantly higher on preferences for variety, flexibility and change; operators and engineers scored higher on logic and certainty.2 

What this means for practitioners takes a bit of unpicking. Start by separating innovation from change receptiveness. Innovation is about designing compelling solutions; change receptiveness is about adopting them. Design is basically a technical process, even if it often needs real empathy to determine what customers want. Change is a human process. Schein’s model matches what I see in technical functions like Engineering or R&D, where people get excited about a new product or system on the strength of its features. If the new thing is something they’ve built, they’ll get frustrated when people don’t adopt it immediately. And if the new product or service is built by someone else, then there’s a job to convince those in the function that the thing is technically sound. From my experience, once these clever guys are convinced, they’ll go and learn it themselves, needing almost nothing from the change workstream.

In contrast to this illustration of engineering culture, the operator culture – everyone else – might not have any particular incentive pulling people to either end of the ‘receptiveness spectrum’.So other things take over: individual receptiveness and receptiveness at the organisation level.  

To win this group over, lean on the 25% rule – the finding that you need only around a quarter of people actively behind a change for the rest to follow.3 Work out where your pioneer functions are as that’s where you’ll find the quick wins and early adoption. The more hesitant functions are where the engagement effort should go, and where the concerns raised are most worth hearing. As I’ve argued before - see The case for custodians linked here, the people who oppose change most visibly  are often the ones holding the organisational insight you need to judge whether the change itself is any good. Functions work the same way. A Risk function raising substantive concerns about an operational change is doing exactly what you employ a Risk function to do.

So ‘how receptive is this population?’ is really a question with three layers: the individual, the function and the organisation. A coherent change strategy covers all three. Where all three point towards resistance, be realistic about the effort involved, put more effort into trust and engagement, and lean on the less eager functions openly, as critical friends. Where all three point towards openness, the job is channelling the enthusiasm so the change doesn’t overwhelm the capacity to embed it. For more on change capacity, download our second FRICtion Factors® white paper.

Checklist
  • Map functional subcultures before designing the change. 
  • Work out your pioneer functions (usually Sales, Marketing, parts of R&D and product) and your less receptive ‘custodian’ functions (usually Risk, Compliance, Finance, HR and parts of Engineering and IT infrastructure).
  • Engage custodian functions as critical friends rather than obstacles to steer around. As with individuals, their concerns often raise design weaknesses nobody else has spotted.
  • Where the three layers stack up – a custodian person, in a custodian function, in a custodian organisation – lower the ambition, stretch the timeline, and build trust before you push for behaviour change.
Footnotes
  1. Schein, E. H. (1996) ‘Three cultures of management: The key to organizational learning’, Sloan Management Review, 38(1), pp. 9–20. ↩︎
  2. Anderson, J. C., Worley, C. G. et al. (2011) ‘Organisational change: Communicating to Schein’s operator, engineer and executive occupational subcultures’, Journal of Change Management. ↩︎
  3. Centola, D., Becker, J., Brackbill, D. & Baronchelli, A. (2018) ‘Experimental evidence for tipping points in social convention’, Science, 360(6393), pp. 1116–1119. ↩︎