Support — Does the Environment Enable the Work?

The question

Does this team's environment enable the work?

Support is the dimension organizations are worst at seeing, because it isn't located in the people — it's the conditions around them: manager support, tools, staffing, process design, psychological safety, workload, resources, feedback, and recovery.¹ When performance is missing, the instinct is to look at the team. Support insists you look at what's been put around it first.

The strongest claim in the whole model

This is where Gilbert's Behavior Engineering Model makes its most important — and most counterintuitive — claim. Across his six cells, three are environmental (information, resources, incentives) and three are individual (knowledge, capacity, motives), and his data put most performance variance in the environment, not the person.² He went as far as to say that "evidence of low motivation is a red flag to look for deficiencies in information, resources, or incentives" — because work-environment factors "will not directly motivate employees," but fixing them is what actually lets people perform.²

That is a strong claim, and it's the source of the guard built into the CAMS pick rule (Part IV): before you treat a team as unmotivated or incapable, rule out that the environment is starving them. A large share of what gets diagnosed as a people problem is a Support problem in disguise — the team is fine, the conditions aren't.

The evidence keeps pointing the same way. HBR's own reporting on why performance management is being rethought surfaces the manager as the dominant environmental factor: a McKinsey survey found 75% of people said the most stressful aspect of their job was their immediate boss — "people join companies and leave their managers."³ The manager isn't outside the system being measured; the manager is part of the team's environment, which is exactly why "manager support" sits under Support, not somewhere else.¹

And Hackman's work on teams makes the structural version of the argument: great team performance comes less from coaching individuals than from getting the enabling conditions right — a real team, a compelling direction, an enabling structure, a supportive context, expert coaching.⁴ Set the conditions and performance follows; leave them broken and no amount of individual effort compensates.

A boundary the model holds

Psychological safety lives here, in Support — it's an environmental enabler of work (can people speak up without consequence?), distinct from SDT-relatedness in Motivation (belonging and connection).¹ They feel adjacent but route to different fixes: a relatedness deficit is a motivation intervention; a safety deficit is an environment-and-leadership one. Keep them apart.

The Performix take

Support is the dimension protected feedback is almost designed to surface, because the people who can see environmental constraints most clearly — the team living inside them — are exactly the people least able to say so safely up the chain. A manager-administered review will rarely surface "the manager is the problem" or "the process is broken"; an anonymized, protected instrument will. This is also where Merchant's controllability principle bites: holding a team accountable for outcomes its environment doesn't permit is both unfair and uninformative.⁵ Measuring Support directly is how you avoid charging teams for constraints that were never theirs to fix.

When Support is the binding constraint

If the diagnosis lands on Support, the lever is to resource and re-engineer the environment: fix tooling, staffing, workload, process, or manager behavior; build the conditions Hackman names.⁴ This is the constraint most likely to have been misdiagnosed as something else — which is the whole reason to measure it as its own dimension. A starved team cannot be trained or motivated out of a broken environment; it can only be un-starved.

---

Footnotes

1. The CAMS construct model — Support sub-constructs (manager support, tools, staffing, process design, psychological safety, workload, resources, feedback, recovery); the psychological-safety (Support) vs relatedness (Motivation) and manager-support (Support) vs manager-clarity (Alignment) boundary calls. ↩ ↩² ↩³

2. Van Tiem et al., Fundamentals of Performance Technology — Gilbert's Behavior Engineering Model; environment-first; "low motivation is a red flag to look for deficiencies in information, resources, or incentives." ↩ ↩²

3. Cappelli & Tavis, HBR's 10 Must Reads on Performance Management — McKinsey: 75% say the most stressful aspect of the job is the immediate boss. ↩

4. Hackman, Leading Teams: Setting the Stage for Great Performances — Part II "Enabling Conditions": (2) A Real Team, (3) Compelling Direction, (4) Enabling Structure, (5) Supportive Context, (6) Expert Coaching. ↩ ↩²

5. Merchant & Van der Stede, Management Control Systems — the controllability principle. ↩