Why CAMS

The activation framework, the conjunction problem, and the eight items that make it executable without a PhD.

A few years ago I sat in a conference room at a 500-person startup that was bleeding out. The product was good. The funding was real. The talent was, on paper, competitive. But unit-economics had inverted. Per-employee output was below comparable companies. Stock options were re-pricing on every round. The CEO wanted to know what was wrong.

The HR team had data. They had a 60-item engagement survey, an annual performance rating cycle, an attrition dashboard, two pulse surveys a quarter, and a manager-effectiveness model imported from a Google talk. None of it answered the question.

What I was working toward — and what fell out of that engagement — was a single number that could be calculated monthly, explained to front-line managers, and tied to the dollars the CEO actually cared about. The number on top is NAV (Net Activated Value); I'll write a separate piece on that. The number underneath, the one this piece is about, is CAMS — the four conditions an employee or team has to have in place to consistently produce at or above expectations.

CAMS stands for:

Capability — what people bring to the company: knowledge, skills, abilities.
Alignment — knowing what's expected and how they're performing against it.
Motivation — preferences, commitment, engagement — the willingness to do the work.
Support — tools, resources, manager and peer relationships, absence of negative consequences.

That list is short on purpose. Most activation frameworks I've encountered in twenty years of this work have eight to twelve dimensions. CAMS has four. The reason for four — and the reason the four matter the way they do — is what this piece is about.

The conjunction problem

Here's the load-bearing claim, and it's the one most activation work gets wrong: all four conditions have to be present. Not three out of four. Not "mostly capable, motivated, supported, but alignment's a little fuzzy." All four.

The intuition most people import from elsewhere is additive. If I'm 80% capable and 80% motivated and 80% supported and 80% aligned, that should add up to about 80% activated, give or take. It does not. Performance doesn't work that way. If alignment is wrong — if I think the priority is X and my manager thinks the priority is Y — capability, motivation, and support buy me precision in the wrong direction. I will produce well. I will produce the wrong thing well. The team will look busy and miss its quarter.

Run the same logic through each factor:

Capable, aligned, supported — but not motivated. The person can do the job, knows the priorities, has the tools, and chooses not to spend discretionary effort. The work meets minimum bar. The hard problems don't get solved.
Capable, motivated, supported — but not aligned. The person has KSAs, wants to contribute, has resources, and is rowing the wrong direction. Output is high; impact is wrong.
Aligned, motivated, supported — but not capable. The person knows what to do, wants to do it, has what they need, and lacks the skill. The work doesn't ship, or ships at quality that won't survive contact with a customer.
Capable, aligned, motivated — but not supported. The person can do it, knows what's expected, wants to do it, and the system blocks them. Tools are missing, the manager is absent, peer relationships are hostile, or the org keeps penalizing the behavior it claims to want.

Each combination fails. It doesn't fail at a smaller scale than full activation; it fails differently, in patterns that look like other problems. Missing alignment looks like a strategy problem. Missing motivation looks like an engagement problem. Missing capability looks like a hiring problem. Missing support looks like a manager problem. In each case the diagnosis points away from the actual cause.

That's the structural reason the conjunction matters. You don't catch the failure by measuring any single factor harder. You catch it by checking all four — and by being willing to act when any one of them is missing, regardless of how strong the other three are.

What the field usually does instead

Most companies measuring activation pick a frame and stay in it. Engagement-led organizations measure motivation, score it, slice it by manager, and call the analysis complete. Capability-led organizations focus on KSAs — competency models, skills inventories, learning-and-development spend. Alignment-led organizations live in OKRs and rating distributions. Support-led organizations focus on tooling, manager effectiveness, removing-friction surveys.

Each of these is a real discipline. Industrial-organizational psychology has decades of work behind each dimension. Engagement alone has been measured at scale since the 1990s; Gallup's Q12 (Buckingham & Coffman, First, Break All the Rules) is the most-cited instance and remains a useful instrument. Goal-alignment research goes back further (Locke and Latham's goal-setting theory; A Theory of Goal Setting and Task Performance, 1990). Job demands-resources frameworks (Bakker and Demerouti, ongoing) anchor the support-and-burnout work. The classifier-tagged library at PA-site surfaces these strands across both the behavioral-science and people-analytics-bridge frames.

