The Compass You Never Handed Out: Why Intent Is the Real Cure for Scope Creep
Pushing pieces through a hole you cannot see

I keep seeing the same pattern. Teams keep pushing. Deadlines are missed. And when you ask what success looks like, nobody can really answer. Not because they disagree, but because no one ever described what success looked like.
This came back to me recently in discussions about roadmaps, and in projects where I watched the scope grow and grow. It shows up in all kinds of projects, but especially in software. And every time, the root is the same. There is no intent.
Pushing pieces through a hole you cannot see
Imagine being handed a box of shapes and a hole. You do not know whether the hole is square, round or triangular. So you push. One shape does not fit, so you try another. Someone gives feedback, so you try a third. Every attempt adds something new to the work.
That is what scope creep looks like from the inside. It is not that people are lazy or that customers are unreasonable. It is that the team is reacting, passing things through without ever stepping back to ask what shape they are trying to fit.
Now imagine the same situation with intent. The intent is to match the shape. Suddenly the behaviour changes. You stop pushing and start looking. You use your peripheral vision. You navigate, you sense, you adjust.
Intent is the compass
Intent is the compass for whatever you are trying to achieve. It does not tell you every step. It tells you which way is north.
Without a compass, every piece of feedback feels like a new destination. With a compass, feedback becomes course correction. That single difference is what separates a team that converges from a team that drifts.
Two scenarios, one outcome
In my experience there are two different ways a team ends up without intent.
The first is absent intent. It is missing all the way through the stack. Leadership has not described it, product has not described it, and the team has not asked for it. Everyone is reactive, and everyone is busy.
The second is trapped intent. This is common in micromanaged teams. The intent actually exists. It sits with whoever is defining the goal, the scope and the target. It just never reaches the team. The team receives tasks without the why.
Two different causes. A very similar outcome. A team pushing pieces without knowing the shape.
It is worth pausing here and asking yourself: which one am I in?
A belief worth letting go of
Some people believe that feeling micromanaged is a sign of growth. I do not buy that. Of course, the feeling can be misread. Sometimes what feels like micromanagement is really someone asking for traction, and that is a fair ask. But being handed tasks without intent is not growth. It is a team being kept away from the compass.
So if it feels like micromanagement, pause before you react. Notice whether it is an ask for traction or actual micromanagement. The test is intent. If there is an intent behind the ask, it is about traction, and you still have room to choose how you get there. If there are only tasks and check-ins and no why, that is micromanagement. And if you cannot see the intent, ask for it before you decide. It might simply be trapped somewhere above you.
Intent is shared. It can be a leadership gap, but it can also be a team gap. Anyone, at any level, can be the one who stops and asks: what does success look like?
The detail illusion
There is another belief I see often. The belief that to hit the target, you need a lot of detail.
It is the opposite. When you have the intent, you need less detail. A team that knows why can fill the gaps themselves, and they will make good calls in places no specification ever anticipated.
So when I see people asking for more and more detail, I treat it as a symptom. The ask for detail is very often a signal that intent is missing.
What to do about it
When the ask comes to me, I answer with the why instead. More often than not, the question changes, or disappears.
When I am advising on a project and see the symptom, I help surface the intent using whatever fits the context. Sometimes that is OKRs, where the objective carries the intent and the key results describe what success looks like. I have written about how OKRs lose their power when they become structure without direction in The OKR Illusion, Why Structure Without Direction Is Just Noise.
Other times it is about making the roadmap or backlog tell a story, so the why is visible in the work itself. More on that in Telling the Story Through your Sprint Backlog, and The Backlog Illusion.
And sometimes it is about how we write initiatives and specifications, so they carry intent rather than just requirements. See How I Apply NLP to shift the way PRDs and specifications Influence Outcomes, and From Features to Transformation.
Hand out the compass
Scope creep is rarely a scope problem. It is a compass problem.
So here is my invitation. The next time someone asks you for more detail, pause. Offer the why first. Then notice what happens. You might find that the shape of the hole was never the mystery. Nobody had simply described it yet.

