Fixing Cross-Team Collaboration Through Structured Retrospectives

To resolve recurring misalignment between design and engineering teams at France.tv, I introduced structured, cross-functional retrospectives at the end of each six-week PI cycle. These sessions, powered by FigJam and tracked in Confluence, created space for open dialogue, reduced cross-team tension, and transformed communication into a shared strength—unblocking stalled projects and reinforcing continuous improvement.

Context

When I arrived, the design team was working in isolation, with minimal collaboration across web, app, and TV development teams. This led to:

  • Friction between design and engineering
  • A lack of transparency or feedback culture
  • Misalignment that blocked decision-making
  • Projects stalled at the design phase due to communication breakdowns

Design was seen more as a bottleneck than a strategic partner.

The Solution: Cross-Functional Retrospectives

Dedicated Retros by Tech Team

France.tv had separate engineering teams for web, apps, and TV. We created tailored retrospectives for each stream, ensuring discussions were context-specific and actionable.

Mixed Team Participation

Each retro brought together designers and engineers from the same stream. These weren’t all-hands sessions—they were focused, respectful spaces for team-to-team alignment.

Structured Reflection

Each session followed a simple, repeatable format:

  • What worked well?
  • What didn’t?
  • What do we want to change?
  • What actions can we take now?
Tracking & Accountability

All retrospective feedback, outcomes, and action items were logged in Confluence, creating a transparent record that evolved over 1.5 years.

Interactive & Engaging

We used FigJam to facilitate discussion visually, making it easier for all voices to participate—regardless of seniority or discipline.

‍

Impact

  • Improved cross-team collaboration
    Designers and developers began solving problems together rather than working in opposition
  • Unblocked critical projects
    The previously stalled initiative was able to move forward once trust and transparency were rebuilt
  • Higher team alignment
    Teams began proactively raising and addressing friction points during PI planning
  • Cultural shift
    Communication, previously flagged as a weakness, became a strength recognized across the org

Why It Mattered

This initiative wasn’t just about agile rituals. It was about building trust, accountability, and shared ownership across product and tech. Over time, retrospectives became a foundational part of how France.tv teams aligned—not just on tasks, but on how they work together.

Previous Project
Automating Digital Production at Blizzard with Internal Tools
Next Project
Scalable Landing Page System for Overwatch’s Global Launch