From Drift to Drive: Helping Teams Move Towards Strategic Outcomes

Teams rarely drift because they’re lazy. They drift because no one’s holding the map up anymore.

It’s easy to get swept along in the rhythm of delivery — sprint after sprint, ticket after ticket — and mistake movement for direction. The team feels busy, work is getting done, but nothing really moves.

As leaders, our job isn’t just to keep the oars moving. It’s to help the team learn how to steer.

The Missing Middle

Most organisations have a strategy. It usually lives in a tidy deck somewhere — full of arrows, pillars, and inspiring words.

But by the time it reaches teams, it’s often been translated into tasks and deadlines. The bigger why gets lost somewhere between the PowerPoint and the pull request.

That’s when the drifting starts. Teams deliver work that looks productive but doesn’t necessarily take them — or the organisation — anywhere strategic.

Bridging that gap means helping people see not just what they’re doing, but why it matters, and how they can help shape where things go next.

Training the Compass

Awareness comes first. A team can’t steer towards a goal it can’t see. This doesn’t mean walking through a 50-slide strategy deck. It means translating the direction into something tangible:

• What are the big bets we’re making as an organisation?
• What kind of engineering maturity do we need to support them?
• Where could today’s work nudge us closer to that future?

Once people see the landscape, capability follows. Understanding strategy is one thing; applying it is another. That’s where mentoring, experimentation, and reflection turn abstract goals into something real.

Seizing Strategic Moments

When Ethan Marcotte published his book on responsive design, it changed how many of us thought about the web.

I was working on a redesign of a news website at the time. We didn’t have a mandate to “go responsive” — the term was barely known — but the idea felt important. So, we experimented. Flexible grids, fluid images, layouts that hinted at adaptability.

We never fully realised it — the project ended, and I moved on soon after — but that experience stuck. Later, when responsive design became mainstream, I felt ready. I’d already wrestled with its ideas, even clumsily, and that gave me the confidence to implement it properly the next time.

That’s how strategic awareness works. You don’t always act on it immediately, but when the moment comes, you’re prepared.

Protecting the Time

Awareness and intent only matter if there’s room to act on them. Even the most strategically minded team can’t steer if they’re rowing flat-out every day.

Part of leadership is making space — allowing the team to take that extra day to do something properly, not just quickly.

When people know they can raise a hand and say,

“While we’re here, could we take an extra day to bring this closer to our architectural goal?” and get a yes instead of a sigh, that’s when strategic thinking starts to take hold.

From Awareness to Ownership

Over time, something changes. The team starts spotting strategic opportunities before you do. They connect ideas across domains, link short-term effort to long-term outcomes, and begin shaping the direction rather than just following it.

That’s when you know you’ve shifted from drift to drive.

Final Bit

Strategy doesn’t live in off-sites or slide decks. It lives in the small, everyday decisions people make — how they name things, what they refactor, what they question.

Your job isn’t to hand the team a map. It’s to teach them how to read the terrain, to recognise when they’re close to something that matters, and to trust them to take the turn.

Stay aware, stay curious — and whatever you do, don’t just drift.