> Markdown version of [/videos/100146-five-ways-to-break-silos-in-your-engineering-organization](https://www.wearedevelopers.com/videos/100146-five-ways-to-break-silos-in-your-engineering-organization). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Five Ways to Break Silos in Your Engineering Organization

Breaking engineering silos doesn't require top-down mandates or massive budgets. Discover five grassroots strategies to drive cross-team collaboration and build collective ownership.

- **Speakers:** [Daniel Schniepp](https://www.wearedevelopers.com/@daniel-schniepp)
- **Event:** World Congress 2026 Europe
- **Published:** July 9, 2026
- **Duration:** 28:49
- **URL:** https://www.wearedevelopers.com/videos/100146-five-ways-to-break-silos-in-your-engineering-organization

## Summary

When entering a large or fast-growing enterprise, it is common to find deep silos hindering cross-team collaboration, but bridging these gaps does not require massive budgets or top-down management mandates. Start by building grassroots communities of practice grouped around shared engineering interests, which encourages vital organic connections. Expanding on this momentum, teams can transition to building shared infrastructure in public—such as enabling broad internal contribution to a central Terraform monorepo—which transforms individual code contributions into a widespread sense of collective ownership. To combat remote-work fatigue and the isolation of acquired team members, lightweight internal hackathons and low-budget tech conferences can spark spontaneous problem-solving and immediate inclusion. Furthermore, offering flexible, opportunity-driven job rotations allows engineers to find greater organizational impact without the friction of formal rehiring processes, directly aligning personal passion with overarching corporate needs.

However, grassroots freedom must be balanced with sensible structure to achieve lasting impact. By establishing technical governance and developer "golden paths" through architecture decision records and dedicated platform engineering teams, organizations can prevent autonomous units from operating in a vacuum. Freedom without direction ultimately reconstructs the very boundaries you aim to remove, causing teams to diverge on tooling based on gut feelings rather than shared strategy.

For these cultural initiatives to endure, champions need a supportive manager who grants the autonomy to experiment, coupled with a genuine passion for their chosen topics. It is crucial to lower the high-pressure dynamics typical of technical expert circles by remaining approachable and prioritizing trust-building. Organizers must embrace the 1-9-90 rule of community engagement, recognizing that while the vast majority may only lurk or observe, they still absorb valuable knowledge and learn to identify internal experts. Finally, do not view the conclusion of an initiative as a failure; sunsetting an event or splintering a broad town-hall into more targeted communities of practice is a natural, healthy part of scaling an organization's collective intelligence.

**Keywords:** breaking engineering silos, cross-team engineering collaboration, grassroots communities of practice, internal developer conferences, corporate hackathons, open internal code contributions, shared infrastructure monorepos, flexible engineering job rotations, technical governance, golden paths for developers, architecture decision records, platform engineering teams, inclusive remote engineering culture, inner source methodology, 1-9-90 community engagement rule, sunsetting team initiatives

## Chapters

1. **Encountering organizational silos in enterprise environments** (00:03) — Joining a large enterprise often reveals rigid team structures that hinder collaborative engineering efforts.
1. **Creating grassroots testing and tech practice communities** (02:19) — Establishing self-driven discussion groups like testing Tuesday fosters intrinsic knowledge sharing outside formal team boundaries.
1. **Driving inner-source collaboration through shared infrastructure** (04:11) — Creating shared infrastructure and monorepos allows teams to adopt inner-source models and take collective ownership.
1. **Reviving connection with internal conferences and hackathons** (05:58) — Organizing low-budget internal tech conferences and hackathons counteracts remote work fatigue and builds momentum.
1. **Facilitating engineering job rotations and expanded ownership** (09:13) — Offering flexible opportunities to swap projects empowers engineers to take ownership without relying on top-down assignments.
1. **Aligning decoupled teams using platform golden paths** (11:34) — Implementing empowering structure and architecture decision records prevents unaligned engineering teams from re-isolating.
1. **Securing management support and finding personal passion** (15:38) — Receiving adequate managerial autonomy and finding personal passion are underlying prerequisites for driving grassroots change.
1. **Lowering intimidation to encourage open technical communication** (17:38) — Fostering an approachable culture ensures technical expertise is shared without intimidating peers.
1. **Understanding participation metrics in engineering community groups** (19:08) — Embracing the 1-9-90 community dynamic helps leaders accept that most members will observe rather than actively contribute.
1. **Knowing when to adjust or stop internal initiatives** (20:34) — Iterating on successful collaborative models involves knowing when to split, adjust, or sunset older activities.
1. **Audience Q&A on remote engagement and startup culture** (22:50) — Answering audience questions on engaging remote engineers, handling human connections across organizational charts, and scaling up startup culture.

## Related Moments

- [Navigating and mitigating the impacts of broken engineering cultures](https://www.wearedevelopers.com/videos/1998-from-code-to-culture-why-leadership-determines-software-quality) (from "From Code to Culture: Why Leadership Determines Software Quality")
- [Breaking down organizational silos to define platform engineering culture](https://www.wearedevelopers.com/videos/238-the-journey-from-developer-to-devops-what-i-ve-learnt-along-the-way) (from "The journey from developer to devops - what i've learnt along the way")
- [Breaking down team silos and overcoming group thinking](https://www.wearedevelopers.com/videos/235-antipatterns-nemesis-of-software-development) (from "Antipatterns - nemesis of software development")
- [Breaking organizational silos to drive actual cultural transformation](https://www.wearedevelopers.com/videos/1842-the-climate-of-talent-from-microtrends-to-macro-forces) (from "The Climate of Talent: From Microtrends to Macro Forces")
- [Summarizing the organizational benefits of platform engineering](https://www.wearedevelopers.com/videos/885-platform-engineering-vs-devops-why-not-both) (from "Platform Engineering vs. DevOps Why not both?")
- [Aligning project communication and breaking enterprise silos](https://www.wearedevelopers.com/videos/463-let-developers-develop-again) (from "Let developers develop again")

## Related Articles

- [10 Creative Workshop Ideas for Conferences](https://www.wearedevelopers.com/magazine/363-10-creative-workshop-ideas-for-conferences)
- [How Engineering Hubs Build Visibility at Developer Conferences like WeAreDevelopers World Congress](https://www.wearedevelopers.com/magazine/720-how-engineering-hubs-build-visibility-at-developer-conferences-like-wearedevelopers-world-congress)
- [The Most Important Concept Every Developer Should Know](https://www.wearedevelopers.com/magazine/344-the-most-important-concept-every-developer-should-know)
- [The Future of Open Source: A Deep Dive - Scott Chacon at WeAreDevelopers World Congress 2024](https://www.wearedevelopers.com/magazine/471-the-future-of-open-source-a-deep-dive-scott-chacon-at-wearedevelopers-world-congress-2024)

## Related Jobs

- [Tribe Lead - ( Software) Engineering Centre of Excllence](https://www.wearedevelopers.com/jobs/ext/1475530-tribe-lead-software-engineering-centre-of-excllence) at **SD Worx**
- [Senior Engineer, Infrastructure Platform](https://www.wearedevelopers.com/jobs/ext/328836-senior-engineer-infrastructure-platform) at **Intercom, Inc.**
- [Senior Software Engineer](https://www.wearedevelopers.com/jobs/ext/15942-senior-software-engineer) at **GitHub**
- [Senior Software Engineer, Enterprise Products](https://www.wearedevelopers.com/jobs/ext/1841248-senior-software-engineer-enterprise-products) at **GitHub**
- [Principal Software Engineer, Enterprise AI Platform](https://www.wearedevelopers.com/jobs/ext/1467292-principal-software-engineer-enterprise-ai-platform) at **GitHub**
- [Principal Software Engineer, Database Infrastructure](https://www.wearedevelopers.com/jobs/ext/1465908-principal-software-engineer-database-infrastructure) at **GitHub**