Cross-functional collaboration guide
How to work across engineering, design, and data in tech
In tech, no one builds anything alone. PMs, BAs, UX designers, and CSMs all depend on relationships across engineering, design, data, and business teams. The people who rise fastest are rarely the most technically skilled — they are the most effective collaborators.
Working with each function
Each function has a different working style, different pressures, and different definitions of "done." Here is what each team needs from you — and what erodes the relationship.
Engineering
What they need from you
- Clear, unambiguous requirements
- Context on why, not just what
- Early involvement — not last-minute asks
What to avoid
- ✕Changing requirements mid-sprint
- ✕Communicating deadlines without effort estimation
- ✕Making technical decisions without engineering input
Golden rule
'What constraints should I know before I finalize this spec?' asked early saves days of rework later.
Design
What they need from you
- User research and context, not solutions
- Space to explore before committing to one direction
- Feedback on behavior and user goals — not aesthetic preferences
What to avoid
- ✕'Can you just make it look nicer?'
- ✕Making design decisions without design input
- ✕Presenting wireframes to stakeholders before the designer has seen them
Golden rule
'What is the problem this design needs to solve?' — ask before looking at solutions.
Data
What they need from you
- Clear questions — not open-ended 'give me everything'
- Context on decisions being made
- Reasonable timelines (data requests take time)
What to avoid
- ✕Asking for data after a decision has already been made (post-hoc justification)
- ✕Ignoring inconvenient findings
Golden rule
'If we find X, we will do A. If we find Y, we will do B.' — define your decision criteria before requesting the analysis.
Marketing
What they need from you
- Feature details in customer language, not technical language
- Enough lead time to create campaigns
- One key message to anchor on
What to avoid
- ✕Last-minute launch requests
- ✕Giving marketing a feature, not a story
The collaboration habits that compound
Individual interactions matter, but the habits below shape your reputation across every team you touch — and their effect grows over time.
1Write decisions down
A Slack message is not a decision. Notion, Confluence, or a doc is. If it is not written, it did not happen — and everyone will remember it differently.
2Over-communicate changes
Send an update when scope changes, even small ones. The teams depending on you cannot adjust to information they do not have.
3Celebrate the team, not yourself
Credit flows back to people who share it. The most effective collaborators make others look good — and earn trust that compounds over time.
Next steps
Choose your role in the tech team
Cross-functional collaboration is a shared skill, but the way you apply it depends on your role. Explore the track that fits where you are headed.