Net Activated Value

The C-suite-facing metric that puts human capital and dollar outcomes on the same axis — what it does, what it doesn't, and why most people analytics work fails to produce one.

A CHRO and a CFO are sitting across from a CEO. The CEO has fifty million dollars uncommitted in the next planning cycle. The CFO has a list of capital-allocation options: a manufacturing line expansion, a software platform consolidation, a market entry in two new geographies, a customer-acquisition push. Each option has a dollar input, a return expectation, a confidence range, and a payback period. The conversation moves quickly.

The CHRO has a parallel list: a manager-effectiveness program, a leadership development cohort, a comp-band restructure, a re-skilling initiative for the operations org. Each option has a dollar input. None of them has a return expectation. None of them has a confidence range. None of them has a payback period. The conversation slows.

I have watched this meeting in different versions for twenty years. The CFO's options are not better than the CHRO's options. The CFO's conversational currency is better. The CHRO is competing for the same dollar against a function that can put numbers on the page in a format the CEO already knows how to evaluate. Human capital decisions get the leftover budget after everything that could be modeled claimed its share. The function isn't lazy. The function doesn't have a number.

Net Activated Value — NAV — is the number. Or rather: it's the one number I've been able to make work, across the kinds of organizations I've consulted with, that puts human-capital state and dollar outcomes on the same axis a CEO can compare against any other capital allocation decision.

This piece is the long argument for NAV. What it is, where it came from, the math underneath, what it's good for, and the part most matters — what it deliberately is not.

The constraint that produced the metric

I built the first usable version of NAV at a 500-person startup that I wrote about in the CAMS piece. The CEO had asked the wrong question and the right question at the same time: Why aren't we as productive as Google per employee? Wrong question because the comparison was load-bearing on conditions that didn't apply. Right question because underneath it was the real one: How much human-capital value am I getting for the dollars I'm spending, and where would another dollar get me the most?

That second question had no metric. The HR team could answer parts of it. They could track headcount cost. They could report engagement scores. They could surface attrition rates. None of the partial answers added up to what's the dollar value of the activated portion of the workforce, and how much opportunity is sitting on the table from the part that isn't activated?

I needed a single indexable KPI that could:

Be practical to implement in a company without a dedicated I/O psych team.
Be easily grasped by front-line managers, not just analysts.
Correlate to employee performance.
Correlate to business performance.
Be administered anywhere by people without a PhD.
Be tracked monthly or quarterly as a regular management ritual.
Be used in conjunction with other data to make better decisions.

Those seven criteria are tighter than they look. Most candidate metrics fail at least two. Engagement scores fail the dollar-correlation criterion: they correlate to retention and discretionary effort but not directly to outcomes. Attrition rates fail the activation criterion: they measure who's leaving, not who's productive. Performance ratings fail the cross-organization criterion: they're calibrated within each company's review process and don't compare. Net Promoter Score for employees (eNPS) fails the diagnostic criterion: it tells you the team is unhappy but not what to do about it. Productivity-per-employee numbers fail the human-capital criterion: they measure output, not the underlying state of the workforce producing it.

What I needed was a metric whose unit was the activated portion of the workforce, valued in dollars. The path to that was: measure activation, convert to a percentage, multiply by a dollar value per employee. That's NAV in one sentence. The rest of this piece is what makes each step honest.

The activation half: from CAMS to Net Activated Percent

The activation half of NAV is CAMS. The longer argument for CAMS is in the previous piece; the short version is that four conditions — Capability, Alignment, Motivation, Support — have to be jointly present for an employee or team to consistently produce at or above expectations. An eight-item survey on a 0–10 agreement scale produces an index from 0 to 80 per respondent. From the index:

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

Net Activated Percent is the input to NAV from the human-capital side. It's a percentage of the workforce — typically computed at the segment level (function, geography, business unit) because the dollar side will need to be segmented too.

A few properties of the percentage worth flagging:

It excludes the at-risk population from the numerator, not the gap-band (the 60–70 range). The gap band is in the denominator but not the numerator — a deliberately conservative count. The Net Activated Percent of a company with half its workforce in the gap band will be lower than a company with the same activated population but most of the rest at-risk. This is correct: the gap band is not activated, even though it's also not actively failing.

It moves slowly. CAMS is a stable construct over weeks; you don't see whipsaw in the percentage from month to month unless something material changed in the org. That stability is part of the metric's value. NAV is supposed to be tracked at planning cadence; a metric that twitches with the news cycle is unusable in capital-allocation conversations.

