March 9, 2026 · 5 min
Relationships are the technical skill.
The operators who compound aren't the ones with the cleanest Salesforce org. They're the ones every function trusts in the room. In this job, fluency in three or four stakeholder languages is as load-bearing as the schema underneath.
Somewhere along the way the ops conversation got obsessed with the stack. Which CDP, which warehouse, which orchestration layer, which agent framework. Fine questions. But I've watched too many technically excellent ops leaders stall out because they couldn't get a creative director, a head of sales, and a staff data engineer to agree on what we were actually trying to do this quarter. The stack wasn't the problem. The room was.
A modern GTM ops role is a translation job. You sit at the seam between the business, the brand, the data, the systems, and the field — and every one of those rooms speaks a different language. With sales, the only currency that matters is whether you've put yourself in their shoes and you understand what drives their number. With your data partners on the B2B side, it's stability, contracts, and trust — they need to know the pipe won't move under them on a Tuesday. With creative and brand, it's respect for the craft; the second they smell you reducing their work to a variant ID, you're done. With engineering, it's precision and no hand-waving. With execs, it's the business outcome, not the mechanism.
Go B2B2C or B2C2B and the surface area doubles. Now you've got an experimentation culture on the consumer side that wants to ship and learn weekly, and an enterprise side where a partner relationship took two years to build and one bad release to break. You don't get to pick which language to learn. You learn all of them, or you become the person who's technically right and organizationally isolated — and that person's roadmap quietly dies every planning cycle.
Here's the reframe: relationships aren't soft skills sitting next to the real work. They are the real work. They're the substrate that lets you hold the line on what actually moves the business while compromising gracefully on shape, sequencing, and surface. Keep everyone in the loop. Give everyone a voice. Be willing to bend on the how. Be stern on the what. You can only do that last part if you've spent the capital to be trusted by every function in the room — and that capital is built one conversation, one shipped commitment, one honest disagreement at a time.
The honest counterargument is that this sounds like a long way of saying "be political." It isn't. Political operators optimize for their own standing. Trusted operators optimize for the business and bring everyone with them. The difference is visible inside of one quarter. One builds a coalition that ships foundational work; the other builds an audience.
If you're early in this career and you want to compound, invest in the relationships at the same rate you invest in the stack. Sit with sales on a Friday. Walk a creative director through what you're actually proposing before the doc goes out. Buy your data engineer coffee and ask what's been annoying them for six months. None of that shows up on a resume. All of it shows up in whether the next big bet you propose actually gets built.