We could, but it would be more work (having to create those communities and get them all set up), and I could see one of two things happening:
(a) If we move everyone to the new joint communities, the individual team comms would be abandoned and I'm not sure I really want that, especially since I want people to feel like their original team comm is their homebase.
(b) If we instead make people join their home team comm AND the new joint team comm, I foresee that people will be a bit confused which comm they should post entries to. I can see that either the same situation as (a) will end up happening (everyone using the joint comm exclusively), or the opposite -- that people continue to post in their separate comms and the joint comm ends up being useless.
I guess I just felt that keeping people in their same comms but allowing both teams to see what the other is posting was the best way to keep content in the original team comms but allow collaboration as well.
no subject
(a) If we move everyone to the new joint communities, the individual team comms would be abandoned and I'm not sure I really want that, especially since I want people to feel like their original team comm is their homebase.
(b) If we instead make people join their home team comm AND the new joint team comm, I foresee that people will be a bit confused which comm they should post entries to. I can see that either the same situation as (a) will end up happening (everyone using the joint comm exclusively), or the opposite -- that people continue to post in their separate comms and the joint comm ends up being useless.
I guess I just felt that keeping people in their same comms but allowing both teams to see what the other is posting was the best way to keep content in the original team comms but allow collaboration as well.
Does that make sense?