From Strategy to Delivery: The Triple Track One Team Way

Why Strategy, Discovery, and Delivery Only Work When You Move as One

Jun 12, 2025

Modern digital product teams often operate with the best intentions — running experiments, shipping fast, and setting bold strategic goals. But too often, these efforts happen in isolation. Strategy stays in executive decks. Discovery lives in siloed research. Delivery becomes just a backlog of tickets.

This article introduces the Triple Track One Team model — a practical approach to unifying strategy, discovery, and delivery within a single, cross-functional team. Drawing on two decades of experience and the influence of practices like Lean Inception, Team OKRs, and Continuous Discovery and Delivery, I’ll show how real alignment transforms not only how teams work, but the outcomes they achieve.

Why Alignment Matters

After more than twenty years working with digital product teams, I’ve seen one challenge surface again and again: the disconnect between strategy, discovery, and delivery.

Yes, we’ve become good at agile rituals, rapid delivery, and experimentation. But too often, those efforts still happen in silos. Strategy gets lost in translation. Discovery lacks a clear connection to business goals. Delivery becomes motion without direction.

The problem isn’t lack of effort — it’s lack of alignment. Not just aligning processes, but aligning people: business, product, and tech. When these functions move together as one unified team, that’s when real impact happens.

Triple Track: Continuous Business Strategy, Discovery & Delivery

That’s what Triple Track One Team is all about — a model that helps teams align continuously and move with purpose. In this article, I’ll show you how it works, and how Team OKRs, Continuous Discovery, Continuous Delivery, and Lean Inception bring it to life.

The Evolution: From Dual Track to Triple Track One Team

Back in 2006, I had the privilege of working closely with Jeff Patton. At the time, we were in Silicon Valley, immersed in product thinking, agile delivery, and the practical challenges of making great software. Those were years of great evolution in how we built software at scale — shifting from rigid plans to iterative learning, from siloed roles to cross-functional collaboration.

Around 2007, Jeff Patton and Marty Cagan — one of the foremost thinkers on product models and high-performing teams — were running a training session together. At one point, on a whiteboard, they sketched out something simple yet powerful: two tracks running in parallel — one for discovery, one for delivery.

Later, Jeff gave it a name and popularized the model: Dual Track Development.

And it resonated. The model helped product teams understand that building software wasn’t a linear process. You don’t just write requirements and throw them over the wall. You learn continuously (discovery), while you build iteratively (delivery).

But over the years, I noticed something.

Even when teams were running discovery and delivery in parallel, something was missing. Discovery efforts weren’t always connected to real business priorities. And delivery, while fast, wasn’t always focused on the most impactful outcomes. Strategy was often a slide deck, reviewed once a quarter, far removed from the day-to-day work of product teams.

That’s when I started to talk about a third track: Business Strategy. Not as a top-down directive, but as a continuous, team-owned process — guided by Team OKRs, reviewed regularly, and lived in the conversations and decisions teams make every week.

When you put all three tracks together — Business Strategy, Discovery, and Delivery — and you align them within a single, cross-functional team, you unlock something powerful. That’s what I call Triple Track One Team.

One team. Three tracks. Continuous motion. Real alignment.

Track One: Continuous Business Strategy with Team OKR

When people hear “strategy,” they often picture a top-down PowerPoint or a long-term roadmap that rarely changes. But modern digital teams need something different — something more dynamic and participatory. That’s where Team OKRs (Objectives and Key Results) come in.

Team OKRs bring strategy to the ground level. They transform vague ambitions into actionable, measurable outcomes that the team can rally around. They answer two essential questions: Where do we want to go? And how will we know we’re making progress?

Instead of waiting for annual planning cycles, teams define OKRs every quarter. This cadence keeps the strategy alive and relevant. More importantly, it keeps it close to the team — not buried in some executive doc or forgotten slide.

At the start of each cycle, the team holds a Team OKR Definition Workshop — a focused session where everyone involved in the product work comes together: product managers, engineers, designers, and relevant stakeholders. They discuss goals, challenges, and the broader context. Together, they define a clear objective and a few key results that are both ambitious and grounded. Crucially, these Team OKRs are not created in isolation — they must align with the strategic direction of the larger structure the team belongs to, whether that’s a business unit, tribe, or company-wide goal. This alignment ensures that while the team has autonomy, it’s pulling in the same direction as the broader organization.

Throughout the quarter, during team OKR check-ins and retrospectives, teams review their OKRs. They inspect what’s working, what’s not, and how their work is (or isn’t) contributing to those outcomes. This turns the OKR into more than a static document. It becomes a living guide that shapes discovery and delivery work in real-time.

