home.social

#teamtopologies — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #teamtopologies, aggregated by home.social.

fetched live
  1. 📢Have you heard about course on the "Remote and Hybrid Team Interactions" course by Manuel Pais and Matthew Skelton on the Team Topologies Academy? This is a self-paced video-based course that will help your organization thrive in a #remotefirstworld. The authors of the #TeamTopologies book, will show you how to clarify team interactions for #fastflow, using simple sense-making approaches and tools such as the #teamAPI, core interaction modes, team dependencies tracker, trust boundaries & more.

  2. 📢Have you heard about course on the "Remote and Hybrid Team Interactions" course by Manuel Pais and Matthew Skelton on the Team Topologies Academy? This is a self-paced video-based course that will help your organization thrive in a #remotefirstworld. The authors of the #TeamTopologies book, will show you how to clarify team interactions for #fastflow, using simple sense-making approaches and tools such as the #teamAPI, core interaction modes, team dependencies tracker, trust boundaries & more.

  3. Seasonal Sale for Team Topologies Academy Just Got Bigger! 🚀🔥

    Enjoy 35% OFF on all @team Topologies Academy courses and bundles. Use code "SUMMER2026" by August 31st to gain insights into operational constraints, patterns, and thinking tools that accelerate team flow!

    #TeamDynamics #DDD #EffectiveTeams #FastFlow #TeamTopologies
    bit.ly/3N3pdZG

  4. Seasonal Sale for Team Topologies Academy Just Got Bigger! 🚀🔥

    Enjoy 35% OFF on all @team Topologies Academy courses and bundles. Use code "SUMMER2026" by August 31st to gain insights into operational constraints, patterns, and thinking tools that accelerate team flow!

    #TeamDynamics #DDD #EffectiveTeams #FastFlow #TeamTopologies
    bit.ly/3N3pdZG

  5. I‘ll be at the WeAreDevelopers „World Congress“ in Berlin next week and happy to discuss anything around building and evolving productive engineering organizations, strategic technology leadership, or to deep-dive into event-driven architecture topics. So if you’re also there and want to meet up, DM me.

    #eda #eventdrivenarchitecture #ddd #teamtopologies

  6. I‘ll be at the WeAreDevelopers „World Congress“ in Berlin next week and happy to discuss anything around building and evolving productive engineering organizations, strategic technology leadership, or to deep-dive into event-driven architecture topics. So if you’re also there and want to meet up, DM me.

    #eda #eventdrivenarchitecture #ddd #teamtopologies

  7. Next week, I will be at Flowtopic Live 2026. I'm looking forward to be with other practitioners, and I will give my talk "Team Topologies in the Age of AI".

    I'm working with some companies that are adopting AI while maintaining flow and allowing platforms to emerge. What have been your experiences with it?

    You can join via ➡️ flowtopia.io/flowtopia-live-20

    #FlowtopiaLive #TeamTopologies #AI

  8. Next week, I will be at Flowtopic Live 2026. I'm looking forward to be with other practitioners, and I will give my talk "Team Topologies in the Age of AI".

    I'm working with some companies that are adopting AI while maintaining flow and allowing platforms to emerge. What have been your experiences with it?

    You can join via ➡️ flowtopia.io/flowtopia-live-20

    #FlowtopiaLive #TeamTopologies #AI

  9. Hallo Mastodon 👋

    Ich bin Lead Software Engineer aus Berlin und schreibe hier künftig über Softwarearchitektur, Entwicklung, Teamstrukturen.

    Mich interessiert besonders, wie wir Softwaresysteme bauen, die nicht nur technisch funktionieren, sondern auch verständlich, wartbar und anpassungsfähig bleiben.

    Sense. Learn. Adapt.

    #introduction #SoftwareArchitecture #EventDrivenArchitecture #SoftwareEngineering #TeamTopologies

  10. Hallo Mastodon 👋

    Ich bin Lead Software Engineer aus Berlin und schreibe hier künftig über Softwarearchitektur, Entwicklung, Teamstrukturen.

    Mich interessiert besonders, wie wir Softwaresysteme bauen, die nicht nur technisch funktionieren, sondern auch verständlich, wartbar und anpassungsfähig bleiben.

    Sense. Learn. Adapt.

    #introduction #SoftwareArchitecture #EventDrivenArchitecture #SoftwareEngineering #TeamTopologies

  11. The conference is full steam, and Zsófia Herendi and I will have our hands-on in 3 days. If business value and org design are topics that matter to you, join us at "From org chart to designed organization: making the invisible visible with business models and teams" hands-on lab!

    Learn more here ➡️ 2026.dddeurope.com/program/fro

    #DDDEurope #TeamTopologies #DomainDrivenDesign #OrganizationalDesign

  12. The conference is full steam, and Zsófia Herendi and I will have our hands-on in 3 days. If business value and org design are topics that matter to you, join us at "From org chart to designed organization: making the invisible visible with business models and teams" hands-on lab!

    Learn more here ➡️ 2026.dddeurope.com/program/fro

    #DDDEurope #TeamTopologies #DomainDrivenDesign #OrganizationalDesign

  13. Zsófia Herendi and I will be running a hands-on lab at DDD Europe in Antwerp on
    June 12.

    The premise: you can't design teams without understanding how the business
    creates value.

    We'll connect Business Model Canvas to Team Interaction Modeling. Practical
    heuristics that you will discover by working with your peers!

    This is not a slideshow. A lab where you will share insights with others!

    Use the link for a discount: ti.to/on3/aardling26/discount/

    #DDDEurope #TeamTopologies #DomainDrivenDesign

  14. Zsófia Herendi and I will be running a hands-on lab at DDD Europe in Antwerp on
    June 12.

    The premise: you can't design teams without understanding how the business
    creates value.

    We'll connect Business Model Canvas to Team Interaction Modeling. Practical
    heuristics that you will discover by working with your peers!

    This is not a slideshow. A lab where you will share insights with others!

    Use the link for a discount: ti.to/on3/aardling26/discount/

    #DDDEurope #TeamTopologies #DomainDrivenDesign

  15. You added colors to your org chart and called it Team Topologies.

    The authors didn't mean that. They gave us patterns and heuristics for reasoning about the limits of teams' cognitive load and how it affects the flow of value.

    We need to put the work into designing non-blocking services, streamlining team interactions, and ensuring value flows through the system.

    Org charts show reporting lines. They don't show how value moves.

    #TeamTopologies #FastFlowConf

  16. You added colors to your org chart and called it Team Topologies.

    The authors didn't mean that. They gave us patterns and heuristics for reasoning about the limits of teams' cognitive load and how it affects the flow of value.

    We need to put the work into designing non-blocking services, streamlining team interactions, and ensuring value flows through the system.

    Org charts show reporting lines. They don't show how value moves.

    #TeamTopologies #FastFlowConf

  17. Organisational Dysfunction of the Day

    Team Topologies, the wrong way round

    Context: Leadership has read Team Topologies. The insights are compelling: stream-aligned teams owning end-to-end delivery, platform teams reducing cognitive load, enabling teams building capability. A reorganisation is planned. Teams are renamed and restructured. The new topology is announced. People find themselves in stream-aligned teams that still wait for approval from the same architects, report to the same managers, and receive priorities from the same product managers who held the backlog before. The platform team is the old infrastructure team with a new name and a mandate to serve internal customers, though nobody agreed on what that means. The enabling team runs workshops that nobody has time to attend. Six months in, the cognitive load has not decreased. Delivery has not improved. Leadership concludes that the teams need to embrace the new model more fully. Another round of communication is planned, and product coaches are hired en masse to fix people.

    OST explains: Team Topologies describes structural patterns that emerge from healthy organisations. Like DORA, it is a map of what good looks like, not a recipe for getting there. The patterns only function as intended when the teams operating them are genuinely self-managing, owning their work, coordinating among themselves, and making decisions without constant escalation. Imposing the topology from above while leaving the underlying design principle unchanged is a bureaucratic (DP1) move applied to a self-managing (DP2) framework. Stream-aligned teams become delivery units with a new name. Platform teams become service departments, and their internal customer model quietly recreates the same dependency it was meant to dissolve. Goodhart's law applies here as much as it does to DORA: the moment the topology becomes a target, it stops being a good topology. The book is right. The reorganisation missed the point.

    #OpenSystemsTheory #SocioTechnical #OrgDesign #TeamTopologies

  18. Organisational Dysfunction of the Day

    Team Topologies, the wrong way round

    Context: Leadership has read Team Topologies. The insights are compelling: stream-aligned teams owning end-to-end delivery, platform teams reducing cognitive load, enabling teams building capability. A reorganisation is planned. Teams are renamed and restructured. The new topology is announced. People find themselves in stream-aligned teams that still wait for approval from the same architects, report to the same managers, and receive priorities from the same product managers who held the backlog before. The platform team is the old infrastructure team with a new name and a mandate to serve internal customers, though nobody agreed on what that means. The enabling team runs workshops that nobody has time to attend. Six months in, the cognitive load has not decreased. Delivery has not improved. Leadership concludes that the teams need to embrace the new model more fully. Another round of communication is planned, and product coaches are hired en masse to fix people.

    OST explains: Team Topologies describes structural patterns that emerge from healthy organisations. Like DORA, it is a map of what good looks like, not a recipe for getting there. The patterns only function as intended when the teams operating them are genuinely self-managing, owning their work, coordinating among themselves, and making decisions without constant escalation. Imposing the topology from above while leaving the underlying design principle unchanged is a bureaucratic (DP1) move applied to a self-managing (DP2) framework. Stream-aligned teams become delivery units with a new name. Platform teams become service departments, and their internal customer model quietly recreates the same dependency it was meant to dissolve. Goodhart's law applies here as much as it does to DORA: the moment the topology becomes a target, it stops being a good topology. The book is right. The reorganisation missed the point.

    #OpenSystemsTheory #SocioTechnical #OrgDesign #TeamTopologies

  19. Zsófia Herendi and I will be running a hands-on lab at DDD Europe in Antwerp on June 12.

    The premise: you can't design teams without understanding how the business creates value.

    We'll connect Business Model Canvas to Team Interaction Modeling. Practical heuristics. Real design work.

    This is not a slideshow. A lab where you will share insights with others!

    🌐 2026.dddeurope.com/program/fro

    #DDDEurope #TeamTopologies #DomainDrivenDesign

  20. Zsófia Herendi and I will be running a hands-on lab at DDD Europe in Antwerp on June 12.

    The premise: you can't design teams without understanding how the business creates value.

    We'll connect Business Model Canvas to Team Interaction Modeling. Practical heuristics. Real design work.

    This is not a slideshow. A lab where you will share insights with others!

    🌐 2026.dddeurope.com/program/fro

    #DDDEurope #TeamTopologies #DomainDrivenDesign

  21. Considerations on cognitive load and organisational structure in sociotechnical systems.
    A blog by Martijn Ras

    In this article we present our rule of thumb for the sizing of solutions based on what an organisation can handle. Our primary goal is to make you aware of cognitive load theory and sociological considerations on organisational structure. Be...

    #dev #softwaredevelopment #TeamTopologies #Cognitiveload #Sociotechnicalsystems #Domain-drivendesign #Agilescaling

    jdriven.com/blog/2026/04/sizin

  22. Considerations on cognitive load and organisational structure in sociotechnical systems.
    A blog by Martijn Ras

    In this article we present our rule of thumb for the sizing of solutions based on what an organisation can handle. Our primary goal is to make you aware of cognitive load theory and sociological considerations on organisational structure. Be...

    #dev #softwaredevelopment #TeamTopologies #Cognitiveload #Sociotechnicalsystems #Domain-drivendesign #Agilescaling

    jdriven.com/blog/2026/04/sizin

  23. You can't design teams and software without understanding how value flows through the business.

    My new case study: an e-learning SaaS company used DDD principles and practices to move from a Big Ball of Mud to domain-oriented teams.

    The customer onboarding went from 60 days to 20 minutes. Cloud costs dropped 80%.

    But the story doesn't end here. Read the full case study: joaorosa.consulting/services/o

    #DomainDrivenDesign #TeamTopologies #OrgDesign

  24. You can't design teams and software without understanding how value flows through the business.

    My new case study: an e-learning SaaS company used DDD principles and practices to move from a Big Ball of Mud to domain-oriented teams.

    The customer onboarding went from 60 days to 20 minutes. Cloud costs dropped 80%.

    But the story doesn't end here. Read the full case study: joaorosa.consulting/services/o

    #DomainDrivenDesign #TeamTopologies #OrgDesign

  25. This is just one lesson in a broader course on modern ways of working — covering how teams can move faster, deliver better, and reduce friction that holds progress back.

    ▶️ Check out the full course on the Team Topologies Academy: bit.ly/41HqZ9t

    #TeamTopologies #ProductDevelopment #DevOps #ModernWaysOfWorking

  26. This is just one lesson in a broader course on modern ways of working — covering how teams can move faster, deliver better, and reduce friction that holds progress back.

    ▶️ Check out the full course on the Team Topologies Academy: bit.ly/41HqZ9t

    #TeamTopologies #ProductDevelopment #DevOps #ModernWaysOfWorking

  27. Adding manpower to a late software project makes it later.

    We've known this since Fred Brooks wrote it in 1975—the opening sentence is a direct quote. Yet many projects still try to add people to meet deadlines, and it fails.

    Even skilled developers need ramp-up time, during which they reduce the team's productivity.

    I wrote about why this happens and what actually works: factor10.com/news/why-is-it-so

    #Development #SoftwareDevelopment #Productivity #Automation #TeamTopologies #DevOps #CI

  28. Adding manpower to a late software project makes it later.

    We've known this since Fred Brooks wrote it in 1975—the opening sentence is a direct quote. Yet many projects still try to add people to meet deadlines, and it fails.

    Even skilled developers need ramp-up time, during which they reduce the team's productivity.

    I wrote about why this happens and what actually works: factor10.com/news/why-is-it-so

    #Development #SoftwareDevelopment #Productivity #Automation #TeamTopologies #DevOps #CI

  29. Discover more with our 3-hour, self-paced "Team Topologies Distilled" course by Manuel Pais and Matthew Skelton on the #TeamTopologies Academy. Don’t forget to take advantage of the Easter offer - get 20% off with code “easter2026” (valid until April 14): bit.ly/3glIZxR

    You can check our collection of courses and bundles here: bit.ly/3ACEdVW

  30. Discover more with our 3-hour, self-paced "Team Topologies Distilled" course by Manuel Pais and Matthew Skelton on the #TeamTopologies Academy. Don’t forget to take advantage of the Easter offer - get 20% off with code “easter2026” (valid until April 14): bit.ly/3glIZxR

    You can check our collection of courses and bundles here: bit.ly/3ACEdVW

  31. CircleK eMobility Journey Towards Effective Cross-functional Value Streams (Eduardo da Silva, Guro Fladvad Størdal)

    tube.tchncs.de/w/pu2dT7B3v9aH8

  32. Some of those stickies at the bottom of the board are still open questions. Good. Better to ask them here than have someone answer them quietly in a pull request.
    Architecture is already happening across the whole room. The question is whether we make it visible.

    This is part of day two of my DDD foundation workshop, and honestly one of my favourite conversations to facilitate.

    #DomainDrivenDesign #CollaborativeModelling #EventStorming #SoftwareArchitecture #TeamTopologies

  33. Some of those stickies at the bottom of the board are still open questions. Good. Better to ask them here than have someone answer them quietly in a pull request.
    Architecture is already happening across the whole room. The question is whether we make it visible.

    This is part of day two of my DDD foundation workshop, and honestly one of my favourite conversations to facilitate.

    #DomainDrivenDesign #CollaborativeModelling #EventStorming #SoftwareArchitecture #TeamTopologies

  34. After 2 years consulting DHL eCommerce BeNeLux, I've decided to join them as software architecture enabler.

    The reason? I'm simply not done yet. And I wonder if I ever will be.

    #DomainDrivenDesign #TeamTopologies #SoftwareArchitecture #CollaborativeModelling #EventDrivenArchitecture
    ...

  35. After 2 years consulting DHL eCommerce BeNeLux, I've decided to join them as software architecture enabler.

    The reason? I'm simply not done yet. And I wonder if I ever will be.

    #DomainDrivenDesign #TeamTopologies #SoftwareArchitecture #CollaborativeModelling #EventDrivenArchitecture
    ...

  36. After 2 years consulting DHL eCommerce BeNeLux, I've decided to join them as software architecture enabler.

    The reason? I'm simply not done yet. And I wonder if I ever will be.
    ...
    #DomainDrivenDesign #TeamTopologies #SoftwareArchitecture #CollaborativeModelling #EventDrivenArchitecture

  37. After 2 years consulting DHL eCommerce BeNeLux, I've decided to join them as software architecture enabler.

    The reason? I'm simply not done yet. And I wonder if I ever will be.
    ...
    #DomainDrivenDesign #TeamTopologies #SoftwareArchitecture #CollaborativeModelling #EventDrivenArchitecture

  38. A quick minimal check if your organisation is ready for agentic AI:

    Ask your engineers what the last most valuable thing their team delivered was.

    If they answer with output-oriented answers, "we delivered the shopping cart redesign" or "we shipped the onboarding flow", rather than
    ...
    #SoftwareArchitecture #AgenticAI #TeamTopologies #DomainDrivenDesign

  39. A quick minimal check if your organisation is ready for agentic AI:

    Ask your engineers what the last most valuable thing their team delivered was.

    If they answer with output-oriented answers, "we delivered the shopping cart redesign" or "we shipped the onboarding flow", rather than
    ...
    #SoftwareArchitecture #AgenticAI #TeamTopologies #DomainDrivenDesign

  40. What do you do on the weekend? Prepare for the week ahead.

    I'm finalizing my workshop gear for another #TeamTopologies and #FastFlow 2-day workshop for a cloud platform at a large organization.

    I love these challenges. Finding leverage points for a platform's evolution to increase its effectiveness for the consumers. Plus, it is a regulated industry; we can enable compliance and speed at scale.

    If you want to improve flow with your org, drop me a message. ✍️

    Happy Sunday!