Why It’s So Hard to Start With the End in Mind?
Everyone has heard the advice. Start with the end in mind. Picture where you want to land, then work backward. It sounds obvious once someone says it out loud — and almost nobody actually does it.
I don’t think that’s a discipline problem. I think it’s unnatural. Visualising an end state and building toward it goes against how we default to thinking, deciding, and acting. Here’s why.
We treat thinking as a delay, not as work
Most environments — teams, families, our own heads — reward visible motion. Someone typing, building, shipping, fixing looks like they’re doing something. Someone sitting still, turning an outcome over in their mind, looks like they’re stalling.
So thinking gets quietly relabelled as time-waste. Not by policy — nobody writes this down — but by how we react to it. The person mapping out what things should look like in three years gets the polite nod. The person taking the next visible step gets called a doer. Over time, we learn which one gets rewarded, and we stop doing the other.
We start with what we already have, and mistake it for the whole field
Here’s the quieter trap. When we do sit down to plan, we don’t start from the end — we start from our inventory. The software we already pay for. The developer we already have access to. The budget line that’s already approved. These become the boundary of what feels possible, and because that boundary is the only thing we can actually see, we treat it as if it’s the only thing that exists.
This isn’t laziness. It’s a genuine bias — what we can see, we assume is all there is. And because we’re acting on something real and tangible, we feel high confidence that we’re making a decision. We’re not. We’re arranging what’s already in front of us and calling it a plan.
Think about how often a project starts with “here’s what we’ve got, what can we build with it” instead of “here’s what we actually want, what would it take to get there.” The first question feels responsible. The second feels like it belongs to someone else — someone with more time, more authority, more room to dream. It rarely does. It just requires sitting with not knowing yet, which is exactly the discomfort the first question lets you skip.
Imagination gets treated as impractical, so it gets cut
The third piece is the one people least want to admit: imagination is genuinely rare, and where it does show up, it’s often waved off by the people who consider themselves practical. Cookie-cutter techniques — templates, standard playbooks, the way it was done last time — get valued because they’re efficient, fast, and cheap to justify. Imagination doesn’t have a line item. It can’t be measured before it’s tried. So in any room where efficiency and speed are what get scored, imagination is the first thing to go quiet.
Why the end still matters, even though it’s uncomfortable to hold
None of this means starting with what you have is wrong — you have to build with real material eventually. The problem is when it becomes the starting point instead of the constraint. A house built from “what materials are in the shed” is a shed. A house built from “what do we actually want to live in” and then sourcing the materials is a house. Same difference shows up in a career built around your current job description versus one built around a role you’d have to grow into that doesn’t exist yet where you are. Same difference shows up in any organisation where the plan quietly becomes “what can our current team and tools deliver” instead of “what outcome are we actually protecting, and does our team and tooling still serve it.”
Starting with the end in mind means tolerating the discomfort of not yet knowing how to get there, resisting the urge to call motion a decision, and defending imagination in a room that will keep asking you to be practical instead.
What would you actually build if you stopped starting from what you already have?
