The operations review ran forty-five minutes. Every agenda item got covered. Every owner reported. Every number was either in range or had a credible explanation for why it wasn't. Toward the end, someone walked through a project update that sounded familiar — and it should have, because it was nearly the same update from six weeks earlier, minus a few percentage points of progress. Somebody said "great, let's keep pushing on that," and the room nodded, and the meeting ended on time.
You closed your laptop. Nothing was wrong. Nothing was moving either. And you could not point to a single thing the team would be doing differently in ninety days because of that hour.
If you have sat in that meeting — and if you lead a team of any size, you have — you already know the feeling I am describing. It is not frustration, exactly. It is something quieter. The team is present, the work is getting done, the updates are credible, and still you walk out with the distinct sense that you just spent an hour tending a garden that is not growing. I have run those meetings. For a long time I assumed the feeling was a personal problem — that I was not pushing hard enough, or not asking the right questions. Most of the senior leaders I work with eventually ask some version of the same question: Is this just what leadership feels like? Or am I doing something wrong? Neither, as it turns out. There is a name for what you are feeling, and it is not your fault.
The name is maintenance mode, and once you can see it, you cannot unsee it.
Maintenance mode does not look like failure. That is what makes it so difficult to name. It looks like competence. It looks like a team that shows up, handles its responsibilities, and does not create problems. From one level up, it can look like everything is fine.
The signals are in the language. Listen for the verbs in your next three meetings. Maintenance conversations are full of preservation verbs: keep, hold, stay on top of, continue, maintain, monitor. Momentum conversations use different ones: build, test, try, redesign, change. Maintenance commitments are about completion — we will get it done. Momentum commitments are about capability — we will figure out how to do it in a way we could not three months ago. And notice the risk in the room: in maintenance mode, nobody is proposing anything that might not work. Everything is defensible. That is the tell.
We are not avoiding the bigger conversation because we are lazy. We are avoiding it because raising it costs something. Nobody wants to be the person who disturbs the meeting. And there is an unwritten rule in most organizations that if you name the real problem, you have just volunteered to solve it — you should have the answer, the path, the recommendation. Easier, in the moment, to stay with the tackle-able problem and let the ambiguous one sit where it is sitting.
Which brings us to the part most leadership writing gets wrong.
The drift into maintenance is not a performance problem. It is the default human condition. Under pressure — time pressure, scrutiny, ambiguity, fatigue — we retreat toward what we can control. We work the tackle-able problem instead of the ambiguous one. We manage the list instead of asking whether it is the right list. We build the Gantt chart because the Gantt chart can be built. Meanwhile the real question — the one that would actually change the trajectory — sits unnamed at the edge of the table, and everyone in the room feels it and nobody brings it up.
That is not weakness. That is wiring. It is what capable, conscientious humans do when the environment rewards legibility and penalizes ambiguity. Your best people are not stuck in maintenance because they stopped trying. They are stuck because gravity is doing exactly what gravity does, and nothing in the operating cadence around them is actively pulling in a different direction.
Three forces make the pull as strong as it is. All of them are signs of normal leadership operating under normal conditions.
The drift you are feeling is a structural condition. The way out is not to work harder inside the operating model you already have. The way out is a different operating model for your conversations.
If drift is the default, then the leader's only real job is to work against it.
To keep people climbing. And not climbing for the sake of climbing — climbing toward something that actually changes the view. From up there you can see the next market. The next capability. The thing that, once built, makes everything below it different. From where the team sits today, that view does not exist. The leader is the one who has to insist on the climb.
Maintenance is inertia. It does not reverse itself. The only thing that moves a team out of it is a leader who actively pushes — and the primary tool for that push is the conversation. The verbs change. The commitments change. The questions change.
A leader I worked with last year changed exactly two questions. At the end of every status update in his staff meeting, instead of "great, let's keep that moving," she started asking two things. The first was what will be true in thirty days that is not true today? The second, reserved for the bigger projects, was harder: if we hit every one of these specs, what did we actually win?
The first few weeks, people froze. Some were annoyed — they had come to report progress, not defend direction. By week six, the quality of what came into his staff meeting had changed. People were building their updates around different questions, which meant they were doing different thinking all week long to prepare. He did not add a meeting. She did not roll out a program. She changed what she asked at the end of a sentence, and the operating system started bending.
That is the order of operations. Notice the language. Change the language. Watch the room change around it.
If you want to see your own maintenance language on the page, here is a starting point for this week. Pull transcripts or detailed notes from two or three recent meetings that bothered you — the ones where nothing was wrong but nothing was moving. Paste them into the AI tool of your choice (see a link to my prompt below). Ask it: "Am I leading for maintenance or for momentum? Look at the verbs I use, the commitments I accept, and whether I close loops on growth or on status. Be specific. Quote me back to myself where the pattern is clearest."
Be ready for the answer. The point of the exercise is not the diagnosis. The point is that you cannot change a pattern you cannot hear.
Maintenance mode is not a verdict on your leadership. It is what every human system does when no one is actively leading against it. Every team on earth is drifting toward it right now, including yours, including mine. The question is not whether your team has drifted. The question is whether you are the one pulling them back to the climb.
The operations review ran forty-five minutes. Every agenda item got covered. Every owner reported. Every number was either in range or had a credible explanation for why it wasn't. Toward the end, someone walked through a project update that sounded familiar — and it should have, because it was nearly the same update from six weeks earlier, minus a few percentage points of progress. Somebody said "great, let's keep pushing on that," and the room nodded, and the meeting ended on time.
You closed your laptop. Nothing was wrong. Nothing was moving either. And you could not point to a single thing the team would be doing differently in ninety days because of that hour.
If you have sat in that meeting — and if you lead a team of any size, you have — you already know the feeling I am describing. It is not frustration, exactly. It is something quieter. The team is present, the work is getting done, the updates are credible, and still you walk out with the distinct sense that you just spent an hour tending a garden that is not growing. I have run those meetings. For a long time I assumed the feeling was a personal problem — that I was not pushing hard enough, or not asking the right questions. Most of the senior leaders I work with eventually ask some version of the same question: Is this just what leadership feels like? Or am I doing something wrong? Neither, as it turns out. There is a name for what you are feeling, and it is not your fault.
The name is maintenance mode, and once you can see it, you cannot unsee it.
Maintenance mode does not look like failure. That is what makes it so difficult to name. It looks like competence. It looks like a team that shows up, handles its responsibilities, and does not create problems. From one level up, it can look like everything is fine.
The signals are in the language. Listen for the verbs in your next three meetings. Maintenance conversations are full of preservation verbs: keep, hold, stay on top of, continue, maintain, monitor. Momentum conversations use different ones: build, test, try, redesign, change. Maintenance commitments are about completion — we will get it done. Momentum commitments are about capability — we will figure out how to do it in a way we could not three months ago. And notice the risk in the room: in maintenance mode, nobody is proposing anything that might not work. Everything is defensible. That is the tell.
We are not avoiding the bigger conversation because we are lazy. We are avoiding it because raising it costs something. Nobody wants to be the person who disturbs the meeting. And there is an unwritten rule in most organizations that if you name the real problem, you have just volunteered to solve it — you should have the answer, the path, the recommendation. Easier, in the moment, to stay with the tackle-able problem and let the ambiguous one sit where it is sitting.
Which brings us to the part most leadership writing gets wrong.
The drift into maintenance is not a performance problem. It is the default human condition. Under pressure — time pressure, scrutiny, ambiguity, fatigue — we retreat toward what we can control. We work the tackle-able problem instead of the ambiguous one. We manage the list instead of asking whether it is the right list. We build the Gantt chart because the Gantt chart can be built. Meanwhile the real question — the one that would actually change the trajectory — sits unnamed at the edge of the table, and everyone in the room feels it and nobody brings it up.
That is not weakness. That is wiring. It is what capable, conscientious humans do when the environment rewards legibility and penalizes ambiguity. Your best people are not stuck in maintenance because they stopped trying. They are stuck because gravity is doing exactly what gravity does, and nothing in the operating cadence around them is actively pulling in a different direction.
Three forces make the pull as strong as it is. All of them are signs of normal leadership operating under normal conditions.
The drift you are feeling is a structural condition. The way out is not to work harder inside the operating model you already have. The way out is a different operating model for your conversations.
If drift is the default, then the leader's only real job is to work against it.
To keep people climbing. And not climbing for the sake of climbing — climbing toward something that actually changes the view. From up there you can see the next market. The next capability. The thing that, once built, makes everything below it different. From where the team sits today, that view does not exist. The leader is the one who has to insist on the climb.
Maintenance is inertia. It does not reverse itself. The only thing that moves a team out of it is a leader who actively pushes — and the primary tool for that push is the conversation. The verbs change. The commitments change. The questions change.
A leader I worked with last year changed exactly two questions. At the end of every status update in his staff meeting, instead of "great, let's keep that moving," she started asking two things. The first was what will be true in thirty days that is not true today? The second, reserved for the bigger projects, was harder: if we hit every one of these specs, what did we actually win?
The first few weeks, people froze. Some were annoyed — they had come to report progress, not defend direction. By week six, the quality of what came into his staff meeting had changed. People were building their updates around different questions, which meant they were doing different thinking all week long to prepare. He did not add a meeting. She did not roll out a program. She changed what she asked at the end of a sentence, and the operating system started bending.
That is the order of operations. Notice the language. Change the language. Watch the room change around it.
If you want to see your own maintenance language on the page, here is a starting point for this week. Pull transcripts or detailed notes from two or three recent meetings that bothered you — the ones where nothing was wrong but nothing was moving. Paste them into the AI tool of your choice (see a link to my prompt below). Ask it: "Am I leading for maintenance or for momentum? Look at the verbs I use, the commitments I accept, and whether I close loops on growth or on status. Be specific. Quote me back to myself where the pattern is clearest."
Be ready for the answer. The point of the exercise is not the diagnosis. The point is that you cannot change a pattern you cannot hear.
Maintenance mode is not a verdict on your leadership. It is what every human system does when no one is actively leading against it. Every team on earth is drifting toward it right now, including yours, including mine. The question is not whether your team has drifted. The question is whether you are the one pulling them back to the climb.
Start with the next meeting. Listen for the verbs. See you next week.