Collaborations rarely collapse over scientific disagreement. They collapse over expectations that both sides held confidently and never stated — and the same handful of failures repeat across partnership after partnership.
Failure one: assumed availability
- One side plans as if the other has full-time staff on the project.
- In reality teaching loads, other grants and part-time students dominate the calendar.
- Prevention: ask for actual hours per week per person, in writing, at planning stage.
Failure two: undefined authorship
- Nobody raises it until a draft exists, at which point the conversation is loaded.
- The less powerful partner absorbs the outcome silently.
- Prevention: settle criteria and order before data collection.
Failure three: the timeline that ignored approvals
- Ethics, permits and institutional sign-off take months, not weeks.
- The project is already late before any work starts.
- Prevention: ask your partner how long approvals historically take at their institution.
Failure four: the budget built in one country's economy
- Costs, overheads and salary norms differ substantially.
- Under-budgeting the local side creates dependence and resentment.
- Prevention: have the local partner build their own budget lines.
Failure five: everything rested on one relationship
- The individual who drove it moves, retires, or changes field.
- No institutional agreement exists and nothing is documented.
- Prevention: framework agreement plus at least two contacts on each side.
Failure six: silence read as agreement
- Concerns were raised indirectly and not recognised as concerns.
- By the time they are stated plainly, the problem is large.
- Prevention: written summaries after meetings, individual follow-ups, and asking what would make this difficult.
One thing worth remembering
Every one of these is preventable in the first month and nearly unfixable in the last.
The first month is when everyone is optimistic and nobody wants to raise awkward operational questions. That is precisely when raising them costs nothing — and it is the single highest-return hour of work in the entire collaboration.
Câu hỏi thường gặp
What actually causes collaborations to fail?
Not scientific disagreement but expectations both sides held confidently and never stated — and the same handful of failures repeat across partnerships.
What is the assumed-availability failure?
One side plans as if the other has full-time staff, while teaching loads, other grants and part-time students dominate the calendar — prevented by asking for actual hours per week in writing.
Why do timelines fail?
Because ethics approvals, permits and institutional sign-off take months not weeks, so the project is late before work starts — ask how long approvals historically take at that institution.
What goes wrong with budgets?
They get built in one country's economy while costs, overheads and salary norms differ substantially — under-budgeting the local side creates dependence and resentment.
When are these failures preventable?
In the first month, when everyone is optimistic and nobody wants to raise awkward operational questions — which is exactly when raising them costs nothing.
