In brief

Organizations hire, train, and increasingly reskill for capability, then assume that capability will be available when conditions change. Frequently it is not. The skill remains intact while access to it narrows, and the behavior that results gets read as resistance.

People readiness is the capacity of people to access and apply what they are capable of when conditions change faster than their habits can adjust.

It is not engagement, which indicates how invested people are in their work. It is not culture, which describes what is typical rather than what is available now. It is not a mood. It is a state rather than a trait, it moves as demands change, and it is drawn down by three conditions in particular: when expectation stops matching outcome, when a working routine has to be rebuilt while still being relied on, and when something is personally at stake.

This matters because it is routinely misdiagnosed. Organizations respond to narrowed access with more communication, stronger mandates, and further training. Where those responses add load without reaching the constraint, they narrow it further. The plan is rarely what fails. The condition of the people asked to execute it usually is.

---

The article

Two teams inside the same organization receive the same plan. Same tools, same budget, the same quality of leadership attention, and people of comparable ability. One team works its way through. The other slows, fragments, and delivers well short of what was intended.

This happens often enough to be a pattern rather than an accident, and the explanations usually offered do not account for it. Communication was poor. The wrong person was leading. There was resistance in the middle layer. Occasionally one of those is correct, or forms part of a larger picture. More often they describe what happened without explaining why it happened in one team and not the other.

The difference sits in a place most organizations do not examine, largely because they have no instrument pointed at it.

Skill is not the same as access to it

Consider what an organization is actually able to draw on when something difficult arrives. It hires for skill, it develops skill, and increasingly it reskills at scale, on the assumption that skill is what will be available at the moment of demand.

A skill, though, only produces value in context, and three conditions have to hold before it produces anything at all. The organization has to know the skill exists. The person holding it has to recognize that the situation calls for it. And they have to be able to bring it forward at the point where it would count, on their own initiative rather than waiting to be directed.

Each of those can fail on its own. An excellent analyst may never bring their analysis to the decision that needed it, because nobody knew to ask, or because they did not identify the decision as one requiring that kind of judgment, or because they identified it and could not act on it in the moment. The skill was present throughout. It produced nothing. And none of what went wrong is a property of the skill. It is a property of the conditions people are working under, and of what those conditions do to them.

When conditions are stable, the distance between what people are capable of and what they actually contribute stays small enough to ignore. When conditions change quickly, that distance opens, and it opens unevenly across a team.

That distance is what people readiness names.

The definition

People readiness is the capacity of people to access and apply what they are capable of when conditions change faster than their habits can adjust.

It is the term I have developed through my work at TPRC, and it draws on established work in threat-rigidity, cognitive flexibility, psychological safety, and readiness for change, none of which it is intended to replace. What it isolates is narrower: how much of a person's existing capability stays available to them as conditions change.

Where that capacity is high, people stay focused, keep talking to one another, and continue to make decisions of the quality the organization requires. Where it is low, their range contracts. They wait for instruction, they protect their position, and they withhold judgment that would have been useful. Sustained across a team, that contraction is part of what an organization experiences as resistance.

That capacity has three requirements: recognizing what the situation calls for, reaching the relevant capability, and translating it into action.

The same plan therefore produces different outcomes in different parts of the same company, and the variable responsible is rarely the one that gets examined.

How access begins to narrow

Capacity and access are closely related without being the same thing. Capacity is how much effective range a person has available under current conditions. Access is whether they can bring the relevant part of that range forward when the situation calls for it. As capacity is drawn down, access becomes less reliable, and it does so before anyone notices, because the person continues to appear competent while operating on a reduced range.

Across my work with organizations through TPRC, three conditions have appeared repeatedly when access begins to narrow. They rarely arrive one at a time, and they are not a closed list.

When expectation stops matching outcome.
Everyone works from a model of how things behave: how long an approval takes, how a client tends to respond, what a colleague will do with a piece of work. That model is what makes ordinary judgment fast. When outcomes stop confirming it, attention is pulled away from the work itself and toward the more basic question of what is now true. This reallocation is involuntary and it is invisible from outside. The person still attends every meeting. They are simply spending a substantial share of their attention rebuilding a map rather than using one.

