Reciprocity in networking: remember commitments, not debts

Reciprocity in networking works best when you remember commitments and context, not when you keep a private tally of favours. A useful introduction may be met with a thoughtful update. Advice received today might shape help you offer someone else months later. The exchange can still be reciprocal without being immediate or equal.

That distinction matters because a professional relationship starts to feel different once every interaction carries an invisible price.

Reciprocity is a norm, not an invoice

Sociologist Alvin Gouldner described reciprocity as a broad social norm: people should help those who have helped them, and avoid harming them. It wasn't a rule that each act must be repaid in the same form or on the same timetable. Expectations also shift with culture, context and the relationship itself.

Later work by Linda Molm examined different structures of reciprocal exchange and how they shape trust and solidarity. The practical point is simple. Reciprocity in networking has more than one valid shape.

A former colleague reviews your proposal. You thank them and tell them what changed because of their comments. Months later, you introduce them to someone who understands a problem they're working on, after checking that both people want the introduction. Those actions are connected by care and attention, not by a calculation that the review was worth one introduction.

Keep the person visible

Some professional networking feels uncomfortable because the relationship has been reduced to what one person can provide. In four studies, Tiziana Casciaro, Francesca Gino and Maryam Kouchaki found that professional-instrumental networking could prompt feelings of moral dirtiness, especially when people pursued relationships mainly for career or task-related gain.

The answer isn't to avoid asking for help. Work runs on advice, referrals, introductions and shared effort. But the person and the shared context should stay visible.

Before making a request, ask yourself:

Why am I asking this person rather than anyone with the same job title?
What context do they need to decide freely?
Is the request specific enough to accept, decline or change?
Have I left room for no?

That last question matters when there is a power difference. A junior colleague, job seeker or dependent contractor may find it hard to decline a senior person's request. Compliance doesn't necessarily mean the exchange felt fair.

Replace favour accounting with commitment memory

A favour ledger records who owes whom. Commitment memory records what you actually agreed to do.

Those records lead to very different behaviour. “Owes me an intro” turns a person into an unsettled account. “Asked me to send the research link on Friday” gives you a clear next action. One invites judgement. The other helps you follow through.

Keep a short record when something concrete happens:

a promise you made
a question you agreed to revisit
an introduction that needs consent or acknowledgement
a useful update you want to send

Don't assign private scores such as “high value”, “three favours owed” or “good source of referrals”. They flatten a relationship into a rating and can colour how you interpret the next interaction.

You don't need to capture every generous act either. Record enough to act thoughtfully, then let ordinary human warmth remain ordinary.

Close the loop without forcing an equal return

When someone helps you, a concise update can be more meaningful than a rushed attempt to repay them.

Suppose a contact introduces you to a hiring manager. You don't owe them an introduction of identical value. You can thank them, let them know the conversation happened and acknowledge what their help made possible. If a relevant opportunity to support them appears later, offer it without presenting it as settlement.

Specific, optional offers work well:

I know someone who has worked through a similar supplier issue. Would an introduction be useful?

Consent matters because an introduction creates work and expectations for three people. Ask both sides before sharing details. A well-meant connection can still be a burden if it arrives without context.

Reciprocity can also travel through a wider network. Advice from an experienced founder may help you support a newer operator later. A professional group might benefit from the time you received from one of its members. That broader contribution doesn't erase your responsibility to thank the original helper. It recognises that healthy networks aren't made of closed two-person accounts.

Give without making generosity compulsory

Research by Adam Grant and Jane Dutton found that reflecting on benefits people had given strengthened a caring contributor identity and increased later prosocial behaviour more than reflecting on benefits received. This suggests a useful shift in attention: remember the contribution you can make, not only the debt you might owe.

But generosity needs boundaries. You can decline when a request exceeds your time, expertise, confidentiality obligations or emotional capacity. You can also offer a smaller form of help.

Instead of taking a 60-minute call, you might send one relevant resource. Instead of making an introduction, you might explain why the match doesn't feel right. A clear limit is kinder than a vague yes followed by silence.

A three-question reciprocity check

Before your next follow-up, take two minutes and ask:

What did I promise?
What context should I remember?
What can I offer that is genuinely relevant, rather than performative?

Notice what isn't on the list: “What do they owe me?”

A private relationship map can give those promises and contexts a home. In Kinnetly, you can record who introduced whom, connect people to the companies, groups or events that explain the relationship, keep private notes and set a follow-up for the action you agreed to take. It doesn't calculate reciprocity or decide whom you should help. The judgement stays with you.

Remember the promises and context that make reciprocity thoughtful. Start your relationship map in Kinnetly.