Your technical skills get you hired. Your collaboration skills get you promoted. In tech, almost every meaningful outcome requires people from different disciplines to work together effectively — and yet very little of the career advice aimed at PMs, BAs, and other non-coders addresses how to actually do this well. Here is what each function needs from you, and what you need to stop doing.
What engineers need from you
Engineers need three things: clarity, context, and early involvement. Clarity means requirements that are specific enough to build against — not vague goals but concrete behaviors. Context means understanding why a feature is being built, not just what it should do. Engineers who understand the business context make better technical decisions. Early involvement means bringing engineering into the conversation before the solution is defined, not after. Last-minute requirements changes are the thing engineers find most demoralizing — and they are almost always caused by decisions being made without engineering in the room.
What designers need from you
Designers need user problems, not solutions. The most common mistake people make when working with design is presenting a solution and asking for it to be made pretty. Define what needs to be solved — the user's pain, the behavior you want to change, the outcome you are trying to achieve — and then let design solve it. Designers who are handed the problem instead of the answer do significantly better work. They also feel significantly more respected, which affects the quality of the collaboration over time.
What data teams need from everyone
Data teams need a specific question with a decision attached. “Give me data on engagement” is not a question — it is a fishing expedition that will produce a report nobody acts on. “We are deciding whether to invest more in feature X — can you tell us what percentage of active users have used it at least three times in the last 30 days?” is a question. The decision attached to the data is what makes the analysis valuable.
The communication mistake that creates the most friction
The single most common source of cross-functional friction is presenting to stakeholders decisions that have not yet been shared with the team. Engineers and designers finding out through an announcement that they are building something — rather than being part of the conversation — is one of the fastest ways to damage trust and slow down a team. Share with the team first, then present to stakeholders. Always.
The one habit that makes you a great collaborator
Write things down and share them widely. A decision that exists only in your head is not a decision — it is an assumption waiting to cause a problem. A meeting that produces no written summary might as well not have happened. The people who become known as great collaborators in tech are almost universally people who over-communicate in writing: they send the recap, they document the decision, they share the update before anyone has to ask for it. It takes fifteen extra minutes and it is one of the highest-leverage habits you can build.