In this article
  1. 1. Listen for the person's actual concern
  2. 2. Make your follow-through small and reliable
  3. 3. Create an occasion to do something useful together
  4. 4. Make introductions with consent and context
  5. What to do when a relationship feels one-sided
  6. Build relationships through one specific practice

The difference appears after the first conversation. A connection request records contact; what happens next determines whether the relationship develops.

1. Listen for the person's actual concern

Ask a relevant question and stay with the answer before moving to your own experience. Curiosity is useful when it helps you understand, rather than when it becomes a technique for extracting a favour.

Dorie Clark's article on meaningful business relationships discusses personal attention and continued contact. The four practices below are an original application for employed professionals, without reproducing its anecdotes.

In a hypothetical conference conversation, a training manager mentions difficulty giving new supervisors practical experience. Instead of immediately offering a product, ask what makes the transition difficult and what they have already tried.

Respect the depth they choose. A professional conversation does not require private personal disclosure, and you should not collect sensitive information merely to appear attentive.

Try a useful follow-up question

Ask, “Which part is hardest in practice?” or “What would a better result look like?” These questions invite detail without presuming that you understand the problem.

If you have relevant experience, offer it honestly and briefly. If you do not, listening is still a worthwhile contribution.

2. Make your follow-through small and reliable

Promise less and complete what you promise. A specific resource delivered when agreed is more credible than a broad offer to “help with anything.”

For the hypothetical training manager, you might offer to send a public checklist discussed in the conversation. Confirm that it is relevant, available and appropriate to share before making the promise.

A useful follow-up could say:

Here is the public resource we discussed. The section on planning a first assignment seemed closest to your question. I have not tested its approach in your setting, so treat it as a possible starting point.

That wording preserves the difference between sharing a resource and claiming it will solve the problem.

Repair a missed commitment plainly

If you cannot deliver, explain briefly and revise the commitment. Do not disappear or send an unrelated item simply to claim you followed up.

Reliability includes acknowledging a limit. You can maintain trust without being able to provide every answer.

3. Create an occasion to do something useful together

Shared work can deepen understanding because people see how each other thinks and follows through. Keep the activity proportionate to the relationship.

Options include comparing notes on a public industry question, reviewing a short non-confidential draft by mutual agreement or participating in a relevant professional discussion.

Avoid volunteering someone for work they have not accepted. A vague invitation to collaborate can conceal a large request for unpaid effort.

For the hypothetical training conversation, a short exchange about what makes a first assignment clear may be sufficient. There is no need to launch a joint project.

Define the boundary

State the purpose, expected effort and what each person will contribute. Agree how any resulting work or ideas may be attributed.

If a collaboration could conflict with employment duties, intellectual property or confidentiality, clarify the relevant rules before proceeding.

4. Make introductions with consent and context

Ask both people before connecting them. Explain why the conversation may be relevant and let each person decide without pressure.

Do not imply that one person has agreed to advise, hire or endorse the other. An introduction opens a conversation; it does not create an obligation.

Use a concise explanation of shared interests, then step back. Avoid oversharing either person's private circumstances to make the introduction seem more compelling.

Keep the relationship human

Not every useful relationship needs an introduction, a collaboration or a schedule. Sometimes a thoughtful conversation is enough.

Notice whether your approach makes it easy for the other person to participate and decline. Respect is part of the value you bring.

What to do when a relationship feels one-sided

Review the pattern before making another request. Have you mostly asked for advice, sent material the person did not request or assumed they would make time whenever you contacted them?

If so, reduce the demand and complete any outstanding commitment. A brief thank-you or relevant update may be more appropriate than another invitation. Do not manufacture a favour to create the appearance of balance.

The other person may also be busy, uninterested or managing constraints you cannot see. You do not need to diagnose the reason. Respect their response and leave room for the relationship to remain limited.

If collaboration is creating unclear expectations, state the boundary directly and courteously. For example, agree that you can review one short draft but cannot provide ongoing unpaid support. A clear limit can preserve goodwill better than reluctant agreement followed by silence.

Relationships beyond networking still need consent, capacity and realistic expectations. The goal is repeated, voluntary evidence of consideration, not an obligation to become close to every professional you meet.

Build relationships through one specific practice

Start with someone you already know. Listen more closely, complete an outstanding promise, suggest a bounded shared activity or offer a permission-based introduction when there is a genuine fit.

Explore BrandofYou, building a reputation and professional visibility without self-promotion for ways to connect everyday conduct with a credible professional presence.

AI-assisted researched guidance from PeakBelt. Hypothetical examples are labelled in the text. See our editorial approach.