It's not a satisfaction metric. A workforce can be highly activated and unhappy about specific decisions; a workforce can be perfectly satisfied and underperforming. The activation construct is designed to predict production, not contentment. The two are correlated but not the same.

The dollar half: ELV per segment

The dollar half of NAV is ELV — Employee Lifetime Value. The naming is borrowed from customer lifetime value (CLV), which is one of the most familiar metrics in commercial analytics. ELV is the people-analytics analog: the dollar value an employee represents over their tenure, computed per segment.

The calculation is:

ELV per segment = HCROI × annual cost × lifetime tenure

Three terms.

HCROI is human-capital return on investment. The cleanest definition is (revenue − non-people-costs) ÷ people-costs — the dollar return per dollar of people spend. It's an aggregate company-level number, sometimes available from finance, sometimes reconstructable from public reporting for benchmarking. HCROI varies hugely by industry: knowledge-work-heavy industries (software, professional services) run higher than capital-intensive ones (manufacturing, retail) because the same dollar of people spend leverages more downstream revenue.

Annual cost is the fully-loaded annual cost of an employee in the segment: salary + benefits + payroll taxes + overhead allocations. The finance team can produce this number per segment without extra instrumentation.

Lifetime tenure is the expected duration the employee stays with the company, per segment. Tenure varies by segment, role, level, and labor market. Three to seven years is a typical range; the exact number is empirical from the company's own data.

Multiplying the three gives the dollar value of an average employee in the segment, over their tenure. It is not an exact number. It is, importantly, a defensible number — every term is reconstructable from finance and HR data, every term has a clear meaning, and reasonable analysts will get reasonable agreement on it. That's what NAV needs from the dollar side: a number the CFO can review without quarrel.

Putting them together

NAV per segment is the simple product:

NAV per segment = (Segment Net Activated %) × (Segment ELV)

NAV is the dollar value of the activated portion of the workforce in the segment. If a segment has 100 employees, an ELV per employee of $400,000, and a Net Activated Percent of 75%, then:

Total potential workforce value: 100 × $400,000 = $40 million
NAV: 75% × 100 × $400,000 = $30 million
Opportunity: $40 million − $30 million = $10 million

The opportunity number is where the C-suite conversation lives. Ten million dollars of value sitting on the table in this segment from the unactivated portion of the workforce. That is a number a CEO can compare against the manufacturing line expansion and the market entry in two new geographies. The CHRO has joined the capital-allocation conversation as a peer.

The interesting comparison is across segments. A segment with high ELV and high Net Activated Percent contributes a lot of dollar value but has little remaining opportunity — additional investment there has a low ceiling. A segment with high ELV and low Net Activated Percent has a lot of opportunity — fixing the activation gap there has a high ceiling. A segment with low ELV is harder to lever even at low activation. The matrix of (ELV × Net Activated Percent) per segment is what tells the CHRO where the next dollar should go.

NAV is a thinking tool, not an accounting measure

This is the part I've had to repeat in every C-suite conversation about this metric. NAV is not a rigorous accounting measure. I am not going to defend the dollar number in a board meeting as the audited human-capital value of the workforce. There are too many estimates in the chain. HCROI is reconstructed from a combination of finance reporting and analyst judgment. Annual cost is approximate at the segment level. Lifetime tenure is empirical but uncertain. The activation index is a survey instrument with construct validity but not perfect precision.

What NAV is, instead, is a thinking tool. It's the metric that lets a CHRO and a CFO and a CEO have the same conversation about human capital that they're already having about every other capital allocation decision. It puts the dollars and the workforce state on a single axis. It generates the right questions: which segment has the largest opportunity? what's driving the activation gap there? what intervention would close it, and what would that cost?

The questions are what matter. The exact NAV number is less load-bearing than the comparative NAV across segments, and the comparative NAV is less load-bearing than the conversation it produces. When the CFO challenges a NAV calculation, the correct response is not to defend the number; it's to acknowledge the estimation chain, ask whether the comparative ranking across segments is in dispute, and move the conversation to the action the comparison implies.

This is the same posture a CFO takes about discounted cash flow modeling on a major investment. The DCF is precise to the last decimal in the spreadsheet; nobody believes the spreadsheet. What the CFO believes is that the DCF surfaces the right comparison among alternatives and forces the assumptions into the open where they can be argued. NAV operates the same way for human capital.

What NAV does in a C-suite conversation

The pattern that's emerged across the engagements I've run:

NAV gets reported at planning cadence — quarterly is typical. The CHRO brings a one-page summary: NAV per segment, comparative NAV across segments, the per-factor CAMS scores underneath each segment's Net Activated Percent, and the dollar opportunity (ELV − NAV) per segment.

