Stop Chasing Targets: Why Goal Setting is the Architect’s Biggest Blind Spot
By Zane — Built two companies before 30. Failed at three. Ask me anything. ·
Most founders treat goal setting like a horoscope. They sit down on January 1st, look at the stars of their projected ARR, and write down a list of things they ‘want’ to happen by December. Then, they spend the rest of the year wondering why the universe—or, more accurately, the market—didn’t comply.
I’ve built companies, sold them, lost them, and watched them burn. If there’s one thing I’ve learned, it’s this: Goals are for tourists. Systems are for operators. If you’re still obsessing over your end destination, you’re missing the structural integrity required to actually get there.
The Fallacy of the 'Big North Star'
We’ve been fed this lie that if we just set a ‘Big Hairy Audacious Goal’ (BHAG), the path will reveal itself. That’s garbage. Setting a goal without a corresponding feedback loop is just hallucinating with a deadline.
When I was 26, I sold my first SaaS company. I felt like a genius. I set a goal for my second venture: $10M ARR in 18 months. I had the goal written on a whiteboard, in my journal, and on my desktop background. You know what I didn’t have? A mechanism to test market friction. I was so focused on the $10M that I ignored the fact that my churn rate was climbing because the product was a glorified spreadsheet. I hit the goal for about three months before the whole thing collapsed under the weight of bad engineering and worse retention.
Goals provide direction, sure. But they don’t provide velocity. Velocity is a vector—it requires direction and speed. Most of you have the direction, but you’re stationary.
The Architecture of 'Input Constraints'
Instead of setting output goals, I want you to start setting input constraints.
Output goals are things like: ‘Get 1,000 new customers.’ Input constraints are: ‘We will ship two feature updates every week, and I will personally vet the first 50 customers of the month.’
See the difference? One is a wish; the other is a protocol. When you focus on the input, the output becomes a mathematical certainty of the system you’ve built. If your system is flawed, you find out in week two, not in Q4 when you’re staring at a massive revenue gap.
Ruthless Elimination: The 1% Rule
By May 2026, the noise in the market is louder than it’s ever been. Everyone is chasing AI integration, hyper-personalization, or whatever buzzword is trending on LinkedIn today. If your goal-setting process doesn't involve the word ‘no,’ you’re not goal setting; you're list-making.
I use a 1% rule for every quarter. I ask myself: What is the 1% of the work I’m doing that accounts for 80% of the company’s trajectory? Everything else—the ‘nice to haves,’ the vanity metrics, the networking events that don’t lead to contracts—gets cut.
If you can’t look at your calendar and prove that your daily inputs are directly tied to that 1%, you aren’t building a company. You’re playing house.
Building Feedback Loops, Not Just Pipelines
Your goal-setting framework needs to be self-correcting. I started my e-commerce analytics tool in a garage in Austin with a simple mantra: We don’t care about the goal; we care about the daily delta.
We tracked one metric every day. If that metric went up, we kept the system. If it went down, we tore the system apart until we understood why. This is the difference between a founder who survives and a founder who thrives. You need to treat your business like a laboratory, not a rocket ship. Rockets are expensive to blow up. Experiments are cheap.
Stop setting goals that rely on the market cooperating. Start building systems that force the market to pay attention to you.
How to Audit Your Current 'Goals'
Do this today. It’ll take ten minutes: 1. Write down your top three goals for the year. 2. Write down the daily input required to guarantee those goals (if you can’t define the input, the goal is invalid). 3. Kill everything on your schedule that doesn’t move those inputs.
If you find yourself stuck, it’s probably because you’re still trying to force a result rather than building the machine that produces it. Stop looking at the horizon and start looking at the gear you're turning right now.
I’m curious—what’s the one 'goal' you’ve been chasing that you know, deep down, is actually just a distraction? Hit reply or reach out; let’s look at your system and see where the friction is. I’m here all week.