Why this works
Most great work happens at the seam between two functions. Engineering and sales. Marketing and support. Product and finance. Capturing those collaborations on camera shows the rest of the org how the work actually gets done, and shows candidates a company that doesn't operate in silos.
Who you'll feature
Two teammates from different functions. Pair them on a shared project.
A manager from each side. One sentence each on what made the partnership work.
A customer or downstream stakeholder if the project shipped externally.
How to capture it
Use Remote recording to bring both teammates into one frame for a 20-minute conversation.
Three prompts:
What were you trying to do that you couldn't do alone?
What did you learn about each other's job?
What would you tell another pair trying to copy this?
Use AI Writer to draft a written companion piece from the transcript.
For software-led collaborations, add a screen recording of the actual workflow.
Reuse it (the 1:10 framing)
One cross-team conversation becomes:
A 3-minute pair feature for the internal Channel.
A 60-second LinkedIn cut.
A blog post titled "How we work across teams."
A new-hire orientation clip on cross-functional norms.
A manager-enablement asset.
A recruiting clip for collaboration-heavy roles.
A board-update slide on operating rhythms.
A reference link in the next planning offsite kit.
An all-hands feature.
A pinned recurring series on the Channel feed.
Group the series into a Collection in Ready to Share people leaders can hand to managers as part of operating-norm training.
Common mistake
Picking the success story everyone already knows about. The most useful collaboration content names the friction. What broke, what nearly didn't ship, what each side wishes the other did differently. Honest seams are more teachable than victory laps.