Pollinators: The Art of Cross-Team Connection
Hook: You're not on any one team, but somehow you're essential to all of them. You carry knowledge, patterns, and context across organizational boundaries that were never meant to be crossed.
You might not even know you're a Pollinator.
You're in a meeting with Team A and you mention something Team B is doing. Eyes widen. "They solved that? We've been struggling with it for weeks!" You make an introduction. A month later, Team A has adopted Team B's pattern and both teams are moving faster.
You didn't write any code. You didn't design any systems. You just... connected dots.
That's pollination. And it's rarer and more valuable than most organizations realize.
The Bee Metaphor
In Three Sisters agriculture, the three plants can't pollinate themselves. They need bees to carry pollen from one plant to another, enabling reproduction and genetic diversity.
In organizations, Pollinators serve the same function:
- They carry patterns from one team to another
- They make introductions that wouldn't happen organically
- They identify duplication before it becomes entrenched
- They spread cultural norms across organizational boundaries
Without Pollinators, teams become islands. Each team solves the same problems independently. Knowledge silos form. The whole becomes less than the sum of its parts.
Why Pollinators Are Undervalued
Here's the problem: pollination doesn't look like work.
You weren't in a meeting; you were wandering between meetings. You didn't write code; you just talked to people. You didn't ship a feature; you just suggested that two teams should talk.
Try putting that on a performance review.
"What did you accomplish this quarter?"
"I helped Team A discover that Team B had already solved their problem, saving three months of redundant work."
"But what did you build?"
This is why Pollinators often struggle in organizations that only value direct output. Their value is indirect—but it's enormous.
What Pollinators Actually Provide
1. Knowledge Distribution Information in organizations is unevenly distributed. Team A knows something Team B needs, but neither knows the other exists. Pollinators are the information superhighway between silos.
2. Duplication Prevention How many times has your company built the same authentication system? The same logging framework? The same deployment pipeline? Pollinators catch this before it compounds.
3. Pattern Recognition Pollinators see the organization from above. They notice when three teams are struggling with the same problem. They spot systemic issues that look like local issues from inside any single team.
4. Social Glue Organizations are human systems. Trust between teams doesn't happen automatically—someone has to build relationships across boundaries. Pollinators are that someone.
5. Cultural Coherence How do you maintain consistent engineering culture across fifty teams? You don't mandate it from the top. You have Pollinators who carry and reinforce cultural norms through personal connection.
The Failure Mode: The Busybody
Every archetype has a dark side. For Pollinators, it's becoming a Busybody.
Symptoms:
- You're in every meeting but add little value
- You share information that doesn't need sharing
- You make connections that don't need making
- People groan when they see you coming
- You've confused being visible with being valuable
Root cause: You've optimized for seeming connected rather than creating real connections. You're performing pollination rather than doing it.
The fix: Be ruthlessly honest about value. Did that connection actually help? Did that information actually matter? Would they be worse off without your involvement? If you can't answer yes, you're not pollinating—you're just buzzing.
What Pollinators Need
To thrive, Pollinators need:
1. Time to wander. If every hour is accounted for, pollination can't happen. Pollinators need slack in their schedule—time to have unplanned conversations, to sit in on meetings that aren't theirs, to explore.
2. Cross-team access. You can't pollinate from inside a single team. Pollinators need permission and context to move across organizational boundaries.
3. Social capital. Pollination only works if people trust the Pollinator. Building that trust takes time and investment. Organizations should recognize that relationship-building is part of the work.
4. Recognition for indirect impact. "Helped Team A and Team B align, saving three months of work" should count on performance reviews. If it doesn't, you're telling Pollinators their work doesn't matter.
5. Organizational awareness. Pollinators need to know what's happening across the org. They need context—strategy, roadmaps, pain points—to know where pollination is most valuable.
The Organizational Superpower
Here's what most organizations don't realize: Pollinators are how you scale culture without bureaucracy.
Process can't make teams collaborate. Documentation can't create trust. Mandates can't spread best practices.
But a Pollinator who's trusted by multiple teams can accomplish all of these—faster, cheaper, and more effectively than any top-down initiative.
When you find a natural Pollinator, don't make them a "regular" engineer. Let them pollinate. The ROI is enormous.
Next in series: "Pollinators: When Connection Becomes Distraction"