Aware, Capable, Able, Willing (ACAW): The Foundation of Any Real Evaluation

A few weeks into a new role, I was running early one-on-ones with all of the teams I’d inherited. One of the engineering managers pulled me aside and said “I don’t think Sarah is going to make it. Her work is weak, she’s doing fewer points than the others, all of which I’ve been mentally tracking.”

A few days later, I sat down with Sarah herself. She told me, unprompted, that she was excited about her upcoming promotion. She’d been the team’s top performer for two quarters.

Both of these statements were said with full sincerity. Working from the same information, they reached opposite conclusions.

I’ve seen a version of this on every team I’ve been hired into. Two people each holding a confident and incompatible read of the same employee. Some version of this is happening right now in every organization you can name.

Every evaluation I’ve ever seen comes down to four key questions. Most reviewers ask one of them. Some ask two. Almost none ask all four, in order, with the right action paired to each answer. These four questions came out of years of experience trying to understand the “Sarah” problem. And once I had them, the discrepancies stopped being mysterious.

The four questions are:

• Is this person aware of what they are supposed to be doing?
• Is this person capable of what they are supposed to be doing?
• Is this person able to do what they are supposed to be doing?
• Is this person willing to do what they are supposed to be doing?

If you only ask one, or two, or three of these questions, you create an incomplete picture of an employee’s performance AND the manager’s responsibility. Reviews are not just a metric on subordinates’ performance but a measure of leadership’s abilities.

The rest of this article walks through what the questions are, how to use them, and why the order is important.

Question 1: Aware

Is this person aware of what they’re supposed to be doing?

Before you can ask this question honestly, something has to be true: the responsibilities have to exist in writing, and both you and the person being evaluated have to have seen them. A job description. A team charter. A list of assigned tasks. The format does not matter. What matters is that there’s a shared artifact, written before the review period started, that both of you can point to.

If that artifact does not exist, the question isn’t failing. You are. The conversation stops, you build the artifact together, and you come back at a later time. Skipping this is how managers end up evaluating against a private model the employee never had access to. Sarah’s manager was tracking points. Sarah was tracking something else. Whatever the standard actually was, it wasn’t written down and it wasn’t shared. The awareness check had already failed before either of them sat down.

With the artifact in place, the question becomes specific. So do the three that follow. Each of the four questions is asked per responsibility, not in general: are they aware of this responsibility, and this one, and this one. Walk the list. Yes or no on each.

If they aren’t aware of an item, the action is to inform. That sounds obvious until you watch how often it gets skipped. The number of “performance problems” that turn out to be “I didn’t know I was supposed to do that” is higher than most managers want to admit.

If they are aware, move to the next question.

Question 2: Capable

Is this person capable of what they’re supposed to be doing?

Capable means they have the skill, the knowledge, the credential, or the experience to do the work. Not “could they figure it out eventually,” but “could they do it now if they sat down to try.”

This is the question most evaluations conflate with awareness. Someone misses a deliverable, and the manager files it as “they didn’t get it done.” But there are at least three reasons that might be true: they didn’t know they were supposed to, they don’t have the skill, or something else is in the way. Until you’ve split these out, you don’t have an evaluation. You have an assumption.

If the answer to this question is no, the action is to educate or train. That’s on you. Hiring someone for a role and then noticing they don’t have the skill isn’t a performance issue. It’s a development issue. The same applies if the role has evolved past the skill set the person was originally hired for. Roles change. People are not expected to acquire new skills by osmosis.

There’s an edge case worth naming. If the person can’t be trained to capability in a reasonable timeframe, that’s a different conversation, and it belongs at the end of the four questions, not the middle.

If they are capable, move to the next question.

Question 3: Able

Is this person able to do what they’re supposed to be doing?

Capable was about whether they have the skill. Able is about whether the conditions exist for them to use that skill right now. It’s the question most evaluation systems skip, and it’s where most of the actual managerial work lives.

Examples of capable-but-not-able: a senior engineer with the skill to ship a feature but no access to the codebase because IT is two weeks behind on provisioning. A product manager capable of running a launch but blocked by a legal review nobody’s pushing forward. A sales lead capable of closing the quarter but with a territory that just got redrawn. A team member capable of focused work but in the middle of a family crisis they haven’t told you about.

