To reach a distant unit, a sponsor goes through acquaintances, a former colleague or a contact from an old project, who carry information and introductions a close circle cannot.
An example
A product director at a regional telecom carrier needed network engineering to reserve capacity for a business fiber offering she meant to propose. Network engineering sat in another building, reported to a different executive, and answered product requests in about six weeks. Nobody on her team knew anyone there. Going through her contacts, she found a field technician she had worked beside on a storm-recovery rotation four years earlier, now a supervisor in network planning. Over coffee he told her what the planners actually worried about: the new offering would land on aggregation routers already scheduled for replacement. He introduced her to the planning manager, who suggested launching after the router swap. Her proposal went to the investment committee with network planning's capacity estimate attached and the launch moved back one quarter, the first product proposal that year to arrive with network engineering's sign-off.
Why it works
Support gets easier to reach, and the proposal itself is untouched. Close colleagues know what you know and the people you know, so they cannot tell you what a distant unit worries about or open its doors. An acquaintance who sits there can, cheaply: a conversation, a name, a warm introduction that gets the meeting a cold email would not. The proposal changes only if what you learn changes it. What it needs is an acquaintance in the right place who is willing to help, and a request small enough for a thin tie to carry.
The thinking behind it
Mark Granovetter The Strength of Weak Ties (1973) argues that close friends tend to know the same people and the same things, while acquaintances connect otherwise separate groups, so weak ties act as bridges that carry new information across a network. A sponsor's own team cannot say what a distant unit worries about. A former colleague who now sits there can, and the introduction they make crosses a gap no one in the sponsor's close circle spans.
When it fits
Use it when a proposal depends on a unit you have no working relationship with: another function, a distant site, an acquired company, a group under a different executive. It draws on a broad set of past contacts from old projects, rotations, training cohorts, or earlier employers, and on the patience to open with a question before an ask. It works best early, while the proposal can still absorb what you learn.
How to use it well
List everyone you know, however slightly, in or near the unit you need: former teammates, people from old projects, a peer from a training program. Look past rank. A planner or supervisor who knows how decisions get made there is often more useful than a director.
- Ask for information first: what the unit is under pressure from, and what it has said no to recently and why.
- Ask for one introduction, to the person who will shape the unit's answer, and let your contact describe you in their own words.
- Fold what you learn into the proposal before you make the formal request.
- Close the loop: tell your contact what happened, and credit them if they want it.
What it costs and where it backfires
Acquaintances owe you little, so each request draws on thin goodwill; ask too much or too often and the tie goes cold. Your contact's standing in their own unit is at stake when they introduce you, and if your proposal turns out to hurt that unit, they pay for it. Keep it to open introductions and honest questions. Using a contact to collect information their unit has not agreed to share, or to go around its leadership, is no longer networking.
When it is used on you
Proposals from another unit sometimes arrive already shaped by conversations with your people. Find out who talked to whom and what was said; usually it means someone did their homework. If a contact gave away more than your unit had agreed to share, deal with that internally and openly, and make sure formal requests still come through the channel your team owns.