The word capacity almost always travels in one direction: something one side has and the other needs.
But working productively under real constraint is itself a capability — and it is usually held by the side that is assumed to be receiving help.
Capabilities that are undervalued
- Designing studies that remain valid when conditions are unpredictable.
- Maintaining equipment far past its supported life.
- Collecting high-quality data in difficult field settings.
- Working across many languages and community contexts.
- Delivering results on budgets a fraction of the size.
What each side genuinely brings
- One side may bring instruments, funding and access to certain literatures.
- The other brings context, feasibility judgement, relationships and data that exist nowhere else.
- Neither list is a subset of the other.
- Treating one as help and the other as need distorts everything downstream.
Better questions to ask
- What can you do that I cannot?
- What would you build if resourcing were not the constraint?
- What have previous partners got wrong?
- The last question produces the most useful answer and is asked least often.
Where support is genuinely wanted
- Ask rather than assume; the answer is often not what you expected.
- Frequently it is analytical methods, not equipment.
- Frequently it is help getting work published, not help producing it.
- Sometimes it is access to literature behind paywalls.
Reframing the relationship
- Describe the partnership by what each side contributes, publicly and in writing.
- Let your partner describe their own contribution in proposals.
- Notice how you describe them to colleagues when they are not present.
- That last habit reveals what you actually think.
One thing worth remembering
Ask: what have previous international partners got wrong?
It gives your partner explicit permission to tell you something useful about a pattern they have lived through repeatedly. Almost nobody asks it, and the answer will save you from repeating a mistake that is entirely visible from their side and entirely invisible from yours.
Câu hỏi thường gặp
What capabilities are undervalued?
Designing studies valid under unpredictable conditions, maintaining equipment past its supported life, collecting quality data in difficult field settings, working across languages and communities, and delivering on far smaller budgets.
What does each side genuinely bring?
One may bring instruments, funding and literature access; the other brings context, feasibility judgement, relationships and data that exist nowhere else — neither list is a subset of the other.
What are better questions to ask?
What can you do that I cannot, what would you build if resourcing were not the constraint, and what have previous partners got wrong.
Where is support genuinely wanted?
Ask rather than assume — frequently it is analytical methods rather than equipment, help getting work published rather than producing it, or access to paywalled literature.
What habit reveals what you actually think?
How you describe your partner to colleagues when they are not present.