It’s not just about tracking progress. It’s about shaping focus. Team OKRs create clarity and autonomy. They empower teams to say no to distractions and yes to what matters most.

And when used within the Triple Track One Team model, Team OKRs become the backbone of the Business Strategy track — continuously influencing what gets discovered and what gets delivered.

Track Two: Continuous Discovery

Discovery isn’t a phase you complete and move on from. It’s an ongoing way of working — something that helps you constantly figure out what to build and why. And how do you learn fast? You run experiments. You decide on MVP — Minimum Viable Product — to test a key assumption. Then you put it in front of users and see what happens.

That’s how you avoid building the wrong thing. You don’t need a big release to get feedback. You just need to learn — fast. And that means testing assumptions early, talking to real users, and staying curious. Prototypes, interviews, quick A/B tests — this is the daily work of discovery.

Teresa Torres really nailed this in her book on continuous discovery. She talks about weekly customer conversations, small bets, and tight feedback loops. I’ve seen this in action. When teams get into this rhythm, they make better decisions and waste less effort.

In a Triple Track One Team, discovery isn’t something one person does. It’s shared. And it’s always tied to the team’s goals. If the Team OKR is to reduce churn, discovery focuses on finding out why users leave. What’s missing? What’s confusing? What can we test to make things better?

Every piece of learning — every test, every insight — helps the delivery track focus on what really matters. And delivery feeds right back into discovery, too. When we ship something, we watch how people use it. That real data becomes the next input for discovery.

Now, there are moments when the team needs stronger alignment — when it’s time to decide what to build next and how to start. That’s when we run a Lean Inception workshop. In a few focused sessions, we align on the roadmap and the MVP. We map user journeys, brainstorm features, check assumptions, and get everything on the MVP Canvas.

It’s fast. It’s collaborative. And it really helps connect discovery and delivery with momentum and clarity.

When teams commit to continuous discovery — and pair it with continuous delivery and strategy — they build products that are not only functional, but meaningful.

Track Three: Continuous Delivery

Shipping fast isn’t enough. What matters is shipping with purpose, based on learning, aligned with strategy. That’s what Continuous Delivery is all about.

Years ago, delivering software meant big releases, long waits, and tons of coordination. Today, we work differently. We deploy small changes regularly — sometimes several times a day — and we use automation to keep things smooth, safe, and scalable.

But continuous delivery isn’t just about speed. It’s about feedback. Every release is a chance to learn from real user behavior. When combined with continuous discovery and strategy, delivery becomes a learning engine — not just a release pipeline.

In a Triple Track One Team, delivery is connected to discovery and strategy at every step. You’re not just pulling tickets from a backlog. You’re building features that tie back to validated discoveries, and those features are chosen because they help move the Team OKR forward.

This is where tools like the MVP Canvas help. During a Lean Inception, teams use it to plan and align on the minimum viable product. Then, during delivery, that canvas becomes a reference point: what are we building, for whom, and why? What's the outcome we expect?

Delivery teams use techniques like feature toggles, canary releases, and monitoring to make sure what they ship works — and to measure if it’s having the intended impact. If it doesn’t, they loop back into discovery. If it does, they keep building on it.

This tight loop — build, measure, learn — is at the heart of modern delivery. With this mindset, the team isn’t just building features — it’s delivering outcomes.

Triple Track, One Team

It’s easy to look at the three tracks — strategy, discovery, and delivery — and imagine three separate teams. But that’s not the point. In fact, that’s the trap.

The real power of Triple Track Development is when a single, cross-functional team works across all three tracks. One team. Shared purpose. Diverse skills. Everyone contributes in different ways, depending on the moment, the goal, and the problem at hand.

Maybe today the focus is discovery — validating an assumption through a quick prototype. Tomorrow it’s delivery — releasing a feature that connects to a key result. And next week it’s strategy — reviewing OKRs and deciding what outcomes to focus on next. But it’s still the same team, moving as one.

That’s why I say: Triple Track, One Team.

And it’s not theoretical. I’ve seen this in action. When a team owns its strategy (via Team OKRs), runs discovery together, and delivers continuously — everything changes. Communication improves. Prioritization becomes clearer. People feel empowered because they understand the why behind their work.

In big companies, the org chart might still show separate areas — business, product, tech. But at the team level, the work is deeply connected. Roles may vary, but the mission is shared. Alignment replaces handoffs. Collaboration replaces silos.

