Thread by @DrSherryPagoto

How about a thread on #teamscience and collaboration, #academictwitter? I taught a team science class for jr investigators for years and have numerous research collaborations myself. Here are some common issues we discuss (and try to avoid!) when doing team science. 1/x

Avoid bringing collaborators into a grant application at the last minute--- “PO says we need an X and that’s you so can I add you? It’s due Monday.” You’ll get nothing substantive from this person since there is no time. It will show. 2/x

Don’t ignore the feedback of collaborators. If you decide to go a different way of their suggestion, it's ok just explain why. It will feel like a waste of time if they went through your grant and they feel you ignored their input. This could lead them to disengage. 3/x

When subcontracting other investigators, each should have the work they are supervising on their respective budget. Asking subcontractors to train your unskilled staff to do a highly technical skill is unnecessarily risky, esp if they have a team who is ready to do the job. 4/x

Note: The cost of having a subcontractor train new folks won’t be less than a subcontract to get skilled people to do it.

In scenarios where getting your staff trained up makes sense (developmental studies), the budget should reflect that extra effort from the contractor. 5/x

When the grant is funded but budget is cut (of course!), engage the team in the cutting decisions. Going it alone risks bad blood especially if cuts seem to disproportionately affect some team members. 6/x

Put collaborators on as co-Is or even multi-PI instead of consultant if the expertise needed is very central to the implementation of the project, Sidelining as consultant to save $ could lose points in study section. And you get less out of that team member. 7/x

BTW, what is diff between consultant, co-I and multi-PI? Consultant – person to invite to a meeting here and there to react to things, review documents, or very time limited specified task. This person is more of a distant, one step removed expert. Very advisory. 8/x

Co-I – this person is at all or most team meetings, including DSMBs. They play an integral role in the project and typically have a set of tasks they are in charge of. 9/x

Multi-PI (or sub-PI)– this person shared in the conception of the idea and provides an expertise that is essential to carry it out AND is bringing their team and/or resources to carry out a significant piece of the project. 10/x

Beware of overtaxing co-I’s during the grant writing process. Be sure meetings are agenda-driven and only when absolutely necessary. For example, a co-I who is only on a grant for 5% probably shouldn’t be expected to attend weekly 2 hour meetings for 6 mos before deadline. 11/x

If you need THAT much time from a co-I during grant writing, you under-budgeted for them. Rule: The time you ask for pre-award should parallel how much you’ve budgeted for them post-award. 12/x

Don’t leave consultants out after the grant gets funded. When I was junior I was afraid to bother my consultants who were so senior to me, so I underutilized them. That was a mistake. 13/x

Finally, avoid being PI-centric. I know that is the model in science, but it isn't conducive to creating high performing, cohesive teams. Be team-centric by engaging team in all decisions--methodological and financial. 14/x