Open Mob Programming: Unlocking Collaboration Through Collective Coding

Rethinking Collaboration in Software Development 

At L’Occitane, we believe the best solutions emerge when we build software together. That’s why our team practices daily remote mob programming—leveraging collective intelligence to make development more transparent, efficient, and engaging. But we didn’t want to keep this experience to ourselves. 

We asked: what if we opened our doors and invited others in? 

That’s how the Open Mob initiative was born—a weekly session where colleagues from across the company join us in live collaborative coding. And this isn’t just about writing code. It’s about breaking silos, spreading best practices, and strengthening a shared sense of ownership in the software we create.  

What Happens in an Open Mob Session? 

Each week, participants from different teams step into our world of collective coding. The format is simple: 

🔹 2-hour live coding session 

🔹 Guest participants take the wheel—only they write the code 

🔹 Our team navigates—guiding, reviewing, and discussing implementation in real time 

This structure ensures that guests are fully engaged, actively learning by doing rather than just observing. The shift in roles challenges both guests and our team: they gain hands-on experience, and we refine our ability to articulate ideas, mentor, and challenge our own assumptions. 

And participants quickly realize : it’s not just about coding—it’s about thinking critically, collaborating effectively, and learning together. 

And let’s be honest—there’s something incredibly satisfying about leaving a session knowing that a tiny piece of your work is now part of a real, running application. 

A special thanks to Woody Zuill, author of Software Teaming, whose work on mob programming and collaboration helped inspire this initiative.  

Breaking Silos, Sharing Knowledge 

One of the most interesting benefits of Open Mob has been its ability to tear down walls between teams. Developers, product managers, and even non-technical colleagues bring fresh perspectives to the table. 

💡 For non-developers, it's an eye-opening dive into software development—demystifying the process and highlighting the importance of clear communication, naming conventions, and structured thinking. 

🛠️ For developers, it's a chance to practice new techniques, like test-driven development (TDD), in a safe, collaborative setting. Many leave eager to introduce these approaches into their own teams. 

📊 For leadership, it’s a game-changer. Initially, some worry that mob programming looks like one person working while four watch. By the end, they see the reality: real-time code review, shared problem-solving, and continuous learning in action—a far more effective model than traditional siloed work. 

 The Hidden Benefits of Open Mob 

Beyond technical skills and cross-team collaboration, Open Mob programming has led to some surprising and valuable takeaways for participants and our team alike: 

🎯 Sharpening Communication & Teaching Skills – Guiding someone unfamiliar with the codebase forces us to be clearer, more structured, and more patient. It’s made us better at explaining concepts and mentoring others. 

🛠 Strengthening Our Own Practices – Every session is an opportunity to challenge our habits. When newcomers ask “Why do you do it this way?” we either reinforce our choices or realize there's a better approach. 

🔍 Spotting Hidden Complexity in Our Codebase – When external participants struggle to navigate our code, it’s a signal: what seems obvious to us might not be as intuitive as we think. These moments have helped us refactor pain points and improve our documentation. 

💡 Building Confidence for Non-Developers – For many product managers and designers, contributing to code feels out of reach. Open Mob has shown them that they can engage in technical discussions and even influence implementation decisions. 

These unexpected wins make Open Mob more than just a collaborative coding practice—it’s a continuous feedback loop that helps us refine our development process, improve knowledge-sharing, and grow as a team. 

What’s Next ? 

While this article highlights the benefits of Open Mob programming, there’s a lot more beneath the surface—especially when it comes to making it work in practice. 

Running Open Mob isn’t just about inviting people and coding together. Behind the scenes, we face real challenges: 

🔹 Finding the right time – How do you fit Open Mob into a busy sprint without disrupting ongoing work? 

🔹 Tooling & logistics – What setup ensures a smooth remote collaboration experience? 

🔹 Preparation & guidance – How much do you plan in advance? Should the session be fully structured, or is it better to keep it flexible? 

🔹 Adapting to different skill levels – How do you guide someone unfamiliar with the codebase without overwhelming them? 

Each of these challenges has forced us to experiment, adapt, and refine our approach. And the truth is, we’re still learning. 

That’s why we don’t just want to write about Open Mob—we want to talk about it. 🎤 

We’d love to share these insights in a broader conversation. 

If you’re organizing a conference or looking for fresh perspectives on collaboration in software development, we’d be happy to bring our experience to the stage. 

There’s so much more to explore—from the real-world challenges of Open Mob to the lessons we’ve learned about teamwork, tooling, and knowledge-sharing across teams. 

Interested in diving deeper? Let’s connect! 🚀