In every one of these cases, scoring the person low on performance is wrong. They are not the problem. The conditions are. Filing it as a performance issue is what produces “good people leave bad managers” stories. The good person was able yesterday and isn’t able today, and nothing about them changed. Something about the environment changed, and the manager didn’t see it.

The action when the answer is no: ask what’s in the way, then remove it. This is genuinely the manager’s job. The person being evaluated cannot remove most of their own obstacles, because most obstacles sit one or two levels of authority above them. That is precisely why the obstacle is an obstacle in the first place.

Some obstacles are personal and the manager can’t remove them. But the manager can still adjust. Reduce scope. Reset deadlines. Move responsibilities temporarily. A manager who answers “able? no” with “well that’s their problem” has misunderstood their role.

If they are able, move to the next question.

Question 4: Willing

Is this person willing to do what they’re supposed to be doing?

By the time you reach this question, three things are true. The person knows what they’re supposed to do. They have the skill to do it. The conditions exist for them to do it. If the work still isn’t happening, you’ve reached the question most managers wish they could ask first.

Willing is the hardest category to evaluate cleanly. Managers often mistake disagreement, burnout, or distrust for unwillingness. By the time you reach this question, the remaining issue isn’t capability or conditions. It’s whether the person still wants to participate in the role as currently defined. That sounds harsh, and it can be. But it’s also genuinely the diagnosis after the first three questions land in the right place. Without going through them first, you don’t actually know that this is what’s happening. You just suspect it.

The action when the answer is no is to find out why, and decide whether the situation can be changed. Sometimes people aren’t willing because the role has shifted into something they didn’t sign up for, and the right move is to redefine the role or move them to one that fits. Sometimes the team has changed and the person feels like a stranger in their own job. Sometimes they’re burned out. Sometimes a competing offer has shifted their calculus and they’re already halfway out the door.

Most of these have manager-side responses available. Reset the role. Reset the team. Take the burnout seriously. Have the honest counter-offer conversation. Each one of these requires the manager to actually take action. And to do it before the situation calcifies into “they’re just not motivated.”

A note on incentives. It is fair to use current employment itself as the incentive. If the person is aware, capable, able, and choosing not to do the job, the relationship between them and the role has already broken. Saying it out loud is sometimes the clearest information they’ve gotten in months: continued employment depends on doing the role. This is not threatening. It’s the honest version of an unstated assumption everyone is already operating under. Use it carefully, and only after the first three questions are clean. Do not over-promise other incentives just to manufacture motivation.

If the answer to the Willing question becomes yes, the situation moves forward. If it stays no after a real conversation, you have your answer about whether this role and this person fit. That conversation belongs in the open, not buried in manager-to-HR backchannels.

A Deeper Framework

The four questions, in order, provide a clear path for employer and employee in performance reviews.

• Aware: if no, inform.
• Capable: if no, educate or train.
• Able: if no, find the obstacle and remove or adjust.
• Willing: if no, find out why, then decide.

To ease adoption, you can use this structure at the role level. Evaluate the employee’s tasks and responsibilities all at once: is this employee able to complete all of their assigned tasks? This also allows for better communication between managers, HR, and leadership about how an employee is performing. For example, an aware, capable, able, but unwilling employee is a different problem from an unaware, capable, able, willing one.

For larger, more foundational impact, you can ask these questions for each assigned task or responsibility. This more granular approach requires extra work from the manager, but it creates a tighter feedback loop and isolates issues at a micro level.

Finding and addressing issues is one of the most important things a leader does. Imagine the impact when a leader can address each employee’s needs individually while maintaining a sense of consistency, or “fairness”, across the team.

Closing

Most evaluation frameworks tell you what to look at or ask. Aware, Capable, Able, Willing tells you what you need to know.

Before you bring the four questions to your next review at work, try them somewhere low-stakes. With a coworker. With a friend. Even with yourself on a goal you keep missing. The same pattern shows up almost anywhere responsibility and evaluation overlap.

When you come back to it at work, the four questions are not a checklist. They are a position. The position says that an employee’s performance is also a measure of the manager’s work. If you ask only the questions that put the responsibility on the employee, you’ll get evaluations that miss the most important parts of what’s actually happening.

Glossary

• ACAW: Aware, Capable, Able, Willing. The four-question evaluation framework this article describes.
• HR: Human Resources.
• IT: Information Technology.
• SLT: Senior Leadership Team.