Overview

Before adding contacts, identify the specific resource need, test whether current relationships cover its knowledge, separate availability from activation, and assess whether the exchange changes a decision. Familiar problems may favor deepening; specialized gaps may require broadening. The checkpoint recommends small, reversible tests rather than an unlimited-network prescription.

Learning outcomes

Define the decision-level resource need before judging whether the network is too small.
If relevant knowledge is present, test activation; if it is absent, broaden toward a fitting channel.
A useful diagnostic records advice, a referral, a refined question, silence, or evidence that the assumed fit was wrong.

Keywords

bottleneckdiagnosiscoveragefitactivationexpertise

Checkpoint: Diagnose the Bottleneck Before You Add Contacts

For founders deciding whether to change their networks, four connected questions matter: can they reach a relevant person, is the needed knowledge available, can the relationship be activated, and does the exchange produce advice they can use? This checkpoint brings those questions together around two contrasting founder problems. Its purpose is practical judgment: choose whether to deepen an existing relationship or broaden the network only after identifying the stage at which support is failing.

A network problem is rarely announced in that vocabulary. It usually arrives as a complaint—“I know plenty of people, but nobody can help with this”—or as an impulse—“I should go to more events.” The complaint may describe missing expertise, a dormant relationship, an unclear request, or advice that does not fit the decision. The impulse may solve the wrong problem. Diagnosis is what turns a general networking intention into a small, testable choice.

A single diagnosis for a messy support problem

Start with the resource need, not with the network. “I need more support” is too broad to identify a person or a channel. A founder might instead need an informed challenge to a pricing assumption, an introduction to a specialist, guidance through an unfamiliar regulatory requirement, or information about a possible source of finance. The more specific the need, the easier it is to ask whether the current relationships contain relevant knowledge.

The next question is about coverage. Do existing ties include people who understand the domain of the problem? If yes, the likely issue is not reach. The founder may have relevant advice available but not yet activated the tie. If no, the issue is not that the current relationships are insufficiently friendly. The network’s knowledge domain is misaligned with the need, so broadening becomes a more plausible response.

Coverage is not the same as certainty. A founder may think a contact can help and discover that the person’s experience is less relevant than expected. Conversely, a person who is not an obvious adviser may know someone who is. The diagnostic value lies in making the assumption visible. “This person probably knows” is a testable belief; “my network is too small” is often only a conclusion drawn from frustration.

If the knowledge is present, examine availability and activation separately. Is the person likely to help if asked? Has the tie been maintained well enough for a request to be intelligible and welcome? Has the founder actually made a clear request? A relationship can be resource-rich in principle while remaining dormant in practice. It can also be active in a social sense without carrying the specialized knowledge the founder needs.

If the knowledge is absent, ask whether a new contact can be reached through an existing tie, a professional setting, or another channel. This is broadening in response to a fit problem, not broadening for its own sake. The founder’s objective is to find a relevant route to expertise.

Published by DeepMox

FAQ

How should a founder define a network problem before seeking contacts?

Define the specific resource need at the level of a pending decision, such as a pricing judgment, specialist introduction, regulatory guidance, or finance information.

What does it mean if current relationships do not cover a founder’s problem?

It indicates a knowledge-fit gap, so broadening through a relevant new contact or channel is more plausible than repeating the request within the same circle.

How can a founder test whether activation is the bottleneck?

Make one specific request to a relevant, reachable tie and observe whether it produces advice, a referral, a refined question, silence, or no usable exchange.

Previous8 minFounder Networks: Two Routes to Useful Advice

Next9 minFounder Networks: Social Skills and Advice Conversion

Founder Networks: Diagnose Before Adding Contacts

Checkpoint: Diagnose the Bottleneck Before You Add Contacts

A single diagnosis for a messy support problem

FAQ