
I’ve been wrestling with a challenge that a lot of product design teams run into: how do you balance vertical focus with horizontal collaboration?
On paper, vertical focus makes sense. Each designer is tied to a product area or feature, with clear goals and ownership. But once the work starts overlapping across navigation, accessibility, or consistency, things can get messy. Designers get stuck, become unsure of their role, and sometimes burn out trying to cover too much without enough communication or support.
How Design Teams Tend to Be Structured
Most design teams evolve into one of two shapes.
Vertical focus (pods, squads, feature teams): Designers embed with engineers and product managers, focusing deeply on one feature or user journey. This creates speed and alignment, but it can also lead to silos.
Horizontal focus (architecture teams, design systems, shared practices): Designers work across products to ensure cohesion, scalability, and shared standards. This avoids duplication, but it can also slow things down or blur ownership when communication is weak.
Some organizations try a hybrid model, with pods supported by design system or architecture groups. Even then, the balance can be fragile.
When Things Work, and When They Break
Vertical pods work best when designers also have a strong community of practice to return to. Without that, they risk drifting apart in quality or direction.
Horizontal teams do well when they are not working in isolation. If they connect regularly with pods through working sessions, shared critiques, and open communication, they create real value. If they only act as gatekeepers, they slow the work down.
The biggest breakdowns happen when:
-
Horizontal ownership isn’t clear, leading to confusion about who should do what.
-
One designer ends up doing it all, creating bottlenecks and burnout.
-
Collaboration is passive, limited to reviews instead of co-creation.
Approaches That Help
I’ve gone through this a few times, and I keep seeing the same pattern. Teams with strong communication and a genuinely collaborative environment tend to have less friction. The hard part is making that collaboration clear and repeatable. Here are a few ways to do that.
1. Build a “Yes And” Culture
Borrowed from improv, this mindset means designers build on each other’s ideas instead of shutting them down. Instead of saying, “that’s not in the system,” the response becomes, “yes, and here’s how we can adapt it to fit both the system and the feature.”
It helps prevent the “us vs. them” dynamic that can show up between pods and horizontal teams. One Redditor described bi-weekly “design snaps,” where each designer shared quick visuals of their work so others could riff on them and add ideas:
“Super fast … way to skim what everyone is doing and you can dig deeper if interested.” - Source
The effect: less competition, more collaboration.
2. Collaborate Frequently and Live
Collaboration works best when it happens often and in real time. Co-working sessions, design sprints, critiques, and even “trifecta meetings” (designer, PM, engineer) help catch issues early.
A Redditor explained how their team stayed aligned:
“We also have ‘trifecta’ meetings weekly with me, PM and Engineering manager so we are constantly in sync on scope work and roadmap planning.” (source )
At Pinterest, teams leaned heavily on rituals like weekly critiques and design all-hands. One designer said:
“At Pinterest, we had strong team rituals … weekly Design All-hands, a Pillar-wide design meeting, and a weekly Crit, and this brought a lot of peace to our schedules.” - Source
3. Keep Communication Visible
Shared boards, working-on logs, and open updates reduce duplication and misalignment.
A PM noted that even something as simple as having designers join daily stand-ups helped keep everyone on track:
“It’s helpful when small design clarification questions arise, Designers have a better sense of what’s going on ATM.” - Source
Communication is less about volume and more about visibility. The goal is to make work easy for other people to see and build on.
4. Spread Out Horizontal Ownership
When one designer owns all of navigation, accessibility, or the system library, burnout usually follows. It’s better to distribute ownership and rotate responsibilities.
Teams that handle this well create shared leadership. System leads partner with feature designers, and contributions flow both ways.
As one designer put it bluntly: “Being system owner + feature design lead + component library upkeep … is unsustainable. Spread it out.” - Source
5. Use Rituals and Cadence to Create Cohesion
The best teams do not leave collaboration to chance. They formalize it through regular critiques, show-and-tells, and retrospectives focused on cross-team alignment.
At Pinterest, weekly critiques were not just about polishing pixels. They were a way to see across pods, spot overlap, and keep the design language coherent.
These rituals make space for collaboration before problems become crises.
6. Choose Tools and Documentation That Enable, Not Control
Design systems, component libraries, and shared docs are powerful, but only when they feel supportive instead of restrictive. Teams that thrive document decisions with context, including why a choice was made, not just the rule itself. They make systems extensible instead of rigid.
As one product leader wrote:
“Pick the right tools and establish communication standards … Clear tools and norms reduce misunderstandings.” - Source
Conclusion
Balancing vertical focus and horizontal cohesion is not a one-time problem. It is an ongoing practice. The teams that do this well are not the ones that found the perfect structure. They are the ones that built the culture and rituals to support the structure they have.
From “yes-and” mindsets to weekly critiques, from rotating ownership to visible communication, none of these methods are especially fancy. They just work. The goal is not control. It is cohesion. Not one designer carrying everything, but a team lifting together.