When an established routine stops producing results.
Routines hold a large part of a person's effectiveness and they hold it cheaply, because a practiced sequence requires little deliberate thought. When a routine has to be reconstructed while still being depended upon, the cost of ordinary work rises steeply. Tasks that were automatic become deliberate. What was previously available for judgment, initiative, or helping someone else is consumed by work that used to require none of it.

When something is personally at stake.
Standing, security, or control over one's own work. This does not require the threat of redundancy, which is why it is so often missed. The prospect of being visibly less competent than one was six months ago is sufficient, and during a significant technology or operating-model change that prospect is widespread. Under it, people become cautious about precisely the things the organization needs from them: proposing something untested, saying they do not know, disagreeing with someone more senior.

Under any of these, the skill itself is unchanged. What narrows is the person's access to it. They still know what they know. They cannot reach it at the point where it would have mattered.

Capacity is the accurate word here, because capacity can be full or depleted. It is not something a person either owns or lacks. It is something they hold more or less of, in a given period, under a given load.

It's not mood either

Capacity described in a mental context is often shortened to mood, and the two get treated as one reading. They are not the same. Mood is what a person reports about how they feel. People readiness is what they are able to do, and the two separate routinely. People in good spirits underperform their own capability regularly. People under considerable strain sometimes produce their best work. What is at issue is availability, not affect.

It is also why training so often fails to produce the change it was bought to produce. Training adds skill. Where the binding constraint is access rather than skill, additional skill does not reach the constraint. The organization concludes the program was weak, when the more likely problem was that the conditions did not allow people to apply it.

Adjacent measures

Most organizations already run instruments that appear to cover this ground. They do not, and the distinction is worth being exact about.

Engagement

Engagement, at its core, indicates investment. It describes how strongly a person is attached to their work and their employer, and how much discretionary effort they are prepared to offer. It is a sound instrument and it is consistently associated with performance. But willingness and capability under changed conditions are separate properties. Someone can be entirely willing to go into a difficult quarter and still be unable to operate effectively once inside it. Engagement indicates who is invested. People readiness indicates what they can currently bring to bear.

Culture

Culture is the set of norms a group has settled into. It describes what is typical for that group over time. People readiness describes what is available now, which can sit well below what is typical when the group is under load. A strong culture raises the ceiling. It does not guarantee that a team can reach that ceiling this quarter.

Readiness for change

Readiness for change is the nearest neighbor, and the most useful contrast. Organizational readiness for change asks whether a group is collectively committed to a specific change and believes it has the collective capability to implement it. It is tied to a named initiative. People readiness is not tied to any particular initiative. It asks what a person can currently access and apply, whatever is being asked of them.

Wellbeing

Wellbeing describes a person's psychological and physical condition. It overlaps with people readiness and measures something different. Wellbeing asks how a person is. People readiness asks what they can currently do.

Recognition, access, and execution

The capacity is not a single thing. It resolves into three requirements, and it can fail at any one of them while the other two remain intact.

Recognition. Whether a person perceives what the situation actually requires. Someone who misreads the moment cannot respond to it, however capable they are.

Access. Whether they can reach their capability once they have recognized the need. This is the requirement people readiness is built to make visible.

Execution. Whether recognition and access translate into behavior. Not merely knowing what to do or intending to do it, but actually doing it.

These three do not hold equally. Across the assessments we have run at TPRC, the same directional pattern recurs: recognition scores highest, access lower, and execution lower again. A person perceives more than they can reach, and reaches more than they act on. The distance between the three is not a rounding error. It is the practical size of the problem, and it explains why two teams with comparable skill produce different results. The skills are equivalent. What differs is how much of that skill survives the conditions.

What the capacity is composed of

