Core premise: Networking is the purest form of leadership development available. Unlike 360 feedback (which builds self-knowledge), coaching (which builds behavioural change), or mentoring (which builds sponsorship), networking builds one thing almost exclusively: social capital. And its effects are durable — the supplied research showed that peer networking relationships can span 20 or 30-year careers, far longer than any mentoring or coaching engagement. This article unpacks the structural-holes concept described in the source, the source's weak-ties finding, and the specific reason networking is a defence project manager's most underrated career investment.
1. The "Why" — Knowing Who Beats Knowing What
Two senior project managers at a defence prime have identical technical credentials and identical years of experience. Both are asked to resolve a thorny interface issue between a combat system sub-contractor and an integration lead at a second-tier partner. The first project manager works the problem through official channels — formal meetings, written queries, escalation logs. Three weeks later, the interface is still unresolved.
The second project manager picks up her phone, calls a counterpart she met at an professional project association national conference eighteen months ago, who in turn introduces her to the right technical authority at the sub-contractor. The issue is resolved in four days.
The difference is not intelligence. It is not technical skill. It is who each project manager knows, and how their knowledge is distributed across the organisational landscape. This is networking — and the supplied research argues it is one of the most powerful and least intentional forms of leadership development in use.
Practice note: The Core Insight Networking is about developing leaders beyond merely "knowing what" and "knowing how," to "knowing who" in terms of problem-solving resources. It is also about expanding one's definition of what and how through exposure to other ways of thinking — challenging the basic assumptions we do not know we hold.
2. The "What" — Networks, Ties, and Capital
Practice note: Definition Networking (as a leadership development practice) refers to the intentional development of connections across functional, organisational, or geographic boundaries, with the goal of building social capital in the form of accessible knowledge, sponsorship, and cross-pollination of ideas.
2.1 Where It Fits in the Development Framework
Networking's primary contribution is support — the psychosocial and informational backup that comes from a wide circle of peers and contacts. Its challenge content is moderate (exposure to different thinking) and its formal assessment content is minimal.
2.2 Strong Ties and Weak Ties — source insight
The supplied research The Strength of Weak Ties is one of the most-cited papers in modern sociology, and it reframes how we think about network value:
| Tie Type | Characteristics | What It Provides |
|---|---|---|
| Strong ties | High-frequency contact, emotional intimacy, mutual confiding, reciprocal services | Loyalty, trust, mutual respect, deep commitment, emotional support |
| Weak ties | Infrequent contact, more acquaintance than friendship, minimal emotional investment | Access to novel, unique, non-redundant information from different parts of the social structure |
The counterintuitive finding is that weak ties are often more valuable than strong ties for certain purposes — particularly information flow and opportunity access. Why? Because your strong ties mostly know what you already know. Your weak ties know things you don't.
The supplied research apply this directly to leadership:
Practice note — supplied research: "Effective leadership requires establishing strong and weak ties, both of which are crucial but serve different purposes. Strong ties build loyalty, trust, and mutual respect — essentially, commitments among individuals — whereas weak ties provide access to novel, unique, and nonredundant information or resources."
2.3 the supplied research Structural Holes — Where Real Network Value Sits
The structural-holes concept described in the supplied research argues that the highest-value network position is one that spans a gap between otherwise disconnected groups. A structural hole is a gap in the social structure — two people who could benefit from each other's information or resources but are not connected. The person who bridges the hole gains disproportionate advantage.
The yellow node above bridges three otherwise disconnected clusters. That node's holder sees information from all three, can broker introductions between them, and has a structural advantage that none of the cluster-embedded actors possess. On a defence acquisition programme with a prime, acquisition authority, government technical authority, and multiple sub-contractors, the project manager who bridges structural holes between these organisations holds a position of enormous latent value.
The supplied research puts it plainly:
Practice note — supplied research: "Managers who build the kinds of networks that allow them to transcend the organisation's formal structure — especially when they form non-redundant ties with people in other networks — are most likely to benefit in terms of information and entrepreneurial opportunities. Managers embedded in a limited network with many redundant ties will not experience these same benefits."
2.4 Peer Relationships — The Underrated Long Game
The supplied research examined peer developmental relationships and found something striking:
Practice note — supplied research: Peer relationships can span an entire 20- or 30-year career — far longer than:
- a typical mentoring relationship
- an executive coaching relationship
This makes peer networks the most durable form of developmental relationship available.
On a defence career that may span complex capability programme, LAND 8116, complex naval-platform programme, and whatever comes next under the next sector strategy review, peer relationships built early persist through every programme transition. The graduate engineers you meet at an early professional project association chapter event may be your sub-contractor technical leads, customer representatives, and alliance partners twenty years from now.
3. The "How" — Three Real Networking Initiatives
The supplied research reviews three specific programme examples that illustrate different approaches to intentional networking.
3.1 a global professional-services organisation's Worldwide Organisation Executive programme
A five-day seminar designed around global partner networking. Partners from different practice areas and regions were brought together to meet, exchange views, and strengthen personal networks as a means of creating entrepreneurial opportunities. The goal was not content delivery — it was the construction of cross-boundary weak ties.
3.2 a technology organisation's executive peer-network programme
The executive peer-network programme had three overall goals:
- Teach VPs about the company's unique heritage and culture
- Help them explore new ways to invent new technologies and businesses
- Foster networking
Note the explicit naming of networking as a goal, not a side-effect.
3.3 a technology organisation's virtual leadership network
A technology organisation used its own advanced video and data-networking technology to run a monthly leadership academy simulcast to offices in 47 countries with simultaneous translation from English into Spanish and Portuguese. Managers could call in with questions and get real-time responses. The programme reinforced a core organisational value that "technology is about elevating, not replacing, human interaction."
For a globally dispersed defence alliance (multinational advanced-capability partnership, intelligence-sharing partnerships, multinational defence alliance interoperability programmes), a technology organisation model is prescient — networking at scale through structured virtual forums, accepting that face-to-face ideal will not always be possible.
3.4 Peer Affinity Groups
A variant that deserves attention: groups of managers with common training or job experiences meeting regularly — over lunches, through electronic dialogue, or in structured peer forums — to share challenges and apply their learning. These are informal, ongoing, and cheap, and they produce some of the most persistent developmental relationships in an organisation.
3.5 the supplied research Propositions 4a and 4b
Practice note — source Propositions 4a and 4b: 4a: "Networking opportunities build peer relationships across functional areas, leading to the creation of additional social capital."
4b: "When used in conjunction with other developmental practices, networking links individual leader development with collective leadership development."
Proposition 4b is the key integrative claim. Networking on its own builds the raw material — contacts and ties — but it needs to be combined with feedback, coaching, and real-work assignments to convert that raw material into developmental impact. Networking is the connective tissue of an integrated leadership development system, not a standalone programme.
4. The Pitfalls — Where Networking Goes Wrong
- Networking as cocktail-party performance. Events that optimise for ritual attendance over genuine relationship-building produce no social capital.
- Redundant ties, not new ones. Building deeper connections with people you already know does not add structural capital — you need to reach into different clusters.
- Optimising only for strong ties. Strong ties are valuable but produce redundant information. Weak ties are often where the new information lives.
- No intrapersonal foundation. the supplied research explicitly warns: "A manager needs the appropriate self-awareness, motivation, and self-regulation skills (intrapersonal competence), in addition to a well-defined set of developmental and strategic objectives, to benefit maximally from networking opportunities." Networking without self-knowledge produces transactional contacts, not developmental relationships.
- Quantity over quality. a professional profile network of 3,000 names means nothing if none of them would take your call.
- Ignoring weak ties in favour of deepening existing relationships. The easy temptation is to spend time with the people we already like. The developmental return is higher when we spend time with people we barely know.
- Treating networking as a standalone intervention. Proposition 4b is clear: networking produces its highest return when linked to feedback, coaching, mentoring, and developmental assignments.
- Ad hoc and unstructured. the supplied research notes that networking's main weakness is that it is typically unstructured, which means its developmental value is unpredictable and hard to evaluate.
5. Key Takeaways
Practice note: Seven Things to Remember
- Networking is the purest social capital investment of any developmental practice.
- Strong ties build commitments; weak ties provide novel information. Both matter, and they serve different purposes.
- Structural holes are where the value is. Being the person who bridges disconnected clusters gives disproportionate access and influence.
- Peer networks are durable. the supplied research shows peer developmental relationships can span 20–30 year careers — longer than mentoring or coaching.
- Intentionality matters. Networking programmes succeed when they are explicit about the goal, not when they are hidden inside "leadership events."
- Networking alone is insufficient. It links leader and leadership development when combined with other practices (Proposition 4b).
- Intrapersonal foundation first. Without self-awareness and clear developmental goals, networking produces transactional contacts rather than developmental relationships.
6. Knowledge Check
Practice note: Test Your Understanding
- Explain the supplied research strength-of-weak-ties finding in your own words. Why are weak ties often more valuable than strong ties for information flow, and what are the implications for a project manager building a professional network?
- Draw or describe a structural hole in the context of an Australian defence acquisition programme. Who are the disconnected clusters, what is the hole between them, and what advantage does the person who bridges the hole possess?
- The supplied research argues that networking alone is insufficient for leadership development (Proposition 4b). Why does networking need to be combined with feedback, coaching, and assignments to produce its full developmental effect?
- The supplied research found that peer networking relationships can span 20–30 year careers, compared with 3–6 years for mentoring and ~6 months for coaching. What does this durability difference imply for how early-career project managers should allocate their developmental effort?
- A defence prime runs an annual "Leadership Connect" event where managers from different sites gather for two days of presentations and networking dinners. After three years, exit surveys show high satisfaction but no measurable developmental outcomes. Using the supplied research pitfall list, diagnose the likely design failures.
Applying the Guidance as a Controlled Practice
Use this subject as a decision aid, not as a label applied after the event. Start by defining the delivery problem, the people affected, the authority available and the consequences of a poor decision. Record assumptions before selecting an intervention. That simple discipline makes later review possible and prevents a preferred leadership style from being treated as the answer to every situation.
Six-Step Application Cycle
- Define the trigger. State the decision, behaviour, team condition or delivery risk that requires attention. Separate observation from interpretation.
- Map the context. Identify the project phase, task uncertainty, dependencies, stakeholder interests, time pressure, team capability and formal authority.
- Choose a proportionate response. Select the smallest intervention capable of improving the condition. Explain why it fits the evidence and what alternatives were rejected.
- Agree ownership and boundaries. Make decision rights, escalation points, review dates and non-negotiable safety or ethical limits visible to the people involved.
- Act and observe. Monitor both delivery indicators and human signals such as challenge, information sharing, participation, trust and follow-through.
- Review and adapt. Compare the result with the original intent. Retain, adjust or stop the intervention, and capture the learning for the next phase.
Evidence and Verification
| Required record | Purpose | Verification question |
|---|---|---|
| Project network map | Makes the selected approach and its basis visible. | Can an independent reviewer understand why this response was chosen? |
| Relationship-development plan | Translates intent into owned actions, interfaces or boundaries. | Does every critical action have an owner, timing and escalation path? |
| Network risk and ethics check | Preserves evidence of follow-through and learning. | Does the record show what changed, what did not and what happens next? |
Evidence should be proportionate to the project's risk and governance needs. A short decision note may be sufficient for a routine team adjustment; a high-consequence change may require sponsor approval, formal consultation, controlled records and a scheduled assurance review. Documentation must support judgement rather than replace it.
Review Questions
- What observable condition are we trying to change, and how will we know if it improves?
- Whose perspective is missing from the diagnosis or decision?
- Are authority, accountability and capability aligned, or are we asking someone to own an outcome they cannot control?
- Could the intervention suppress challenge, conceal risk or create dependency on one individual?
- What evidence will trigger escalation, adaptation or closure?
Practice boundary: Frameworks in this article organise thinking; they do not guarantee performance. Project context, contractual obligations, safety duties, workplace requirements and approved governance remain controlling.