top of page
fond flou.png
fond flou.png

2026-07-27

When No One's Wrong, Everything's Broken

A typical situation where nobody is really bad at their job:
→ the PO sits in every single product discussion
→ the devs build what's in the ticket, nothing more
→ the Scrum Master is running around trying to help but just adds noise

You can't expect a team to properly perform if they don't get the big picture. As always: "Take it to the team!"

Coeur.png

15

comment2.png

3

View on

LinkedIn.png
stickerweb-color.png
stickerweb-color.png
erik collard linkedin team collaboration diagram showing Product Owner DevOps and Scrum Master roles
TOP COMMENTS

This is a common pattern. Most teams don't struggle because people lack capability. They struggle because context stays with a few people instead of being shared across the team. When everyone understands the "why" behind the work, ownership naturally increases and collaboration becomes much easier.

Tolu

If we're doing anything new or different, "why" is going to be my first question. It might seem annoying, and some people will lead with "what" and "how". But the way I make sense of things I need to understand what problem we're solving so then I can think critically about the proposed solution. I think I've seen too many shiny solutions that just end up adding additional problems. … more

Nina

bottom of page