People readiness resolves into four dimensions. They are not traits. They are patterns of behavior observable in how people work, and each can be developed.

Self-awareness.

Self-awareness. Recognizing your own patterns and how they influence your decisions. Without it, people operate on autopilot, unaware that their internal state is driving their choices.

Communication and connecting.

Communication and connecting. Sharing information, processing difficulty, and staying open under pressure. This is what converts individual awareness into collective action.

Interpersonal effectiveness.

Interpersonal effectiveness. Sustaining collaboration under real conditions, particularly where perspectives differ or the stakes are high.

Growth mindset.

Growth mindset. Whether a person holds that both their skills and their capacity can develop, and that a difficult situation can produce a better outcome than the one preceding it. This shapes whether someone treats an unfamiliar demand as something they can grow into, or as evidence that their range is fixed. It is also what makes the other three worth developing, since a person who believes their range is fixed has no reason to extend it.

These four are not a separate list from the conditions described earlier. They are what those conditions act on. Self-awareness is what allows a person to notice that their working model has stopped matching what is in front of them. Communication and connecting often begins to withdraw when something personally important is at stake. Interpersonal effectiveness is what holds a team together while its routines are being rebuilt. Growth mindset shapes whether the disruption is read as something that can be learned through, or as evidence that one's range is fixed.

None of these is exotic. What makes them consequential is that they are the first to give way when the environment destabilizes, and the ones organizations rarely examine directly.

People readiness is a state, not a trait

A team can be ready in March and depleted by June, with the same people in the same roles. What changed was not who they were or what they knew. It was the demands placed on them and the order in which those demands arrived.

A new executive takes over a division. A platform goes live before the training has settled. A strategy is revised two months into its execution. Each of these acts on the condition of a team, and the effects tend to accumulate rather than resolve. Occasionally a well-handled change leaves a team with more capacity than it had before. More often the effects run the other way, and they compound quietly enough that nobody registers them until delivery slips.

The consequence is that people readiness cannot be established once and then treated as known. An assessment taken at the start of a program describes a condition that has usually moved by the point at which it becomes decisive. This is the property that most separates people readiness from the measures it gets confused with, and it is why it has to be read repeatedly rather than profiled once.

How people readiness shapes the outcome

When people cannot reach their capability under pressure, the behavior that results looks like resistance. They go quiet. They wait to be told. They raise problems without proposing solutions. They complete the training and change nothing.

Organizations read this as an attitude problem and respond accordingly, with more communication, stronger mandates, more pressure. Where those responses add load without reaching its source, access narrows further.

But a good deal of what gets recorded as resistance was never an attitude. It was capability that could not be reached.

This pattern is well documented. Staw, Sandelands, and Dutton described it in 1981 as the threat-rigidity effect: individuals, groups and organizations facing perceived threat restrict their information processing and constrict control, becoming more rigid at precisely the point where flexibility would serve them better. The finding has been examined and extended across four decades of organizational research. Related work on attentional scope and cognitive flexibility points in the same direction, with threat and anxiety narrowing the range of responses a person considers.

None of this accounts for every form of resistance, and it would be wrong to suggest that it does. People also resist because they disagree with the direction, because they distrust the process, because incentives pull against it, or because they are right and the change is a poor one. But where the capability is demonstrably present and its application deteriorates anyway, an access problem is the explanation least likely to be examined.

A plan can be strategically sound and still underdeliver because the conditions required to execute it were not in place. That is the variable organizations are least equipped to see.

What becomes possible when it is visible

An organization that can read this variable stops making three expensive mistakes. It stops treating an access problem as an attitude problem, and therefore stops applying pressure at the moment pressure makes matters worse. It stops commissioning training against a constraint that training does not address. And it can establish, before committing to a program, which parts of the organization are currently in a position to deliver it and which are not.

None of that requires a better plan. It requires knowing something about the people executing the plan that most organizations have never had a way to see.

Skill is what people can do. People readiness is whether they can reach it when it matters. Significant change is often won or lost in the distance between those two sentences.