I’ve watched talented engineering teams burn out not from working too hard, but from working without direction. The pattern is always the same: leadership announces a new strategic pivot every quarter, teams scramble to adjust, morale craters, and your best people start updating their LinkedIn profiles.
The problem isn’t the changes themselves. It’s that without a guiding vision, every shift feels like a complete reversal rather than a necessary course correction.
Sailing Toward Something
Here’s what I’ve come to realize: engineering teams need a north star. Not a rigid plan, but a compelling direction to sail toward. It doesn’t actually matter if we ever reach it—in fact, the best visions are grand enough that we never fully arrive.
What matters is that when we tack the boat left or right to catch the wind, everyone understands we’re still heading in the same direction.
I’ve seen this work. One team I led had a simple vision: “Make our platform so intuitive that customers never need to call support.” Was it achievable? Probably not completely. But when we needed to shift from our planned feature work to fix a confusing workflow, nobody complained about the pivot. They saw it as adjusting our course to stay true to the vision.
Contrast that with another organization where the strategy changed with the seasons. One quarter we were “mobile-first,” the next we were “enterprise-focused,” then suddenly we were “AI-driven.” Each shift made perfect sense in isolation—market conditions change, competitors move, opportunities emerge. But without a unifying vision, these weren’t course corrections. They were 180-degree turns that left everyone disoriented.
The Burnout Pattern
The demoralization follows a predictable path. First comes confusion: “Wait, I thought we were building X?” Then comes frustration as work gets shelved or abandoned. Finally comes cynicism: “Why bother investing in this? They’ll change their minds again next quarter.”
Engineers don’t burn out from hard problems. They burn out from pointless work. And nothing feels more pointless than building something that gets discarded because leadership changed direction before you could finish.
I’ve been in those retrospectives where teams try to make sense of the chaos. Someone always asks, “What’s our actual strategy?” The answer is usually some variation of “respond to market demands” or “stay agile.” Which sounds reasonable until you realize it’s code for “we don’t actually know where we’re going.”
What a Real Vision Provides
A genuine north star does something powerful: it transforms apparent contradictions into coherent movement.
When you’re sailing, tacking back and forth across the wind looks chaotic if you don’t know the destination. But with a clear endpoint, those zig-zag movements make perfect sense. You’re not changing direction—you’re adjusting your approach to work with current conditions.
The same applies to engineering strategy. With a strong vision, you can:
- Prioritize without politics: “Does this move us toward our north star?” becomes the deciding question, not “Which executive shouted loudest?”
- Embrace tactical flexibility: Market shifts don’t require strategy rewrites, just different paths toward the same destination
- Maintain psychological safety: People can invest in their work knowing it serves a stable purpose, even if implementation details shift
- Attract and retain talent: Engineers want to build toward something meaningful, not just execute random feature requests
The vision doesn’t need to be revolutionary. It needs to be clear, compelling, and stable enough to orient around.
The Grand Vision Advantage
Here’s the counterintuitive part: the more ambitious the vision, the more room you have for tactical changes.
If your vision is “ship these five features this quarter,” any deviation feels like failure. But if your vision is “fundamentally change how developers deploy infrastructure,” suddenly you have tremendous flexibility in how you get there. Pivoting from one approach to another doesn’t mean abandoning the vision—it’s just trying a different route up the mountain.
I’ve noticed the best engineering leaders articulate visions that are ambitious enough to be enduring but specific enough to guide decisions. Not “be the best in our industry” (meaningless) or “increase customer satisfaction by 15%” (a metric, not a vision), but something like “make complex systems accessible to generalist developers” or “eliminate the operational burden of running our software.”
These kinds of visions can sustain years of work. They survive market changes, technology shifts, and organizational evolution. They give teams something to navigate by when everything else is uncertain.
What This Demands from Leadership
Creating and maintaining a north star isn’t a one-time exercise. It requires:
Consistent communication: The vision needs to be reinforced constantly, especially when making tactical changes that might seem contradictory to people who don’t see the bigger picture.
Authentic commitment: You can’t change the vision every time a competitor releases something or a board member has a new idea. The whole point is stability.
Translation work: Help teams connect their daily work to the broader vision. When someone’s debugging a frustrating issue, they need to understand how that connects to where you’re sailing.
Saying no: The hardest part of having a vision is declining good opportunities that don’t align with it. That’s also what makes the vision credible.
I’ve seen leaders struggle with this because it feels limiting. They want to keep all options open, respond to every opportunity, chase every trend. But that’s precisely what creates the pivot exhaustion that destroys teams.
The Alternative to Pivoting
Without a vision, every change is a pivot. With a vision, changes are adjustments.
I remember working with a team that had spent three years trying to “modernize the platform.” They’d started and stopped four different rewrites, each time with a new technology stack that promised to solve all their problems. The engineers were exhausted and cynical.
When new leadership arrived, they did something different. Instead of announcing another technology choice, they articulated a vision: “Make our platform architecture invisible to product teams so they can ship features without infrastructure work.”
Suddenly, the question wasn’t “Should we use Kubernetes?” but “Does Kubernetes help product teams ship without thinking about infrastructure?” The technology choice became a means to an end, not the end itself. And when they later shifted some workloads to serverless, it didn’t feel like abandoning Kubernetes—it felt like finding a better tool for the vision.
Why We Avoid This
If visions are so valuable, why don’t more organizations have them?
The honest answer: because articulating a genuine vision is hard work that forces uncomfortable trade-offs. It means:
- Choosing a direction when you’d rather keep all options open
- Committing to something that might turn out to be wrong
- Being accountable for a clear outcome rather than hiding behind vague platitudes
- Saying no to things that might be valuable but don’t serve the vision
It’s much easier to stay flexible, respond to market signals, and change direction whenever something shinier appears. That approach feels agile and responsive. What it actually creates is chaos.
Finding Your North Star
I’m not suggesting every team needs some grand, world-changing mission. But every team needs to know what they’re building toward and why it matters.
Maybe your north star is “give our sales team the data they need without engineering bottlenecks.” Maybe it’s “make our API so well-documented that integration takes hours, not weeks.” Maybe it’s “handle 10x our current load without adding operations overhead.”
The specifics matter less than having something stable to orient around. Something that survives quarterly planning cycles and organizational changes. Something that makes tactical adjustments feel like progress instead of pivots.
Because when you’re sailing toward something clear, tacking back and forth isn’t confusing—it’s exactly what you’re supposed to do to reach your destination.
What’s your team’s north star? If you had to articulate it right now, could you? And more importantly, would everyone on your team give the same answer?
Share your thoughts on LinkedIn - I’m curious about how different teams think about vision and direction.
#Engineering #Leadership #Strategy #Vision #Management