There’s a version of this post where I name the advice. But I think the specific content matters less than the pattern — and the pattern shows up everywhere.
Here’s how it goes.
You’re early in your career. You don’t know what you don’t know. Someone with more experience tells you something that clicks. A principle. A heuristic. A way of seeing a problem.
You use it. It works. You use it again. It works again.
Eventually it becomes reflex. You stop thinking about it — you just apply it. This is how experienced people think, you tell yourself. They have frameworks. They have instincts. They know.
And then at some point — usually around the time you start being responsible for things that don’t fit neatly into the frameworks — the advice stops working.
Not because it was wrong. Because you grew past the context where it was right.
How advice becomes reflex
Most advice comes embedded with a context the adviser doesn’t specify.
“Move fast” works when the cost of being slow is higher than the cost of being wrong. “Default to yes” works when your main risk is missing opportunities. “Ship it” works when you’re underdelivering.
The advice is correct. But the context is doing all the work.
What happens is this: the advice works so well that you stop checking whether the context still holds. The heuristic becomes the strategy. The example becomes the rule. You optimize for the advice being true rather than for the original outcome the advice was meant to produce.
This is how good advice becomes bad advice without ever changing.
The version of you that learned it
Here’s the uncomfortable part: the advice usually was right for the version of you that received it.
The person who told you “move fast” was right — you needed to stop being cautious and start being decisive. The person who told you “default to yes” was right — you needed to stop saying no out of fear. The person who told you “ship it” was right — you needed to stop polishing and start delivering.
You internalized it. You grew. You got to a place where that particular constraint no longer applied.
But the advice is still running. And now it’s running against a different problem.
What actually changed
The issue isn’t the advice. The issue is that you’ve changed the problem.
Early-stage work is usually about moving fast and building momentum. The risk is slowness, perfectionism, hesitation.
Later-stage work is often about precision, about knowing which things don’t scale, about protecting things that are actually valuable from being disrupted by the velocity you’re capable of generating.
Same person. Same advice. Different problem.
The instinct that made you good at building is now making you bad at sustaining.
The cost of being consistent
What makes this hard to see is that the advice keeps working in small ways. Moving fast still produces outputs. Defaulting to yes still builds relationships. Shipping still gets things out the door.
But you’re not optimizing for those things anymore. You’re optimizing for not being the person who “overthinks” or “plays it safe” or “doesn’t ship.”
You’ve turned a means into an end.
And once that happens, you start measuring success by how well you’re following the framework rather than by what’s actually happening.
What to do instead
I’m not sure “stop listening to advice” is useful. Most people err in the other direction — too much input, too many frameworks, too much optimization for other people’s playbooks.
The move I’ve found useful is narrower: hold your advice at arm’s length and ask what problem it was meant to solve.
Not “is this advice still true?” — that’s too abstract. “Is the problem I’m facing the problem this was built for?”
The person who told you to move fast was solving a specific problem in a specific context. You probably don’t remember that context. You just remember the rule.
Go back. Not to the advice. To the problem.
Odds are, you’ve moved far enough from that problem that the solution doesn’t fit anymore. You just can’t see it yet — because you stopped asking the question a long time ago.