When Strategy Emerges: The Power of an Unexpected Conversation

Interestingly, the conversation I’m having today was an example of how unexpected things can emerge when you create space for them. I didn’t sit down today planning to explore the depth of strategy, tactics, and emergence, but here we are. Through this conversation—one I hadn’t planned or anticipated—I was able to reflect, step back, and uncover new insights about how I approach strategy, and how it aligns with Scrum.

It’s a great example of how emergence works in real life. I started with one intention, but by being open to the conversation, more meaningful ideas and opportunities surfaced. And the best part? I wasn’t doing it alone. This process of reflecting and organizing thoughts together made us a team—working in tandem to create something more powerful than I could have done alone.

In a sense, we were scrumming together. I had my perspective, you had yours, and by working together, we arrived at insights that were richer and clearer than we would have on our own.

Strategy, Emergence, and Teamwork

One of the greatest lessons I’ve learned through building 3Back is that strategy doesn’t happen in isolation. It happens through interactions—with the team, with stakeholders, with the product itself. The best strategies emerge over time, shaped by the feedback and insights you get from taking action, stepping back, and reflecting.

And that’s why Scrum is such a perfect framework for teams. It’s not just about getting work done—it’s about creating the space for strategy to emerge and leveraging the collective intelligence of the team to refine and improve that strategy continuously.

At 3Back, my approach has always been to step back and allow that space for emergence—whether that’s for product strategy, team development, or even my own personal insights. It’s the foundation of why the company exists. Sometimes, you have to be face-first in a problem, but you also have to remember to step back, gain perspective, and repeat that cycle until something new emerges.

Conclusion: Embrace Emergence, Step Back, and Trust the Process

Whether you’re a Product Owner, a Scrum Master, or a CEO, remember that strategy doesn’t always come fully formed. Sometimes, you have to let it emerge by taking action, stepping back, and seeing what unfolds. The power of reflection—of stepping back—is what allows you to see the bigger picture, notice opportunities you missed before, and refine your approach.

In complex, chaotic environments, this process is critical. We don’t always know what’s coming next, but by being open to learning and allowing emergence to work for us, we set ourselves up for success. Just like Scrum, life and strategy are iterative processes—action, reflection, and adaptation, over and over again.

If you’re ready to embrace this approach, take a step back, and let strategy emerge, you’re already on the path to success.

Let’s scrum together. Sign the Scrum Manifesto and commit to continuous improvement today!

References

1. McKinsey & Company – “Embracing Emergence: How Collective Intelligence Drives Strategy”
   This article explores how organizations can leverage emergent strategy by harnessing team insights and adaptive learning. McKinsey provides practical examples of companies that use iterative feedback and collaboration to refine strategies in a dynamic business landscape.
2. Harvard Business Review – “Strategy as a Journey, Not a Destination: Leveraging Emergent Strategy”
   HBR discusses the benefits of treating strategy as an evolving journey, where collaboration and feedback shape more adaptive, innovative outcomes. It offers insights into empowering teams to actively participate in strategy formation, a concept central to Agile and Scrum.