A recommended recipe
Keep it simple. Start with one flow for each team. CA Flowdock provides the most benefit for teams that are building something together and use common tools.
Flows can either be visible to and joinable by anyone in your organization, or invite-only. We recommend keeping team flows open for others to join. Doing this lets people from outside the team drop by for quick questions, or simply spectate if they’re interested in what the team is doing. Trust your people to focus on the things that matter to them – avoid creating barriers for communication. We believe that people know best what information they need to get their job done most effectively.
Bigger groups that meet less frequently can benefit from having their own flows to gather topics over time and to share notes or progress to a larger audience. Team flows probably have more “noise”, both in the chat and team inbox integrations.
Cross-company flows that focus on a certain topic (“Mobile development”, for example) are a good way to gather the people who are interested in some subject, even though they might not be in the same team or department. These flows are a great way of spreading domain-specific knowledge across an organization.
Higher level flows for groups of teams, departments or the whole company can also be a good idea. These flows should be used when the conversation topic concerns a larger group than just a team. One risk for these flows is that they become too noisy, in which case reminding participants how many people are being notified of their messages can help.
Anyone in your organization can create a flow. The flow creator or an organization administrator are the only ones who can disable and delete a flow. Otherwise, all flow members have equal rights: anyone can add or remove team inbox content or change the flow’s settings.
Open vs. invite-only?
By defaulting to open flows, people suddenly have a new way of collaborating or solving problems across the company: they can easily pop into flows for teams, topics and company functions that they can join when needed. These flows will contain the team members, subject area experts or simply interested parties that can answer questions. Compared to email, where the sender needs to know who to contact and where responses can take days or weeks (due to gatekeepers and the nature of the medium), open flows often provide answers within minutes or hours.
- Try defaulting on open.
- CA Flowdock defaults to allowing anyone in your organization to join a new flow. You need to explicitly check the box that says "Open flow to any member of organization name" when creating the flow. This option can later be enabled or disabled.
- Invite-only flows are, of course, a necessity for some teams or subjects. For example, HR teams often discuss topics that should stay within teams due to legal reasons.