Your network is the reason a decision that should take three weeks takes three hours. When a supplier collapses on a Friday, when a factory line goes down, when the board wants a restructuring plan by Monday, the COO who already knows who to call moves at a completely different speed than the one starting from a cold search.

That is the real point of networking for an operations leader: it is infrastructure you build before you need it. The relationships that matter are not the ones you form at a crisis; they are the ones you already had, warmed up and ready, when the crisis arrived.

This guide treats networking as an operational discipline with the same rigour you'd apply to a supply chain or a hiring plan. It covers the three networks a COO actually runs on, how to tell a strong network from a weak one in daily practice, and the routines that keep relationships alive without turning your calendar into a coffee-meeting factory.

The three networks a COO actually runs on

Most networking advice treats connections as one big pile. A COO's network is really three distinct systems, each doing a different job.

The first is your internal network: department heads, plant managers, finance partners, the engineer everyone quietly relies on. This is where execution lives. The second is your external peer network: other operators who've solved the problem you're about to hit for the first time. The third is your vendor and partner network: suppliers, contractors, and service firms whose reliability is baked into your own numbers.

A weak COO builds only one and neglects the others. Someone who came up through operations often has a deep internal network but no external peers to sanity-check a major decision. Someone hired from outside has a strong external Rolodex but no internal trust, so their directives stall. The job is to run all three at once.

Map yourself against this table honestly. Whichever row is thinnest is where your next quarter of relationship-building should go.

Building an internal network that actually surfaces the truth

The internal network is the one COOs most often assume they have and most often don't. Being in the org chart above someone is not the same as having their trust. The test is simple: do people tell you about problems while they're still small and cheap to fix, or only once they've exploded and there's no hiding them?

Strong internal networks run on informal, low-stakes contact that has nothing to do with reporting lines. Weak ones run entirely on scheduled reviews, where every conversation is a performance and nobody volunteers bad news. If the only time you speak to a warehouse supervisor is when a metric turns red, you've trained the whole floor to keep problems away from you.

The practical fix is deliberate, recurring exposure across levels. Walk the operation. Sit in on a shift handover. Have a standing fifteen-minute check-in with two or three people who are two levels below you, purely to hear what's actually happening. One COO of a distribution business kept a rotating list of a dozen frontline people and had a short conversation with a different one each week. Within a couple of months, she was hearing about equipment problems and process workarounds long before they reached the formal reporting system, which let her fix root causes instead of firefighting symptoms.

This connects directly to how you run the top of the house. The relationship that most determines whether your internal network holds together is the one with the chief executive, because your ability to act on what you hear depends on that alignment. It's worth investing in that partnership deliberately, as covered in the COO-CEO working relationship and reinforced by the broader essential COO skills that hold operations together.

Building an external network that shortens your learning curve

External peers exist to save you from expensive first-time mistakes. Almost every hard operational problem, scaling a plant, integrating an acquisition, moving from regional to national distribution, has already been solved dozens of times by people who'll happily tell you what went wrong if you ask well.

A strong external network is specific and reciprocal. You know operators in adjacent industries and at your own stage of scale, you've given them useful help, and you can call one of them about a concrete problem and get a real answer the same day. A weak external network is a long list of LinkedIn connections you've never spoken to, plus a handful of conference acquaintances whose names you half-remember.

The way to build the strong version is to lead with usefulness. Peer advisory groups and industry associations are the reliable structures here because they create repeated contact around shared problems rather than one-off introductions. But the relationships that stick are the ones where you gave first: you made an introduction, shared a template, warned someone about a vendor before they signed. The value-exchange principle isn't a nicety; it's the mechanism. People remember who helped them and answer that person's calls.

Be concrete about what you're building toward. Pick two or three operational challenges you know are coming in the next year, then deliberately find people who've faced each one. That focus turns "networking" from a vague social obligation into a targeted intelligence-gathering exercise with a clear payoff.

Vendors and partners: the network your numbers depend on

Vendor relationships are where networking and operational risk overlap most directly. A supplier is not just a line item; they are a dependency, and the quality of that relationship shows up in your uptime, your costs, and how fast you recover when something breaks.

Strong vendor networking means you have a genuine relationship with your key suppliers' people, you've pre-qualified credible alternates, and you know who to call for emergency capacity before you need it. Weak vendor networking means a single sole-source supplier you interact with only through purchase orders, whose failure you'd discover the same day it happened, with no backup lined up.

