Nobody has a Drive problem at the project kickoff.
The initiative is new, the room is full, the slides are good. Motivation at this stage is almost free—it comes with the novelty and the attention, and it tells you nothing about the leader or the team.
Drive is what's left of that motivation at month eighteen, when the initiative is harder than expected, the team is tired, and the early results are mixed. That is the only reading of the dimension that counts, because that is the only moment it gets tested.
Why it hides
Of the ten dimensions, Drive is the one high performers misread longest. Here's the mechanism.
A leader with depleted Drive still produces. The habits are there, the calendar is full, the output arrives. From the outside, and often from the inside, nothing looks wrong. What's gone is the connection between the work and its reason, and since output doesn't require that connection in the short run, the deficit remains invisible.
Then one of two things happens. Either the leader notices a flatness they can't name and attributes it to something else like sleep, workload, the team, or someone close to them notices first. Neither is a good way to find out.
The three states, for this dimension
Valley is running on obligation. You can describe what you're doing in detail and struggle to say why it matters. The work hasn't stopped; the reason has.
Plateau is committed but rarely connected. You know the why when asked, but you don't feel it in the Tuesday afternoon version of the work. This is where most sustained leadership lives, and it holds for a long time.
Peak is clear on the reason most days. Not every day; nobody is. But the connection between the task in front of you and what you actually care about remains intact and available.
Notice that none of these is about effort. A leader at Valley in Drive is often working harder than one at Peak. That's part of why it hides.
The honest read
One question, written down, once:
I'm doing this because _________
Finish it without stopping to edit. Then look at what you wrote.
If the sentence ends in a reason you'd give a stranger—the role, the title, the expectation—that's useful information. If it ends in something you'd only say to yourself, that's useful too. If you can't finish it, don't treat that as a failure. Treat it as the clearest reading you've had of this dimension in a while.
What to do with a Valley here
Not more effort. That's the instinct, and it's the one that got you here.
Two things, in order. First, reconnect the daily work to the actual reason, if a reason still exists, which usually means naming, specifically, who the work is for and what changes for them. Second, if no reason survives that exercise, say so plainly to yourself. A Valley in Drive that has no reason underneath it isn't a conditioning problem. It's information about whether this is still your climb.
Most of the time, it is. The reason went quiet; it didn't leave. But you can't find that out by pushing harder.
Where are you now? Fifty questions, about eight minutes.
