3 ms·

What about as a way to make sure the different teams know what everyone else is doing?

• Consultant32452 9y ago
  Your post just made me shudder. There's nothing I can say or do to stop my PM from calling those exact meetings. I've gone so far as to say, "I'm already working with [dept rep 1] and [dept rep 2], they're both being extremely responsive and actively working on solving this problem with me. There's no need to take action." The immediate response is to call a meeting, bring in extra business people, and call it a "working session" that ultimately slows progress and increases confusion because now the tech people have to continually translate what we're doing into non-tech speech.
  • fhood 9y ago
    I don't usually have to go to these meetings, but I find it very convenient to have at least one person on the team who can let people know when they are reinventing a wheel that was already implemented by another team.
• andygcook 9y ago
  In my experience this doesn't work really well because although it solves the problem for the people in the meeting, most organizations don't have a culture of documentation to actually write down what was talked about in the meeting. As you grow, it's almost inevitable someone who would find that information useful won't be there because of a multitude of reasons (sick, traveling, stuck in another meeting).
• tboyd47 9y ago
  Why can't they work that out themselves? Are you such a critical link between them that you have to be driving every interaction? If that's the case, why can't you provide the information they need yourself, rather than playing matchmaker?