The problem isn't the disciplines. The problem is what happens when the disciplines stay in their lanes. A company doing engagement analysis at the Q12 level will get a clean read on motivation and will routinely miss alignment failures that are wrecking the same teams. A company doing OKRs without instrumented engagement will get clean alignment metrics and will miss the team where everyone knows the goal and quietly disengages because the work itself is unsustainable.

The activation framework's value isn't that any single dimension is novel. It's that the conjunction is the unit of analysis. You don't measure motivation; you measure whether the team has all four conditions. The data is cheaper than the alternatives. The diagnostic is faster. And the action is unambiguous: when any of the four scores low, that's the lever.

The eight items

The CAMS index is an 8-item survey. Two items per factor: one written from the team perspective, one from the individual perspective. All eight items use a 0–10 agreement scale. The total runs 0 to 80 per respondent.

The survey is intentionally short. A 60-item engagement instrument has psychometric range and gives an academic measurement team a lot to work with. It also has a response-rate problem, a fatigue problem, and an interpretation problem when you try to act on it. The eight items trade some psychometric depth for executability: a manager can administer it, a respondent finishes it in two minutes, and the index produces actionable signal at the team level.

The two-perspective design — team and individual per factor — is the part that took the longest to get right. An individual can be personally capable and motivated and supported and aligned, working alongside a team that isn't. Or the team can be high-activation in aggregate while one person on it is collapsing. The team-perspective and individual-perspective items disambiguate. You can see when the average hides the underlying state.

The exact wording of the items is calibrated through use — items get tested against the construct, retired when they cluster with the wrong factor, replaced when language shifts. (Construct validity is the boring word that does the work here; see the 4S piece for the longer argument on why this matters.) What stays stable is the design: four factors, two perspectives, ten-point agreement, eighty-point total.

The thresholds and what they mean

From the 0–80 index, two thresholds:

Activated = CAMS index ≥ 70.
At-Risk = CAMS index < 60.
Net Activated Percent = (workforce − at-risk in workforce) ÷ total headcount.

The 60–70 band is intentionally a gap. People in that band aren't activated by the threshold definition; they're also not at-risk. They're the population where the diagnostic is least clear and where intervention has the least predictable return. Treating them as either activated or at-risk overclaims; treating them as a band-to-watch gives the manager something to do that isn't a false alarm.

The Net Activated Percent is the headline operating metric. It's a percentage of the workforce; it ranges 0% to 100%; it can be tracked monthly or quarterly; it can be sliced by segment, function, manager, tenure. When it moves, you can usually see which factor drove the move by looking at the per-factor scores underneath it. That's the manager-level reporting layer.

There's a temptation to compress this further — one number, one threshold, one percentage. The temptation is wrong. The four-factor structure is what makes the index diagnostic. Collapsing it to a single composite preserves the score-tracking but loses the action. The point of CAMS isn't to grade activation; the point is to surface which of the four conditions is breaking, so the intervention can be aimed.

How CAMS gets used in practice

The pattern that's emerged across the engagements I've run this on, after the 500-person startup:

Monthly or quarterly cadence. The frequency depends on the company's rhythm — startup teams usually monthly, larger organizations quarterly. The index is administered as a routine instrument, not an event. When something becomes an event, response rates collapse.

Reported at the team level first. Individual scores exist for the survey to function; they don't get surfaced to managers. The manager sees their team's index, their team's four per-factor scores, their team's net activated percent. The org rolls up.

Acted on at the factor level. When a team's index drops, the question isn't "are we activated?" — the index already answered that. The question is which factor is low? If alignment dropped, the conversation is about clarity of priorities and feedback. If motivation dropped, the conversation is about why discretionary effort fell. If support dropped, the conversation is about what's blocking. If capability dropped, the conversation is about what's changed in the work versus the skills on the team.

Tracked over time. A single index reading is a snapshot; a trend is signal. Most of what CAMS catches is in the change, not the level. A team running at 72 that drops to 65 has lost something; finding it early matters more than the absolute number.

