Why Co-creating and Mobbing Matter
Co-creating and mobbing bring the whole team together around a single goal or problem, unlocking benefits such as:- Real-time idea sharing
- Continuous learning and upskilling
- Collective institutional knowledge
- Improved efficiency and automation
Successful co-creating or mobbing sessions require clear goals, a shared workspace (physical or virtual), and rotating roles to keep everyone engaged.
Defining Co-creating vs. Mobbing
Co-creating
Each team member works from their own workstation, contributing code, diagrams, or documentation into a shared repo or platform. This approach lets individuals iterate simultaneously while maintaining collective visibility.Mobbing
One person “drives” at a central system—often projected for the group—while everyone else observes, reviews, and suggests improvements. The driver implements the team’s consensus in real time.
Pair Programming vs. Mob Programming
Pair and mob programming are focused forms of these techniques:- Pair programming is ideal for onboarding or tackling complex logic.
- Mob programming shines when you need immediate consensus across multiple stakeholders.
Quality Today, Speed Tomorrow
Investing a bit of extra time now—by pairing or mobbing—yields long-term dividends:- Fewer production defects
- Less rework and firefighting
- Sustainable, well-documented solutions
- Distributed expertise across the team
Avoid endless mob sessions without clear goals. Time-box your collaboration rounds to keep momentum and focus.
Summary
Whether you’re co-creating documents or mobbing through code, these collaborative practices will:- Increase long-term quality by embedding best practices from the start
- Foster team cohesion with shared problem-solving
- Accelerate future delivery by reducing defects and onboarding time
- Distribute knowledge evenly across all members
