Build With, Not Against

A stance for working across team boundaries: when two teams' work overlaps, the answer is almost never to out-build the other side. Draw the seam, concede where they're better, follow what's best for the customer, and make your durable layer their extension — not a land-grab.

Explanation

The source (Working Heuristics — Data, Matching, Product, Org, Tooling) bundles four moves into one collaboration philosophy:

• Turf friction is almost always an unowned boundary, not redundant work. When two teams grind against each other, the cause is usually a seam nobody owns — not genuine duplication. The fix is to draw the seam explicitly and make the pieces compose, not to build a competing version of the other side's thing.
• Concede where the other side is genuinely better. Yielding the parts they do better is what makes you a partner, not a territorialist. Refusing to concede is how you signal a land-grab.
• Separate "best for the customer" from "keeps my team relevant." These two motives feel identical until they diverge — and when they do, follow customer-best. Naming the difference is what stops relevance-protection from masquerading as strategy.
• Build with, not against: make the durable layer the other team's extension of their own work, not something erected to replace or outflank them. Durable infrastructure that extends a partner's work survives; a land-grab invites a fight.

Why it matters / where it shows up

• Turf fights are usually a design smell. Reframing friction as an unowned boundary turns a political problem into a solvable interface problem — draw the seam.
• It's the org-scale twin of Build It as an Extension. "Extension, not a new thing" recurs at two scales in this source: extend the user's mental model (product) and extend the other team's work (org). Same move against duplication and rivalry.
• It rhymes with Personal vs Team Agents. Every's shift from per-person agents to shared "unit" agents is the same lesson: shared, composable infrastructure beats per-actor land-grabs that no one can maintain or hand off.

Open questions

• "Follow customer-best when motives diverge" assumes you can tell relevance-anxiety from genuine strategic value. How do you keep that distinction honest under political pressure?

Connections

• Build It as an Extension — the product-scale version of the same "extension, not land-grab" move.
• Personal vs Team Agents — shared/composable beats per-actor empire-building; the AI-org analogue of "build with, not against."
• Scope Hygiene for Tickets and Tooling — "draw the seam explicitly" is the collaboration-level version of splitting orthogonal scope and cutting duplicative work.

Sources

• Working Heuristics — Data, Matching, Product, Org, Tooling — turf friction as an unowned boundary; concede where better; customer-best over team-relevance; build with, not against.