Tied to dollars at the segment level. This is where NAV comes in — the C-suite-facing metric that translates Net Activated Percent into the dollar opportunity created by the unactivated portion of the workforce. I'll get to that in the next piece. For now, the point is that CAMS sits one layer below NAV — the diagnostic underneath the dollar conversation.

Where this differs from engagement

Engagement is a useful word that has lost most of its meaning. The original construct — discretionary effort, emotional commitment, intention to stay — was specific. As the instrument category commoditized, "engagement" stretched to include satisfaction, advocacy, well-being, fit, manager relationship, career path, recognition, and roughly anything else a vendor wanted to sell.

CAMS is narrower on purpose. Motivation, as one of the four factors, is engagement-shaped — it covers preferences, commitment, the willingness to do the work. The other three factors are not engagement. Capability is a skills question. Alignment is a goal-and-feedback question. Support is a tools-and-relationships-and-system question. Conflating them inside a single "engagement" composite is what makes engagement scores useless for diagnostics. The team scored low on engagement — was it because the people don't want to work, or because they can't, or because they don't know what they're supposed to do, or because the system keeps blocking them? Engagement-as-currently-measured doesn't tell you.

That's the diagnostic lift. CAMS keeps motivation as one of four factors. It refuses to absorb the others into it.

What CAMS does not do

CAMS is an activation framework. It is not:

A performance rating. A team can be activated and still produce middling work if the strategy is wrong or the market shifts. Activation is necessary, not sufficient.
A retention model. CAMS doesn't predict who's leaving; that's a different instrument with different inputs. Some high-CAMS people leave for reasons that have nothing to do with activation (a spouse's job, a better offer, a life event).
A culture survey. Culture is broader. CAMS measures the four conditions that drive consistent performance; it doesn't tell you whether the org has the culture it wants to have.
A diversity, equity, or inclusion instrument. Those measurements have their own constructs and their own science. CAMS items should not be repurposed to ask DEI questions; the construct validity collapses.

The discipline of saying what an instrument doesn't measure is part of why the instrument keeps working. Many activation frameworks fail by expanding to cover anything anyone asked them to cover. CAMS holds its lane: four conditions for consistent above-expectation performance, eight items, two thresholds, one net percentage. Everything else lives in other instruments.

Why this matters for everyone, not just Google

The version of this story most people analytics professionals have heard runs through Google or another elite organization. The case there is that Google had the budget, the I/O psych talent, the data infrastructure, and the executive commitment to run a 60-item engagement instrument continuously across tens of thousands of employees and act on it.

Most companies do not have any of that. Children's Medical in Dallas — a non-profit children's hospital where I built the people analytics function early — couldn't. The 500-person startup I worked with afterwards couldn't. Most of the companies I've consulted with since couldn't either.

The reason CAMS exists in the form it does is that the alternative isn't a smaller version of Google's instrument; it's no instrument at all, or a vendor product that doesn't have behavioral science underneath it. The eight-item survey, the four-factor diagnostic, the team-level reporting — all of it is engineered to be implementable by a one-person people analytics function with a spreadsheet and a survey tool, in a company that will never have Google's budget. That's the constraint that produced the design. The constraint isn't a limitation; it's the design objective.

If the field can only do activation analytics at Google scale, it stays where it is — accessible to the few elite organizations and locked out of the rest. CAMS is one attempt to fix that. Not the only one. The first one I built that worked across organizations.

Closing

Activation is a conjunction. Four conditions, each necessary, none sufficient on its own. Eight items measure the conjunction; two thresholds turn the index into action; one net percentage rolls up to the dollar conversation. The framework is short, the survey is short, the diagnostic is fast.

The longer argument — for the dollar tie, for the segment-level analysis, for the C-suite use of NAV as the indexable KPI tying human capital to outcomes — is the next piece. CAMS is the layer underneath. If the four conditions are right, the rest of the analytics can compound on top of them. If any one of the four is missing, no amount of additional sophistication recovers the team.

That's the case for CAMS. The case for Why CAMS specifically and not the dozens of adjacent frameworks is the conjunction. It's the part most activation work gets wrong. It's the part this one tries to get right.