Readiness Inventorying identifies the actions consequential work depends upon and tests whether readiness is actually available. It reveals where readiness is strong, conditional, or constrained.
In the first part of a two part blog post set, I suggested that employee engagement may become more useful when understood as an inventory of readiness to act. That reframing leads fairly quickly to another question, because readiness is not one thing and it certainly cannot be understood by asking employees whether they feel generally prepared for whatever the organization happens to ask of them next.
People are ready for different kinds of action in different ways. A team may be very ready to maintain dependable service while being much less ready to challenge an established practice. Employees may genuinely want to collaborate but find themselves navigating systems and handoffs that make collaboration surprisingly difficult. A manager may have the experience and judgment required to make a sound decision, yet work inside an environment where independent judgment is encouraged in theory and routinely reversed in practice.
This is where the idea of a Readiness Inventory begins to earn its place. Its purpose is not to create another sprawling employee survey, nor to find a more elaborate way of producing an engagement score. It is to identify the forms of readiness upon which consequential work depends, and then determine whether those forms of readiness are actually available.
That sounds reasonably straightforward, which is usually the moment when someone becomes tempted to add twelve dimensions, four maturity levels and a diagram with arrows travelling in a circle. There may be a simpler route.
The first question is not how ready people are. It is what they may need to be ready for.
That distinction is important because readiness only has meaning when connected to something consequential. An organization preparing for a significant systems change may need people to learn new ways of working, adapt established routines, exercise judgment in unfamiliar circumstances and ask for help before small problems become expensive ones. An organization facing succession may depend more heavily on people sharing knowledge, coordinating dependencies and becoming comfortable exercising judgment that previously sat elsewhere.
Another organization may be under sustained operational pressure, where success depends partly upon people maintaining important standards even when targets, workloads or deadlines make shortcuts tempting. The forms of readiness change because the work changes.
A useful Readiness Inventory therefore begins with a broad possibility set. We might consider readiness to deliver reliably, prioritize competing demands, exercise judgment, adapt, learn, raise concerns, offer dissent, experiment, coordinate, collaborate, share knowledge or protect important standards when pressure rises.
The point is not to assess all of them. The point is to avoid deciding, from the comfort of a meeting room, that the only forms of readiness that matter happen to be the first three that occurred to us.
From that broader field, the organization can identify perhaps five to eight forms of readiness that genuinely matter to the work ahead. That limit is useful. An organization that discovers seventeen immediate readiness priorities may have learned something important, although perhaps not what it expected to learn.
Once the important forms of readiness have been identified, the question changes. Can the organization reasonably rely upon them?
Consider something apparently simple such as readiness to raise concerns. We could ask employees whether they feel comfortable speaking up, collect the answers and move along. The difficulty is that “comfortable speaking up” contains several very different possibilities.
An employee may understand perfectly well when a concern should be raised and believe strongly that doing so is part of responsible work. They may have the knowledge and confidence to explain the concern clearly. At the same time, they may believe that raising it will damage a relationship with their manager, or that previous concerns have disappeared into a procedural mist from which nothing useful ever emerged.
Calling that employee simply “ready” or “not ready” tells us very little.
The more useful inquiry is into the conditions that make readiness available.
Five conditions appear to provide a practical anatomy:
The distinctions are important because superficially similar performance problems can arise for completely different reasons. If people do not understand what is expected, clearer direction may help. If they understand and value the action but lack the necessary skill or capacity, the response may involve training, resources, practice or workload. If they are capable but not enabled, the problem may sit in authority, process, leadership behaviour or organizational norms. If all of those conditions look reasonably strong but people have learned that their action rarely produces anything useful, another invitation to “get involved” is unlikely to restore confidence.
This is the point at which readiness becomes more than an interesting idea. It helps the organization diagnose before it prescribes.
There is an obvious temptation to take the five conditions, average them together and produce an overall Readiness Score.
Organizations do like a number. Numbers fit neatly into dashboards, accept arrows gracefully and can usually be persuaded to turn green.
The trouble is that averaging may conceal the very thing we need to understand.
Imagine that employees score strongly on understanding, value and capability for offering dissent, but weakly on whether the organization enables dissent and whether they believe dissent will influence anything. An average might produce something resembling “moderate readiness.” That is technically tidy and managerially unhelpful.
The more useful conclusion is that personal readiness exists, but organizational conditions are constraining access to it.
That distinction matters because readiness should not be treated as something stored inside the employee. It arises from the relationship between the person, the action and the environment in which the action must occur.
The five conditions should therefore be read as a profile rather than collapsed prematurely into a single score. From that profile, the organization can interpret whether a particular readiness appears broadly available, conditional upon certain circumstances, constrained by the surrounding system, depleted through experience, or simply uncertain.
The numbers help us see the pattern. They should not be allowed to erase it.
The practical output of this work can be a Readiness Ledger.
For each readiness priority, the ledger records the pattern across the five conditions, the interpreted state of readiness and the most important factor supporting or constraining it. It creates a concise view of what the organization appears able to rely upon and where there is reason for caution.
One organization might discover that readiness to deliver reliably is strong, while readiness to collaborate across boundaries is conditional because coordination remains cumbersome. Employees may be ready to exercise judgment but constrained by narrow decision authority. They may readily offer ideas while having considerably less confidence that worthwhile ideas survive the journey from suggestion to decision.
Those are quite different findings, and they lead toward quite different responses.
If understanding is weak, clarify. If capability is weak, build it. If capacity is the problem, adding training may simply consume more of the resource already in short supply. If enablement is weak, examine the surrounding system. If people no longer expect their action to matter, credibility is unlikely to be rebuilt by asking them to believe more enthusiastically.
The purpose of the ledger is not to create a more sophisticated dashboard. It is to improve the choices made after the diagnosis.
There is an important boundary around this work. A Readiness Inventory should never become an instrument for asking how much more an organization can extract from its employees. Low readiness is not automatically an employee deficiency, and strong readiness is not an invitation to consume it without regard for consequence.
Sometimes people are quite reasonably unready.
They may be unwilling to absorb another priority because no existing work has been removed. They may hesitate to act because responsibility has been delegated without authority. They may resist a proposed change because they can see effects that have not yet entered leadership's field of view. They may decline to take a shortcut because an important professional, ethical or safety standard matters more than this month's target.
Those are not necessarily signs of disengagement. They may be valuable information about the organization itself.
The purpose of readiness inventorying is therefore not to manufacture readiness wherever leadership wants it. It is to understand whether the forms of readiness required for consequential work are genuinely present, what conditions affect them, and what the organization may need to change if it hopes to rely upon them.
That brings us some distance from the familiar question, “How engaged are our employees?”
A more consequential question is whether people are ready for the work that matters next — and whether the organization has created the conditions that allow that readiness to become action.
When you work with Guiding Star, you ignite real transformation — in your people, your teams, and your impact. Let's spark light, warmth, and lasting excellence for your customers, donors, and stakeholders.
Reach out today. Let's build something brilliant together.
.png){kind=logo}