Stop 11 · Stakeholder Management & CommunicationTopics · 1/9

Cross-Functional Collaboration

In short

Nobody on the team reports to you, yet you're blamed if the launch slips. Your real tool is how well design, engineering and sales trust you and each other.

A PM has no direct authority over design, engineering, marketing or sales — success depends entirely on earning trust and alignment across teams you don't manage.

The purple blob holds a setlist on a small stage beside a drum kit, guitar and keyboard.

Think of it like this

The college band

The drummer, guitarist and keyboard player each know their instrument better than you. Your job is the setlist: which song, in what key, for which crowd. Tell them early and listen to their ideas, and the show works. Hand them a list ten minutes before going on stage, and it falls apart.

Watch it happen

Kicking off a feature with three teams

Design

Engineering

Sales

Problem + user quotes

1/5You share the problem and real user words before any solution. Design gets the why, not a screen to copy.

The big ideas

What you need to know

Trust before tasks

Have coffee with your engineers and designers before you need anything. People help those they know.

Share the why

Teams make better calls when they know the problem and the goal, not just the ticket.

Involve early

Bring people in while ideas are rough. Late surprises feel like orders, early ones feel like teamwork.

Give credit away

Publicly thank the people who did the work. It costs you nothing and builds goodwill.

Save yourself the pain

Common mistakes

Oops

Handing engineers a finished spec and asking for an estimate.

Do this instead

Show them the problem early and ask how they'd solve it. You'll often get a cheaper idea.

Oops

Talking to each team separately and telling each a slightly different story.

Do this instead

Keep one shared doc and one message so nobody hears conflicting plans.

Your mission

Map your team

~25 min

Quick check

When is the best time to involve engineers in a new feature idea?

Go deeper

1Map every function your product touches and what each one needs from you.
2Learn to speak each team's language: metrics for growth, feasibility for engineering, positioning for marketing.
3Practice proactively sharing context before someone has to ask for it.