Gaining the confidence to speak up when cross-team work isn’t working

There's a kind of friction that shows up in healthy companies: your team is doing fine on paper, but you're spending real hours absorbing someone else's gaps. Maybe another team isn't holding up their side of shared reliability. SLOs slip, alerts are noisy or missing, and your engineers end up doing triage work that isn't really yours to own. Or a partner team takes forever to make an important decision, and your roadmap sits in a holding pattern while you're still accountable for dates.

The instinct in those moments is often to stay quiet. You don't want to be difficult. You don't want to look like you're throwing another team under the bus. You tell yourself it's temporary, or that raising it will make things awkward in the next cross-functional meeting.

Sometimes that's true. A lot of the time, silence just encodes the problem into "how we work here," and your team pays for it on nights and weekends.

You can speak up without picking a fight. Chances are you're not the only one seeing the issue, and putting words to it can help your peers, too. The goal is to name a joint dependency with enough specificity that it can actually get fixed.