Lessons from Unifying Divisions Across People, Systems, and Product
About Me
I’m Sean Herschmiller. My work spans large and small tech organizations. I’ve led product teams through integrations, culture shifts, and realignments—always learning that lasting impact starts with how we treat each other, not just how we ship.
There’s a quiet friction in most product-led organizations. Teams working on parallel product lines—even in the same tech stack—drift into silos. Divisions pop up not just between workstreams, but also in culture, tooling, and priorities.
I’ve seen it firsthand. Product teams supporting different solutions inside the same ecosystem used separate developer tools, prioritized their own customer feedback, and built processes incompatible with each other. Over time, these splits become invisible walls. Collaboration sags, major initiatives stall, and even shared wins get lost because nobody “feels ownership” outside their lane.
When strategic alignment became critical, the instinct was to unify “the product.” What I learned is this: you can’t build one team by declaring one roadmap. Real one-team impact only happens when you start with people and systems.
Where Most Unification Efforts Fail
- Product-first focus: Leaders often demand a unified roadmap, expecting teams to comply. But alignment rarely lasts unless it’s rooted in shared values and day-to-day workflows.
- Tooling disconnects: Teams working on similar software use incompatible dev tools and processes. Friction increases, and information gets lost.
- Identity silos: Even inside a single company, groups cling to their own identity. The intent isn’t bad—it’s pride and loyalty—but it fights against bigger goals.
How One-Team Thinking Succeeds
- Start with people: Before touching the product, hold joint retros, planning sessions, and social events. Let teams see each other as partners, not competitors.
- Audit systems: Map out every tool, document, and collaboration process. Where are things breaking? Where does redundancy waste time?
- Celebrate cross-team wins: Make a point to highlight and reward work done as a collective. This rewires incentives and speeds up adoption.
What Worked in My Experience
- Invite engineers to share the quirks of their workflows, then pick one joint tool or process to trial for a month.
- Create joint feature panels for feedback and decision-making across teams, not top-down mandates.
- Anchor integration efforts in shared rituals—demo days, bug bashes, informal “ask me anything” hours—where teams explain decisions, not just deliver code.
For Product Managers
Whether you own security, developer experience, or the next AI-driven release, start your one-team push at the people and systems level:
- Build a simple, shared space for daily questions and wins.
- Flatten hierarchies by rotating facilitation in meetings.
- Let engineers and PMs shape the new processes. When they design the playbook, they own the change.
Last Word
Unifying product teams takes patience. It starts in conversations before diagrams, rituals before feature specs. Products follow people. Systems enable the habits to stick. Roadmaps only work when everyone believes they’re building the same thing for the same reason.
This experience taught me to lead with empathy, system thinking, and visible reward—not slogans or mandates. It’s the best asset I’ll bring to my next team.