Contact us
Thank you for your message, we'll come back to you shortly.
Oops! Something went wrong while submitting the form.
Back to Blog

TakeTurns Tips: Collaboration compartmentalization

At Every Turn TakeTurns Blog
|  by
Clare Nosowitz
Clare Nosowitz
Customer Success Manager
TakeTurns Tips
TakeTurns Tips: Collaboration compartmentalization

TakeTurns is designed to simplify your external collaborations while making them more secure. 

One way TakeTurns achieves this is through compartmentalization, or the practice of separating information and resources into distinct sections or compartments, to limit access and reduce the risk of unauthorized disclosure or compromise.  TakeTurns is broadly supportive of this security practice. For example, only individuals invited by leaders can participate in a TakeTurns collaboration or flow. Another example, TakeTurns, allows you to separate your external collaboration into as many (or as few) parts as necessary.   And that’s the topic of today’s tip. 

Rather than illustrate the concept in overly conceptual terms, let’s focus on a concrete example. Consider an RFx project (RFI, RFP, RFQ), from the point of view of the procurement team, the external collaboration portions could be one big collaboration between the department and a vendor, or it could be broken into three big phases:

  • Invite: The procurement team invites vendors to participate. As part of the process, NDAs are exchanged to show commitment to the process
  • Provide Package (and Receive Response):  In this phase, the RFI/RFP/RFQ, etc. is released to the participating vendors. The vendors respond and then the purchasing team downselects vendors for evaluation.  (In some cases, this can result in custom demos, proof of concepts, or pilots).
  • Award: The procurement team selects and engages in negotiations as the final step of the purchase process.

RFx Tools Need To Support the Organic Structure of RFx Projects

How to compartmentalize your collaborations

Choosing between one big collaboration or several small collaborations depends on the degree of compartmentalization required by your organization. 

For example, in many organizations, the individuals participating in subsequent phases are often different from their predecessors. In these kinds of scenarios, we might choose to create new collaborations for that team (as opposed to removing participants and changing subject lines). The one exception might be a situation in which the participants need content or findings from previous phases to complete their jobs. In those cases, one might choose to extend the collaboration over multiple phases. 

Other scenarios where a single collaboration approach is useful are client service scenarios, as one might find in accounting.  For example, a single collaboration for a quarter (or fiscal year) might be useful since the team on the client side (and at the accountancy) might wish to reference or review material previously exchanged. 

In any case, TakeTurns provides the flexibility to accommodate your organization’s security and operating model.  

Final Thoughts

If you’re ready to elevate the way you work with external stakeholders, are interested in a demo, or just want to reach out, click here to discover the transformative impact TakeTurns can have on your external collaborations.

Go async eBook