Cross-Functional Collaboration Framework

Content design at Cvent was always downstream, copy requests arrived after the IA was locked and the flows were built. I ran discovery across engineering, product, support, and marketing to map every gap where content wasn't involved but should have been. The result was a structured collaboration model that scaled to new teams without being rebuilt each time.

The problem

Content design was always downstream. By the time the copy request arrived, the IA was locked, the flows were built, and the only option was to write around a broken structure.

What I did

Discovery across engineering, product, support, and marketing mapped every touchpoint and every gap where content design wasn't involved but should have been.

Documented a collaboration model showing when and how content designers engage across the product lifecycle: ideation, design, build, ship, post-launch.

Implemented as structured 1-hour sessions with stakeholders covering role overviews, touchpoint mapping, open Q&A, and agreed next steps.

Result

• Earlier content involvement meant fewer structural rewrites late in the sprint.
• Teams outside UX understood what content design actually does and when to bring us in.
• The framework scaled as new teams joined without needing to be rebuilt each time.