The error is not being shy

The networking myth says the problem is not daring to speak. In practice, the damage is done by sociable professionals who collect contacts and do not build a channel. Shyness shows in a room. Abandonment shows a week later, when nobody wrote. The second error is more expensive and more common.

The failures below are not minor etiquette. They are system failures: identity, capture, judgment and follow-up. They can be corrected without becoming someone else. They are corrected by deciding what happens after the tap.

Collecting without recording

The most common error is treating the exchange as a trophy. The profile is shared, the QR is scanned, a screenshot is saved, and the detail sits in limbo: no CRM, no note, no owner. When the salesperson changes teams, the relationship leaves with the personal phone. The company believes it has a network. It has a set of screenshots.

Recording is not bureaucracy. It is the only way the meeting survives the person who made it. Anyone who resists entering the contact into the system usually also resists writing the reason to return. Without both, there is no transferable network.

Talking about yourself and not asking

The second error is using the meeting as a stage. A monologue about your own company creates no obligation to reply. A precise question —what they are trying to solve, who else is involved, what failed before— does. Extractive networking is recognized at once: the other party feels they are an audience, not a counterpart.

The correction is simple and hard to sustain: talk less, write more down. The note is not for the archive. It is the raw material of the 72-hour message. Without it, follow-up is invented and sounds like a template.

Letting the 72 hours pass

Silence beyond 72 hours forces you to introduce yourself again. The other person no longer has the thread. The late message needs a reconstruction paragraph that the punctual one does not. That cost is paid by the person who arrived late, not by the recipient.

  • Not writing because “there is no proposal ready” —thanks plus a sentence from the meeting is enough.
  • Writing three weeks later with a generic sales argument.
  • Handing follow-up to an agent without controls and letting the tone fail to match the meeting.

The error is not using help to draft. The error is that the text could not be signed by the person who was at the table. Gartner in 2026 insists on a trust harness for sales AI for this reason: an agent without limits industrializes the hollow message.

Treating every contact the same

A flat list is another classic error. Not every meeting deserves the same cadence. Some people decide. Some recommend. Some inform. Some do not fit and should be archived without guilt. Treating everyone as a funnel for the same week exhausts the team and bothers anyone who did not ask for persistence.

The criterion is written down. If it is not written, Friday’s mood decides: you persist with whoever felt likable and forget whoever was relevant. That is not networking. It is emotional weather dressed up as method.

How to correct the habit

The correction fits in a short ritual. The same day: enrich and record. Within 72 hours: a message with context. Once a month: review who deserves an introduction, silence or a file. If the team cannot sustain that ritual, the next event is not the problem. Operations are.

The most common professional-networking errors look alike: they turn the other person into a collection object. The correction looks alike too: return them to the status of counterpart —with memory, punctuality and judgment—. The rest of the room advice is secondary.