You finish the quarter having done almost everything you said you'd do. The v2 shipped. The senior engineer started. The pricing page got rebuilt. You look at the list and most of it is crossed off. You look at the objective and you're not appreciably closer to it than you were three months ago.
This is a specific kind of failure, and it's not the one most goal-tracking writing addresses. It isn't a discipline problem. You executed. It isn't a planning problem in the usual sense, either. The plan you wrote got done. The problem is that the plan was made entirely of one kind of thing, and the kind of thing it was made of can't, on its own, produce the outcome you wanted.
Actions and habits do different work
Most plans contain two structurally different kinds of work, and most people treat them as one.
Actions are finite. They have a definite end. Launch the new landing page. Run the strength block before race week. Close the Series A. You either complete them or you don't, and once they're done they're done. Actions are how plans visibly progress. They're satisfying. They tick off.
Habits are recurring. They don't complete, they accumulate. Train four times a week. Make ten outbound calls a day. Sleep before midnight. Their value is in the compounding, not in any individual instance. A habit you did for three weeks and dropped is worth almost nothing.
The two do different jobs. Actions move you in steps. Habits hold the conditions that make those steps work. A plan needs both, and a plan that contains only one is almost always missing the half that's harder to see.
This is also where OKRs run out of road. OKRs are good at defining the outcome and how you'll measure it. They don't tell you anything about how you'll deliver it. The key results are the destination, not the plan, and the gap between objective and delivery is exactly where actions and habits live. A well-written OKR can sit alongside a plan that won't produce it, and nothing in the OKR itself will tell you.
What a habit-light plan looks like in execution
Take the fitness version. You decide to run a sub-90 half marathon in October. You build a plan around it. Sign up for the race. Pick a training block. Buy proper shoes. Book a sports massage every six weeks. Do a tune-up 10k in August. Each of these is a real, finite action, and each of them gets done.
What's not on the list, or what's on the list as a single line that doesn't get reviewed, is the four runs a week and the protein target the whole thing depends on. The runs aren't an action. They don't complete. There's no week where you finish running. Hitting your protein target isn't an action either. It's a daily behaviour with no satisfying endpoint. Both are the foundation the actions sit on, and both are easy to leave implicit because they don't tick off.
By August you've done all the action items. The shoes are good. The tune-up is booked. But you ran three times one week, twice another, missed a week to travel, and your easy pace hasn't moved since June. You also under-ate on protein for most of the block and the strength work didn't hold. The plan executed. The conditions underneath it didn't get built. The race goes the way it was always going to.
The founder version is the same shape. You set a £2m ARR target for the year. The plan is a list of moves. Launch the new tier. Hire a second AE. Run a partner campaign in Q2. Redo the website. Attend two conferences. By October most of it has happened, and you can describe in detail what you shipped.
The thing that wasn't on the list, or was on it in a way that didn't get tracked, is the daily outbound and the weekly pipeline review. The behaviours that produce the top of the funnel the actions are meant to convert. They're recurring. They don't complete. So they got delegated to "we should be doing more of this" and never got a weekly target. The actions all landed on a funnel that wasn't being fed, and the year ends with a deck full of completed initiatives and a revenue line that doesn't match.
In both cases the visible work is fine. Someone reviewing the plan at year end would say it was executed. What failed isn't the execution. It's that the plan was structurally incomplete from the start, and the incompleteness was invisible because what was missing wasn't a missing action. It was a missing kind of thing.
Why habits go missing
Habits get left out of plans for a reason. They're worse to plan with.
Actions feel like progress when you write them down. Each one represents a decision made, a thing committed to. The list grows and the plan feels more solid. Habits do the opposite. Adding a habit to a plan is admitting you're going to do something boring, repeatedly, for a long time, with no individual instance feeling like an accomplishment. The plan doesn't feel more solid for containing them. It feels more demanding.
There's also a measurement problem. Actions are binary. They're done or they aren't. Habits are continuous. Did you train enough this week? Enough is doing a lot of work in that sentence. Without a specific weekly target the question can't be answered, and without an answer the habit isn't really being tracked, it's being hoped for. Most plans end up hoping for their habits.
When the habits get cut
Watch what happens to a plan under pressure. A week gets busy. Something urgent lands. You look at what you committed to and ask, honestly, what has to give. The actions tend to survive. They have deadlines. Other people are waiting on them. Skipping one has a visible cost.
The habits go first. Missing a single training run doesn't visibly cost anything. Missing a day of outbound doesn't change today's revenue. Each individual instance is small enough to absorb, which is exactly the property that makes habits valuable in aggregate and easy to drop one at a time. You don't decide to abandon the habit. You decide, this once, that the action takes priority, and you do that for eight weeks in a row.
This is the loop that quietly empties out the half of the plan that was holding the conditions. Each individual call is defensible. The cumulative effect is the plan you executed and the outcome that didn't arrive.
What a complete plan actually contains
A plan isn't complete when every action is listed. It's complete when both layers are present and each is doing its job.
The actions are the discrete moves. They have owners and end dates and they get crossed off. The habits are the recurring behaviours those moves depend on. They have weekly targets and they get reviewed for accumulation, not completion. Neither half makes sense without the other. The actions without the habits land on conditions that weren't built. The habits without the actions produce consistency without arrival.
The test of a plan is not whether you could execute every item on it. It's whether, if you did execute every item on it, the outcome would actually follow. Most plans fail that test, and they fail it in the same place: the actions are there, the habits are implicit, and the gap between effort and outcome shows up in October.