What Are Your People Actually Ready For?

In the first part of this discussion, I argued that employee engagement may be more useful when understood as an inventory of readiness to act. That reframing immediately raises a practical problem, because readiness is not one thing and it is certainly not something that can be understood by asking employees whether they feel generally prepared for whatever comes next.

People are ready for different kinds of action in different ways. A team may be very ready to maintain dependable service and much less ready to challenge established practice. Employees may be willing to collaborate but unable to navigate the systems and handoffs that make collaboration possible. A manager may have the judgment required to make a sound decision, yet work inside an environment where independent judgment is politely encouraged and routinely reversed.

This is where the idea of a Readiness Inventory becomes useful. The aim is not to invent another giant employee survey. It is to identify the forms of readiness the organization may need, then determine whether those forms of readiness are actually available.

That sounds simple enough, which is usually the point at which consultants begin making it considerably less simple.

Start With the Work That Matters

The first step is not to ask how ready people are. It is to ask what they may need to be ready for.

That distinction matters because readiness only becomes useful when attached to consequential work. An organization preparing for a major systems change may need people ready to learn new ways of working, adapt established routines, exercise judgment under uncertainty and ask for help when things go wrong. Another organization may be facing succession, which places greater emphasis on sharing knowledge, coordinating dependencies and following through on commitments. A third may be operating under intense performance pressure and need people to uphold important standards when short-term demands begin competing with quality, safety or professional judgment. The list changes because the work changes.

A practical Readiness Inventory therefore begins with a broad possibility set. The organization considers a range of readiness forms, such as delivering reliably, prioritizing competing demands, exercising judgment, adapting ways of working, raising concerns, offering dissent, experimenting with alternatives, collaborating across boundaries, navigating friction and acting in service of customers, clients, citizens or mission.

The purpose of the list is not to declare that every organization must assess everything. Its purpose is to prevent the conversation from being limited to whatever happens to occur to the six people in the room.

From that wider set, the organization selects perhaps five to eight forms of readiness that genuinely matter to the work ahead. The number matters. If everything is important, the inventory has already become an exercise in avoiding prioritization.

Then Ask Whether Readiness Is Available

Once the important readiness objects are identified, the next task is to understand whether the organization can actually rely on them. That requires looking beneath the surface.

Take something seemingly straightforward such as readiness to raise concerns. It would be easy to ask employees whether they feel comfortable speaking up and leave it there. The problem is that such a question collapses several quite different realities into one response.

An employee may understand exactly when a concern should be raised and believe strongly that doing so is important. They may have the confidence and knowledge required to raise it clearly. Yet they may also believe that doing so will damage a relationship with a manager, or that nothing useful will happen after the concern is voiced.

The person is not simply “ready” or “not ready.” Some of the conditions are present and others are not. That is why the anatomy of readiness matters.

Five Conditions of Readiness

For any selected form of readiness, five questions help reveal whether it is genuinely available.

The first is whether people understand what is expected. Do they know what the action means in practice, when it is appropriate, and what good judgment looks like?

The second is whether they value the action. Do they see sufficient reason to do it, given its importance, legitimacy, meaning and the competing obligations already in front of them?

The third is whether they can do it. Do they have the capability, confidence, capacity, attention, resources and practical means required to act?

The fourth is whether they are enabled to do it. Do authority, norms, relationships, systems and interdependencies make the action realistically possible and reasonably safe?

The fifth is whether they expect it to matter. Do they believe that acting will receive a meaningful response and contribute to a useful consequence?

These five conditions sound deceptively simple, but they create very different diagnoses.

If people do not understand what is expected, the organization may need clearer direction. If they understand and value the action but lack capability or capacity, the issue may be training, resources or workload. If they can act but are not enabled to do so, the problem may lie in authority, leadership behaviour, processes or culture. If they believe nothing meaningful will happen after they act, the problem may be accumulated experience rather than motivation.

This is the point where a Readiness Inventory begins to earn its value. It helps distinguish between problems that may look similar from a distance but require very different responses.

Score the Anatomy, Not the Person

There is a strong temptation to turn all of this into one number. Organizations are fond of roll-ups because they make complex realities fit neatly into boxes, preferably boxes with arrows.

I would resist that.

If readiness to offer dissent scores strongly on understanding, value and capability, but weakly on enablement and expectation of consequence, an average score may suggest “moderate readiness.” That would be a fairly unhelpful conclusion.

The more useful interpretation is that personal readiness exists but organizational conditions constrain access to it.

This distinction matters. Readiness should not be treated as a trait stored somewhere inside the employee. It emerges from the interaction between the person and the conditions surrounding the work.

That suggests a different kind of output. Each readiness object is profiled across the five conditions and then interpreted as broadly available, conditional, constrained, depleted, unavailable or uncertain. The numerical ratings support that interpretation, but they do not replace it.

The Readiness Ledger

The practical result can be recorded in a Readiness Ledger. For each priority readiness object, the organization captures the pattern across the five conditions, the interpreted readiness state and the most significant constraint.

The ledger might reveal that readiness to deliver reliably is broadly available, while readiness to collaborate across boundaries is conditional because coordination systems remain weak. Readiness to exercise judgment may be constrained because employees possess capability but lack real authority. Readiness to offer ideas may appear strong until the final condition is examined, where people reveal that they do not expect their ideas to go anywhere.

The value is not in generating a more sophisticated dashboard. It is in identifying what the organization can reasonably rely upon and what it cannot.

That creates a better management conversation. If the limiting factor is understanding, communicate differently. If it is capability, build skill. If it is capacity, stop pretending another course will create more hours in the week. If it is enablement, change the system. If people no longer expect action to matter, leaders may need to rebuild credibility through visible response rather than another encouragement campaign.

The methodology therefore points toward intervention without prescribing one intervention in advance.

Readiness Is Not Compliance

There is one final guardrail worth making explicit. An organization should not use readiness inventorying to ask how much more effort it can extract from people. Low readiness is not automatically an employee deficiency, and high readiness is not an invitation to consume it carelessly.

People may reasonably be unready to support a poorly explained priority, absorb another initiative without removing existing work, or act in ways that conflict with professional judgment. In such circumstances, the absence of readiness may be useful organizational intelligence.

That is why the ledger matters. It turns engagement away from generalized positivity and toward something more operational and more honest.

The question becomes not simply whether employees are engaged, but whether the organization has access to the forms of readiness its consequential work requires.

That is a much more demanding question, but also a more useful one. It asks leaders to look not only at what they need from people, but at whether the organization has created the conditions that make that readiness possible.