The concrete practice is to treat supplier relationships like the resilience investment they are. Know at least one viable alternate for every critical input, and keep that relationship warm enough that they'd take your emergency call. Maintain a real relationship with your primary suppliers' account teams so that when you need a rush or a favour, you're a known name, not a ticket number. This is the relationship layer underneath a formal vendor management approach, and it's what makes the difference when a disruption hits, which is why it sits at the centre of any serious crisis management plan.

The maintenance routine that keeps a network alive

The hardest part of networking isn't meeting people; it's staying connected without letting it consume your week. A network decays if you only reach out when you want something. The fix is a lightweight system, not more coffee meetings.

Strong maintenance looks like a simple tracked list of your most important relationships with a note on when you last spoke and what matters to that person. Weak maintenance looks like relying on memory, which means you contact people only in bursts of need and let the rest go cold. A basic CRM or even a spreadsheet does the job; the tool matters far less than the discipline of using it.

Build the touchpoints into your existing rhythm rather than adding new obligations. When you read something a contact would find useful, send it, no ask attached. When someone's company hits a milestone, note it. A useful frame is to aim for several no-ask contacts for every request you make, so that your relationships aren't purely transactional. Working this into your normal week, rather than saving it for a quarterly networking sprint, is what makes it sustainable, and it fits naturally into a well-structured COO daily routine.

How to know it's working

Networking resists measurement, but you can watch for real signals rather than vanity metrics. The number of connections you have tells you almost nothing. What tells you something is speed and access: when a problem lands, how quickly can you reach someone who can genuinely help?

Track a few honest indicators over time. Are you hearing about internal problems earlier than you used to? When you face a new operational challenge, do you have a peer to call, or are you starting from a blank page? When a supplier wobbles, do you have an alternate ready? A network that's working shows up as decisions made faster, risks caught earlier, and fewer moments where you're stuck because you don't know who to ask. That access is a genuine operational advantage, and it compounds with the stakeholder relationships and board communication you build alongside it.

Key takeaways

• A COO's network is operational infrastructure you build before you need it, not a business-card collection to grow for its own sake.
• Run three distinct networks at once: internal (execution), external peers (borrowed lessons), and vendors/partners (capacity and resilience). Whichever is thinnest is your priority.
• A strong internal network is measured by whether people tell you about problems while they're still small; that requires deliberate, informal contact across levels, not just status meetings.
• External peers exist to save you from first-time mistakes; build the network by leading with usefulness and targeting the specific challenges you know are coming.
• Vendor relationships are a resilience investment: keep pre-qualified alternates and warm relationships so you're a known name when you need a favour.
• Maintain the network with a lightweight tracked system and several no-ask contacts per request, worked into your normal week rather than saved for a sprint.

Frequently asked questions

How is networking for a COO different from networking for other executives?

A COO's network is weighted toward execution and risk rather than deals or fundraising. A CEO or CFO networks heavily for capital, investors, and market positioning; a COO networks for people who can help things get done and for early warning on operational risk. That means the internal network and the vendor network carry unusual weight, because both directly affect uptime, cost, and delivery, the numbers a COO is accountable for.

I came up internally and don't have an external network. Where do I start?

Start with one or two peer advisory groups or industry associations relevant to your sector, and go in with the goal of being useful rather than collecting contacts. Pick two operational challenges you know are coming in the next year and deliberately seek out people who've already faced them. A handful of real, reciprocal relationships with operators at your stage will do more than hundreds of passive connections, and they're far faster to build when you lead with help.

How much time should a COO realistically spend on networking?

Less than most advice implies, if you build it into your existing routine instead of treating it as a separate activity. The high-leverage version is a few short internal check-ins a week, sending useful things to external contacts as you come across them, and keeping vendor relationships warm through normal business contact. The goal is steady, low-intensity maintenance, not periodic sprints that swing between neglect and overload.

How do I keep an internal network from turning into politics or favouritism?

Keep the purpose explicit: you're building informal contact to surface truth and speed execution, not a private circle of allies. Rotate who you talk to across levels and departments so no one group becomes your only source, and act on what you hear in a way that's visibly fair. When people see that talking to you leads to problems getting fixed rather than to insiders getting advantages, the network stays healthy.

What's the single biggest networking mistake COOs make?

Only reaching out when they need something. A network built on requests decays fast, because people learn that your call means work for them. The fix is leading with value, making introductions, sharing intelligence, and offering help well before you ever ask for anything, so that when you do need a favour, the relationship can carry it. The second most common mistake is neglecting vendor relationships until a supplier fails, at which point there's no time left to build the alternate you should have had ready.