At some point, you'll be in a meeting where a colleague presents a half-formed idea and gets praised for it. Or you'll watch someone less competent than you get the project you wanted. Or you'll hear that a peer got a better rating in the same cycle where you did more work.
The instinct, in those moments, is competitive. To position, to angle, to make sure the right people know who actually did what.
That instinct isn't wrong, exactly. Visibility matters. Credit matters. But when competition becomes the default mode — when colleagues become opponents, when every interaction becomes a positioning exercise — you've made a trade that doesn't pay off. You win the room and lose the room over time.
This isn't a piece about being nice. It's about what actually works over a 20- or 30-year career — which, it turns out, looks a lot more like long-term investing than a series of tactical wins.
In this article
Why Smart People Play Zero-Sum — and Why It Backfires
Zero-sum thinking at work isn't irrational. It often emerges from real structural pressures: finite promotion slots, limited budgets, calibration curves that force relative rankings. When only one person on a five-person team can get the top rating, it's not paranoid to think about your position relative to theirs.
The problem isn't the instinct. It's that the game being played in most organizations is longer and more networked than any single review cycle, and purely competitive behavior tends to have compounding costs that outrun compounding gains.
The Four Ways Zero-Sum Thinking Costs You
It makes you harder to promote
Promotion decisions — especially to senior individual contributor (IC) or management tracks — increasingly hinge on cross-functional influence. Decision-makers want to know: does this person make the people around them better? A reputation for being competitive rather than collaborative is a specific flag that blocks senior advancement in most organizations.
It shrinks your information access
People share information with people they trust. In competitive environments, colleagues start filtering what they share with rivals — which means the person playing hardball is often the last to know what's actually happening. Collaboration expands your information network; competition contracts it.
It damages your external reputation over time
Industries are small. The colleague you undermined at company A becomes your interviewer at company C, your client at company D, or your reference's colleague everywhere. In a career spanning multiple decades and multiple companies, the external reputation you build among peers outlasts any single internal win. Word travels further and faster than most people expect.
It's cognitively expensive
Tracking perceived rivals, managing your positioning relative to others, parsing every interaction for competitive subtext — it's exhausting. That cognitive load comes directly out of your capacity for actual work. The people who are genuinely great at their jobs rarely have the bandwidth to be great competitors as well.
The Compound Return on Collaboration
Think of professional relationships the way a long-term investor thinks about a portfolio. Individual transactions — a favor given, a piece of knowledge shared, a project supported — seem small in the moment. Compounded over five or ten years, they become the network that defines your career options.
The mechanics of collaboration compound in a few specific ways:
Year 1–2: You build a reputation as a multiplier
When you help colleagues do better work — sharing context, offering your time, connecting people who should meet — you become known as someone who makes things happen. This is low-cost to you and high-signal to your organization. Calibration committees notice who the team runs through for help.
Year 3–5: Your network becomes an asset that opens doors
The colleagues you've invested in start moving into positions of influence themselves. You get considered for projects before they're announced. Opportunities come to you via people who know you, rather than through applications or cold outreach. Your ambient network — former colleagues, adjacent industry contacts — starts delivering returns that have nothing to do with your current employer.
Year 7–10: The network provides resilience when things change
Layoffs, reorgs, industry shifts — a career spanning decades will encounter all of these. The people who navigate them fastest are almost universally the ones with strong collaborative networks. References come through. Job leads materialize. Soft landings happen. This is the return that no individual win can replicate.
📊 What the research shows
Organizational network research consistently finds that employees who sit at the center of collaborative networks — the people others go to for advice, input, and connection — advance faster, are more resilient to layoffs, and report higher job satisfaction than high performers who work primarily in isolation.
The finding that's perhaps most counterintuitive: in many studies, being a "connector" in the informal network predicts promotion more reliably than individual performance metrics. The person who helps everyone tends to be more visible and more trusted than the person who quietly excels alone.
How to Collaborate Without Losing Ground
The legitimate worry underneath most competitive behavior is this: if I'm generous with my time, my ideas, and my credit — will I get taken advantage of? Will I end up doing everyone else's work while they advance?
It's a fair concern. Indiscriminate generosity — saying yes to everything, sharing every idea with no regard for attribution, doing favors for people who never reciprocate — is not the strategy. Here's what the distinction looks like in practice.
Collaboration That Builds Capital vs. Collaboration That Drains It
| Builds capital ✓ | Drains it ✗ |
|---|---|
| Sharing relevant information proactively | Sharing everything indiscriminately (your time is not unlimited) |
| Giving credit to specific colleagues in front of leadership | Deflecting all credit in a way that erases your own contribution |
| Helping with a project because you can add real value | Taking on others' work that belongs to them, not you |
| Advocating for a colleague in a meeting they're not in | Advocating so loudly for others that your own work goes unnoticed |
| Saying no to requests that don't fit your capacity or goals | Saying yes to everything to seem helpful, then underdelivering |
| Building reciprocal relationships — investing in people who invest back | Continuing to invest in relationships that consistently take and never give |
The "Give First, Track Lightly" Framework
The most effective collaborators tend to operate on a simple principle: give generously by default, but pay attention to patterns over time. A colleague who takes without reciprocating over months — who never returns favors, never acknowledges contributions, never shows up for you — deserves less of your investment going forward. That's not cynicism; that's calibration.
Importantly, this doesn't mean scorekeeping on individual transactions. If you helped a colleague navigate a political situation in January and they didn't immediately return the favor, that's not a red flag — it's just how most reciprocal relationships work. The unit of analysis is the pattern over months, not the tit-for-tat of individual exchanges.
The Visibility Problem — Solved Without Competing
The most common pushback on "collaborate more" is this: visibility matters for advancement, and if you're busy elevating others, you become invisible yourself. It's a legitimate concern, but it conflates two things that are actually separable: making others look good and making yourself invisible.
The best collaborators are, in fact, highly visible — not despite their generosity but because of it. Here's how they make both work at the same time.
Visibility Through Collaboration, Not Competition
Be the person who synthesizes, not just executes
In collaborative work, there's usually someone who does the work and someone who articulates what the work means. The person who can say "here's what we learned across all of this and what it means for the strategy" gets credit proportionate to the whole effort, not just their slice. Be that person.
Give credit in a way that includes yourself
"The team did great work on this — Jamie built the model, I led the analysis and presentation" is both generous and complete. "The team did great work" alone erases you. You can acknowledge others and document your own contribution in the same sentence. This isn't taking credit; it's accurate attribution.
Let your quality speak across the team's output
When you help a colleague produce better work, that better work reflects on you too — if the people involved know about your contribution. Brief, well-placed comments in shared channels ("Happy to help Alex with the deck structure — it came out really well") establish both your generosity and your involvement.
Build visibility directly with senior stakeholders
If you're worried that being generous makes you invisible to leadership, the answer isn't to stop being generous — it's to build your own senior relationships in parallel. A collaborative reputation at the peer level, combined with direct visibility at the leadership level, is the strongest possible combination. See the section on skip-level relationships in the Workplace Relationships pillar guide.
📋 A scenario worth thinking through
You and a peer both contributed to a project. In the debrief, your peer gets most of the praise and you get a nod. You feel like you did more of the work.
The competitive move:
Wait for another opportunity to position yourself, downplay your peer's contribution subtly, make sure people know it was you. This typically reads as political and insecure — and your peer now views you as a rival.
The collaborative move:
Talk to your manager directly: "I wanted to flag my specific contributions to the project — I led X and Y. I'm not raising this to take credit from [peer], but I want to make sure my work is visible." Direct, professional, and non-adversarial. This almost always works better than positioning.
When Competition Is Actually Healthy
This piece isn't an argument against all competition. Some forms of competition are genuinely useful — professionally and organizationally. The distinction is whether you're competing against a standard or competing against a person.
✓ Healthy competition
- Competing against your own past performance
- Competing to produce the best work in a pitch or proposal
- Being motivated by a high-performing peer to raise your own standards
- Healthy market comparison — understanding your value externally
- Competing for a role that genuinely requires selection
✗ Corrosive competition
- Actively working to make a peer look worse to look better yourself
- Withholding information a colleague needs
- Positioning against a peer in conversations with leadership
- Sabotaging a project you're not leading so yours looks stronger
- Using a colleague's mistake as a political opportunity
High-performing teams often have significant internal competition — for resources, recognition, stretch roles — that nonetheless functions collaboratively. The difference is whether the competition is transparent and above-board or political and covert. Organizations tolerate (even encourage) the former and consistently punish the latter.
⚡ On stack ranking
Some organizations — particularly in tech and finance — use stack ranking or forced distribution for performance ratings, where only a fixed percentage of the team can receive the top scores. This does create genuine zero-sum dynamics within a review cycle. Even so, the long-game argument holds: the colleague you beat for a top rating this year is still a peer you'll collaborate with next year, reference after this company, and potentially hire or be hired by later. Perform well. Don't sabotage.
Collaboration in Hybrid and Remote Teams
In 2026, most knowledge workers operate in some form of hybrid or fully remote environment. This changes the texture of collaboration significantly — for better and worse.
The upside: distributed teams can surface talent across geographies and reduce the "loudest voice in the room" dynamic that disadvantages quieter contributors in in-person settings. The downside: the informal bonds that make collaboration feel natural — the hallway conversation, the post-meeting coffee — don't happen automatically. They have to be engineered.
What Breaks Collaboration in Remote Settings
Async communication gaps breed misreading
A terse Slack message that would read as neutral in person reads as cold or dismissive over text. Remote teams need more explicit warmth and context than in-person teams — not less. Erring on the side of more explanation, not less, reduces unnecessary friction.
Silos form faster when there's no ambient connection
In-person offices create incidental cross-pollination — you overhear a conversation, you run into someone from another team. Remote environments don't. Without deliberate cross-team relationships, teams naturally silo and collaboration becomes transactional.
Recognition travels less naturally in distributed environments
In an office, praise given in a meeting is heard by everyone present. In async environments, it often doesn't travel at all unless deliberately shared in a visible channel. Collaborators who give credit in public, shared forums — not just in private messages — are more effective at building trust across distributed teams.
Practices That Work
Recognize publicly in shared channels
A specific, public acknowledgment in a team Slack channel or shared thread is the remote equivalent of praising someone in a meeting. It takes 30 seconds and is seen by everyone who matters.
Schedule optional connection time — and show up
Virtual coffees, casual check-ins, team channels that aren't only about work — these are the remote version of ambient connection. They feel optional until you realize that the people who showed up to them know each other better and collaborate more fluidly.
Over-communicate on cross-functional work
In cross-team remote projects, clarity on who owns what, how decisions get made, and how conflicts get resolved needs to be explicit — not assumed. Teams that invest 20 minutes at the start of a project on "how we'll work together" save hours of confusion later.
Maximize in-person time when you have it
When your team is together — offsite, company event, quarterly visit — use it for relationship investment, not just logistics. One real conversation builds more collaborative trust than weeks of well-crafted Slack messages.
Frequently Asked Questions
Summary
What to Take Away
Zero-sum thinking has real structural causes — but it compounds costs faster than it compounds gains. The people you out-maneuver today are the industry you navigate for the next 30 years.
Collaboration compounds: a reputation as a multiplier, a network that opens doors, and resilience when things change — none of these are available to people who played purely competitive careers.
Collaboration and self-advocacy are not opposites. Give credit accurately — including your own contribution. Be visible. Build direct relationships with leadership. You don't have to choose between generosity and advancement.
Give generously by default, calibrate by pattern. Relationships that consistently take and never reciprocate deserve less of your investment — not grudgingly, just rationally.
In remote and hybrid environments, collaboration doesn't happen by proximity. It requires deliberate scheduling, public recognition, and maximizing in-person time when it exists.
More in the Workplace Relationships Series
Workplace Relationships Series · Pillar
The Complete Guide to Workplace Relationships
The full framework: managing up, peer dynamics, visibility, and conflict
Workplace Relationships Series
How to Work With Any Manager
Managing up — for every type of boss
Workplace Relationships Series
How to Handle Workplace Conflict Without the Drama
Navigate tension, have hard conversations, keep relationships intact
Promotion Strategy Series
What Promotion Committees Actually Look For
Why collaborative reputation shapes promotion outcomes — and how to build one