The CEO and CFO use it to triage. The largest opportunities get attention first. The conversation isn't how do we improve engagement? — that's a perennial agenda item that never resolves. The conversation is the operations segment has $14M of opportunity, the per-factor breakdown shows alignment is the weak factor, what would it take to close the alignment gap? The question is specific. The answer is bounded. The investment can be sized against the opportunity.

The CHRO uses it to defend investments. When the comp-band restructure costs $2M and the case is that it will lift Net Activated Percent in a segment with $14M of activation opportunity, the CFO has a recognizable shape to evaluate against. Even if the precision is rough, the comparative claim is legible. Investments that can't articulate a NAV-style lift get re-evaluated against ones that can.

The CFO uses it to challenge. NAV calculations are routinely contested. The HCROI assumption is wrong, the tenure number is dated, the activation index is biased toward newer employees. Each challenge is useful. Either the challenge is right and the calculation tightens, or the challenge is wrong and the metric gets reinforced. The metric becomes more durable through the contest, not less.

The conversation that doesn't happen is the conversation about whether human capital matters. That conversation is over the moment NAV is on the page. The CEO has dollar value, dollar opportunity, and segment-level comparisons. The question of whether to invest in human capital becomes a question of which investment in human capital, against which opportunity, at what cost. That is a normal capital-allocation conversation.

What NAV is not

NAV is a tool with a specific job. It is not:

A measure of culture. Culture is broader and has its own instruments. NAV is silent on whether the company has the culture it wants.
A measure of equity or fairness. Compensation equity is measured separately; pay-gap analyses run on different data with different methodologies; NAV doesn't capture them and shouldn't be repurposed to.
A measure of strategic talent risk. Some employees are load-bearing in ways the segment-average ELV doesn't capture — a single key engineer, a CRO who's irreplaceable in a one-year window. NAV is a portfolio-level metric; succession-critical risk is a different analytical surface.
A retention model. NAV doesn't predict who's leaving. It measures the dollar value of the currently-activated workforce, not the durability of that activation against external offers.
A productivity instrument. NAV reflects the conditions for production (the four CAMS factors) and the dollar value of the workforce. It doesn't measure output directly. Productivity per employee is a different metric with different uses.

Each of those is a real analytical question. Each one has its own instrument, its own data inputs, its own science. NAV's discipline is that it does not absorb them. The metric holds its lane: dollar value of the activated workforce, opportunity from the unactivated portion, compared across segments, surfaced at planning cadence.

How NAV got to be the metric

I want to be honest about the path the metric took. I did not derive NAV from first principles. I built three or four versions of an indexable KPI for the 500-person startup, watched which one survived contact with the CHRO, the CFO, and the CEO, kept the parts that survived, and discarded the parts that didn't. The seven criteria at the start of this piece are reverse-engineered from the version that worked.

The CAMS activation construct came together first because the four-factor conjunction was diagnostic at the team level. The ELV calculation came together because finance could already produce most of the inputs and didn't need an instrumentation buildout. The product of the two — NAV — came together because the CHRO had a problem the CFO had a solution to, and putting them on the same axis let the two functions talk to each other.

That's the part I'd encourage anyone trying to do this work to take seriously. The metric you build will not be NAV unless your company is shaped like the ones I built it for. It will share NAV's structure: an activation construct that measures the workforce state, a dollar construct that translates state into outcome, a multiplication that puts them on a single axis, a segment-level decomposition that supports comparison. The specific calibration will depend on the company. The structure carries.

Closing

Two things tie this piece together. One: NAV is the C-suite-facing metric that puts human capital and dollar outcomes on the same axis. The math is simple. The work is in the construct validity underneath the activation index, in the segment-level calibration of the dollar side, and in the discipline of not asking the metric to do more than it can.

Two: NAV is a thinking tool, not an accounting measure. The number is less load-bearing than the comparison it enables. The comparison is less load-bearing than the conversation it produces. The conversation is the point. When the CHRO walks into the planning meeting with NAV per segment, the function has the same shape of input the CFO has had for decades. Human capital decisions get evaluated against the alternatives they are actually competing against.

That's the case for NAV. The first version I built failed at a startup that, in the end, didn't recover. The metric did. It worked there, it worked at the engagements after, and it works now in the consulting practice that grew out of those years. The constraint that produced the metric — a CHRO without a number in a capital-allocation conversation — is still the constraint most people analytics functions are stuck inside. NAV is one way out.