I'm not sure the tomato business translates well to IT. I'm a project/product manager and I'm writing specifications, give an answer if someone is unsure about

I'm not sure the tomato business translates well to IT. I'm a project/product manager and I'm writing specifications, give an answer if someone is unsure about how to do something, link departments, contact the outside, try to find ways to improve weak work. While I try to make my team self-sufficient, it surely doesn't default to it. Programmers forget to remind marketing of releases, front-end guys don't talk enough to the designers, QA as the last link has to work overtime when time is scarce, programmers writing UI ignoring all conventions and of course the common disagreement that dissolves in to nothing with a hint of counseling. Any tips for making myself less needed? I really try, but giving away responsibilities most often fails. I recently started tracking delegated tasks so things are actually done at some point (devs have tickets, but other departments don't). With demanding upper management everyone also feels like he has no time to do anything other than "his job" regarding further responsibilities (even though the team is generally great and thinking along well).