Leadership Videos
  • All Technology
  • AI
  • Autonomy
  • B2B Growth
  • Big Data
  • BioTech
  • ClimateTech
  • Consumer Tech
  • Crypto
  • Cybersecurity
  • DevOps
  • Digital Marketing
  • Ecommerce
  • EdTech
  • Enterprise
  • FinTech
  • GovTech
  • Hardware
  • HealthTech
  • HRTech
  • LegalTech
  • Nanotech
  • PropTech
  • Quantum
  • Robotics
  • SaaS
  • SpaceTech
AllNewsDealsSocialBlogsVideosPodcastsDigests

Leadership Pulse

EMAIL DIGESTS

Daily

Every morning

Weekly

Tuesday recap

NewsDealsSocialBlogsVideosPodcasts
HomeBusinessLeadershipVideosScaling Teams with Ownership - Thomas Coopman - DDD Europe 2025
CTO PulseHuman ResourcesLeadershipManagement Consulting

Scaling Teams with Ownership - Thomas Coopman - DDD Europe 2025

•February 16, 2026
0
Domain-Driven Design Europe
Domain-Driven Design Europe•Feb 16, 2026

Why It Matters

Restoring clear ownership and aligning teams to bounded contexts reduces coordination overhead, speeds delivery, and improves product quality by embedding domain expertise and post-release accountability within teams. This offers a practical blueprint for firms whose pursuit of feature-team scale has created fragmentation and slowed outcomes.

Summary

Thomas Coopman described his experience helping Protime scale its engineering organization, where an initial move to feature teams expanded from three to 12 teams and produced more than 40 deployable services. That rapid scaling eroded clear ownership: teams frequently touched many bounded contexts briefly, work handoffs became messy, and agility and velocity declined. Through broad workshops and modeling sessions, the company agreed to restore stronger team ownership aligned to bounded contexts, create cross-functional teams, involve teams earlier in product discovery, and ensure teams remain responsible for running and measuring their features. The shift balances feature delivery with long-term domain knowledge and operational accountability.

Original Description

Domain-Driven Design Europe 2025 - Organised by Aardling (https://aardling.eu/)
https://dddeurope.com
https://newsletter.dddeurope.com/
https://be.linkedin.com/company/domain-driven-design-europe
https://bsky.app/profile/dddeu.bsky.social
https://mastodon.social/@dddeu@m.aardling.social
Thomas recently helped at Protime (https://www.protime.eu/) with a transformation from feature teams to stream aligned teams - or how we called them: domain teams. In this case study, he'll go over what went wrong with their past setup, what kind of problems they have solved and what challenges are still open. Thomas will talk about changing the team structure (from mostly dev teams to more cross functional teams) and giving teams more autonomy, clear ownership and responsibilities helps the teams grow and improves flow in the company.
About Thomas Coopman:
Thomas Coopman is a senior consultant at Aardling. He trains and consults teams working in complex environments to bring meaningful change to their organisations. He has built deep expertise in Domain-Driven Design and optimising for team productivity and efficacy.
Thomas excels with organisations that recognise that high-performing teams need both technical excellence and a relentless focus on process, practices, and environment.
His childhood curiosity with computers took him to the University of Leuven to study computer science. While there, he grew an enduring love for learning new programming languages, with a current proclivity for all things functional programming.
Thomas teaches several public classes on topics ranging from Strategic Design, EventStorming, and Tactical Patterns at DDD Academy. He’s also a regular public speaker, with recent well-received talks at DDD Europe and KanDDDinksy.
Outside of software, Thomas is a keen parent and a triathlon hobbyist.
0

Comments

Want to join the conversation?

Loading comments...