Socio-techno problems require you to grapple with both the socio and technical.

At large engineering-driven companies it's possible to accidentally ignore the socio component: "If I just got the founder to tell the other team the right technical answer is X, this would be solved".

But in situations where you have to coordinate not only internally but with external parties, there's no boss to go to that can magically fix things with the right pronouncement.

That makes it more obvious you need to grapple with the socio components too.