Still, it’s important to clarify: Triple Track Development happens at the team level. That’s where execution lives. That’s where strategy becomes action.

In smaller organizations, this kind of alignment often happens naturally. But in large organizations, it’s more complex. Hierarchy exists — and it matters. Whether you call it company, tribe, business unit, or squad — the structure is there. But the essence of Triple Track isn’t about changing the hierarchy. It’s about how teams operate within it.

Each team should align with the broader strategic direction of their business unit or tribe. But when it comes to doing the work — discovering what matters, delivering with purpose, and shaping strategy through Team OKRs — it’s that single, unified team that makes it happen.

**Not like this:** strategy, discovery, and delivery in silos, owned by different levels.

**Like this:** one cross-functional team, integrating all three tracks in a continuous flow.

Triple Track isn’t about complexity — it’s about clarity. It gives your team a model to understand how work connects across perspectives, and how to move forward together.

It’s Triple Track. It’s One Team. That’s where the magic happens.

Turning Alignment Into Action

Triple Track Development isn’t just a clever model. It’s a practical way for teams to work — with clarity, purpose, and momentum.

When you bring together continuous strategy (Team OKRs), continuous discovery (experiments, MVPs, and validated product increments), and continuous delivery (fast, feedback-driven releases), you stop guessing and start learning. You stop building blindly and start building what matters.

But it only works if the team is unified. One team, not three. Business, product, and tech pulling in the same direction — not in parallel lanes, but on a shared path. That’s where the “one team” part really matters.

Earlier, I simplified the visuals by showing each track as a separate arrow. But in practice, it feels less like three independent paths and more like something tightly woven — like a threefold cord.

Imagine you have a rope to pull something. Now, imagine two colleagues beside you, each with their own rope. Separately, you make some progress. But together — pulling the same thing with shared intent — you achieve far more.

That’s the real picture: Three areas — Business Strategy, Continuous Discovery, and Continuous Delivery — braided together. One team. Unified. Pulling together.
Like the image below:

**Triple Track, One Team: A Threefold Cord** — Business Strategy, Discovery, and Delivery woven into one unified effort.

Each strand matters:

Business Strategy gives direction and purpose.
Continuous Discovery fuels learning and insight.
Continuous Delivery turns ideas into value, quickly and reliably.

On their own, each track is powerful. But when intertwined, they become far stronger — capable of real momentum, real impact, and real alignment.

The threefold cord isn’t just a metaphor. It’s a mindset. And it’s how Triple Track Development truly comes to life..

A Personal Note: Two Decades to Simplicity

It took me more than two decades to arrive at this simple model — Triple Track One Team. Mark Twain once wrote, “I didn't have time to write a short letter, so I wrote a long one instead.” That’s exactly how I feel. I apologize for the many (and often long) articles I wrote before this one — I was still in the process of making things simpler.

I began my career as a developer. I loved building. Then I joined ThoughtWorks, where I had the privilege of working alongside Martin Fowler, Jeff Patton, Jez Humble, and many other brilliant colleagues.

Jez was at the forefront of a transformation in how we deliver software. His work helped define what we now call Continuous Delivery — deploying fast, learning fast, and changing the way software reaches users.

Jeff had a profound influence on me as well. He helped me shift from a delivery-first mindset to a more user-centered approach. That shift led me toward discovery work and, eventually, to creating Lean Inception — a method designed to align people early, validate ideas faster, and connect vision to execution.

As my work evolved from delivery to discovery, another challenge emerged: strategy. I began exploring OKRs, and at first, it didn’t quite click. But over time, I discovered the true power of Team OKRs — not as top-down mandates, but as shared objectives that teams own and revisit regularly. That was the missing link. It bridged the gap between strategy, discovery, and delivery.

Throughout the years, I’ve worked with many different teams — across startups, enterprises, and everything in between. And one thing consistently stood out: the teams that truly collaborate, that align deeply and move together, are the ones that achieve the most meaningful outcomes.

And of course, I must thank my longtime coach and mentor, Martin Fowler, who has continued to guide me — not just in how we craft software, but in how we write, communicate, and focus on what really matters.

This model didn’t come from theory. It came from the field — from workshops, experiments, setbacks, and reflections. And from writing five books focused on strategy, agility, alignment, and team collaboration.

Triple Track One Team may look simple. But behind that simplicity lies a long journey — and a deep belief: when teams align around outcomes, collaborate across disciplines, and own their work across all three tracks, they don’t just deliver features — they deliver real impact.

From Strategy to Outcomes

Discussion about this post

Ready for more?