Building a strong connection - at the social level - is one of the most important things in the implementation of an EU project. Mónica Expositor Blasco is an expert on this and therefor a natural expert guest for my episode on social elements when implementing EU projects in my Implementation Series. There were many things to discuss, so this episode is divided into two episodes.

In the first half, we examine the human side of EU project delivery - how teams actually work together once the grant is awarded. We map the “typical consortium story”: euphoric kick-off, then a slide into silent struggle - passive meetings, free-riding perceptions, unclear roles, and coordination teams forced into “babysitting”. Monica’s point is blunt: these aren’t just people problems; they’re architecture problems. Most projects rely on informal habits and administrative project management, but rarely design how collaboration should function. Rhythms, roles, rules, spaces, and norms that help a set of entities act like a team.

Monica introduces the role of a collaboration architect - not just facilitating one good meeting, but blueprinting the whole system. We have a look at the symptoms of weak architecture (information-dump kick-offs, passive observers, “update theatre”), then get concrete about solutions: phased kick-offs with online onboarding before the room, interactive formats instead of slide marathons, and a light playbook that sets communication norms, decision paths and “speak-up-early” principles. We close with practical examples like speed-dating across work packages, movement and micro-rituals to get voices in the room, and agenda designs that prioritise sense-making and decisions over presentations.

In the second half we then get hands-on with practical tools and the principles behind them. Monica walks through dynamic kick-off designs (gallery walks, “cross-WP speed-dating” with three clarifying questions), flipping monthly calls from update theatre to problem-solving, and building a single source of truth with a lightweight project hub and task-oriented channels. We cover weekly asynchronous “last week I / this week I” updates, rigorous agendas framed as questions, and the core principles that make it all work: design before you build, make the implicit explicit (via a team playbook), engineer serendipity, and move from contract to commitment.

Time codes (part 1):

00:01:41 Introduction

00:03:59 Fly in

00:06:52 A consortium's "typical story"

00:17:33 The diagnosis: Symptoms of a weak architecture

00:30:36 The solution: Designing the system for success

Time codes (part 2):

The future: collaboration as a competitive advantage

Practical tools and why they work

Reflections and advice

The toughest challenge