AVEVV It: What to Do When a Good Employee Stops Performing
You have a problem on your team, and it has a name.
Six months ago this person was one of your best. Now deadlines slip. Work comes back needing a second pass. Two people on the team have quietly started routing around them. Nothing has been said out loud, but everyone has noticed, including you.
Most leaders do one of two things. They wait, hoping it self-corrects. Or they schedule a hard conversation, deliver it, and are surprised when nothing changes.
There is a third option. Run it through the operating system.
AVEVV® is five disciplines in a deliberate order: Accountability, Vision, Execution, Vulnerability, Values. Each one makes the next one possible. Behind each discipline sit twenty observable behaviors, and when you turn those behaviors into questions and ask them of yourself, honestly, before you ask anything of the employee, the problem usually looks different than it did.
This is what we mean by "AVEVV it." Here is what it looks like on this problem.
Accountability: own your part first
The first discipline is not about holding the employee accountable. It is about the standard you set for yourself. Start there.
Did I set clear expectations, or did I assume they were understood?
Did I clarify ownership and roles, or is this person carrying work that was never explicitly theirs?
Have I measured promised versus delivered, or am I working from an impression?
Did I correct course quickly when results first fell short, or did I let it run for months?
Have I ensured this person has the resources to succeed?
Have I removed the obstacles in their way, or have they become excuses I'm now blaming them for?
Am I protecting their capacity and focus, or have I been the one loading them up?
Answer those and one of two things is true. Either you find a gap that is yours, and you now know where the conversation starts. Or you confirm the standard was clear, the resources were there, and the miss belongs to them. Both outcomes are progress. Neither is available if you skip this step.
Vision: can they see where this goes?
People sustain effort for work they understand. They do not sustain it for work that has lost its reason. When a strong performer fades, the connection to purpose is often the first thing that went.
Have I connected their daily work to a larger purpose, or has it become a list?
Have I explained why the work matters, recently, in words they would repeat?
Do they know what success looks like in their role right now?
Are my priorities unmistakably clear to them, or are they guessing which fire matters?
Have I reinforced the destination repeatedly, or once, at their onboarding?
Have I sought their perspective on where the work is going, or only reported mine?
If the honest answer is that the "why" has gone quiet, you are not looking at a motivation problem. You are looking at a direction problem, and it is yours to fix.
Execution: what is actually happening between decisions?
Execution failures are almost never about effort. They are about ownership that is unclear, commitments that are invisible, and no rhythm that keeps work on track. Look at the mechanics before you look at the person.
Have I prioritized what matters most, or does everything on their plate carry the same weight?
Is progress visible, to them and to me, or do I find out at the deadline?
Do we hold a regular operating review, or do we talk when something breaks?
Have I delegated effectively, with authority, or just assigned tasks?
Have I made the difficult trade-offs, or have I passed them down as "figure it out"?
Am I solving problems before they grow, or discovering them after?
Very often the answer here is a missing rhythm. The person is not failing to execute. They are executing without a system, and the system is your job.
Vulnerability: is it safe to tell you the truth?
Now the conversation. Before you have it, be honest about the conditions you have created for it.
Have I invited honest feedback from this person, and acted on it when it was hard to hear?
Do I listen to understand, or to defend?
Do I ask questions before I give answers?
Have I named the uncomfortable truth directly, or hinted at it and hoped?
Have I made it safe for them to admit a mistake, or a struggle, without it becoming a career calculation?
Have I shared, appropriately, when I have been in the same place?
If someone on your team is slipping and has not told you why, that is information about the environment, not just about them. The conversation you are about to have will go exactly as well as the trust you built before it. Open it with a question, not a verdict. "Something has changed in the last six months. I want to understand it before I do anything about it." Then be quiet.
Values: what does this decision say about you?
Every leader eventually has to decide what to do about a person who is not performing. How you decide is watched by everyone.
Am I treating this person with dignity, whatever the outcome?
Am I keeping the commitments I made to them, even now that it is inconvenient?
Am I giving credit for what they did well, publicly, and handling the shortfall privately?
Am I developing this person, or using them until they are used up?
Would I be comfortable if the whole team saw exactly how I handled this?
Am I making the decision that creates long-term value, or the one that ends my discomfort fastest?
Values are not the closing statement. They are the test of whether the first four disciplines were real. A leader who owns their part, restores direction, rebuilds the rhythm, opens the conversation, and then acts with integrity has done the work. The outcome, whether the person recovers or moves on, will be one the team respects.
The order is deliberate
Accountability creates ownership. Vision gives that ownership direction. Execution turns direction into results. Vulnerability keeps execution adaptive. Values ensure the results last.
Skip Accountability and you deliver a verdict you have not earned. Skip Vision and you fix a symptom. Skip Execution and you get a good conversation followed by the same month. Skip Vulnerability and you never learn what was actually wrong. Skip Values and you may solve the problem and lose the team.
This is not a checklist to run once. It is an operating system to run every time. The next problem will be different. The questions will not be.
Try it on your own situation. Type "AVEVV it" into any AI and describe the problem. Or run the full diagnostic at avevv.com/avevvit.
AVEVV® is The Leadership Operating System™ — five disciplines leaders run daily inside their real work, practiced through the AVEVV Performance Continuum™ and measured through the AVEVV Performance Dashboard™.