Career Advocacy

Career advocacy — getting seen, and getting things through

Verified 2026-07-29. Volatile figures live in career-coach/references/market-snapshot-2026-06.md.

0. The term, because it matters

This is not "social engineering". In this library and in security generally, that term means deceiving a person into breaching a control — llm-security and threat-modeling use it that way, and it names an attack. Borrowing it for career work imports the wrong instincts.

The right names are organisational influence, internal advocacy and informal networks — and they are ordinary, legitimate professional skills. Work does not speak for itself, decisions are made by people, and people decide about what they have seen and understood.

The line, and it is a bright one:

The working test: could you say what you are doing, to the person you are doing it to, without the tactic failing? Pre-briefing a stakeholder passes — you can say "I wanted your view before Thursday so I'm not springing it on you." Timing a proposal so a known objector is on leave does not.

Manipulation buys one decision and costs the relationship. In an organisation you may be in for years, and a senior market small enough that people share notes, that is a bad trade even before it is a wrong one.

1. The insight everything else follows from

Decisions are not made in the meeting. They are made in the hours and days before it, and the meeting documents a decision that has largely already happened.

People form views while reading, while thinking, while talking to a colleague they trust. By the time they are sitting in the room with your deck on screen, most of them arrived with a position.

So a proposal that first meets its audience in the meeting is already losing, however good it is. Everything in §2 follows from taking that literally.

2. Pre-wiring a decision

The consulting-firm practice, and it is not exotic: before a recommendation goes to a committee, every decision-maker has already seen it individually and their position is known.

1. Separate who decides from who can veto. They are rarely the same people, and a veto is almost always exercised by someone who was surprised. Map both (career-leadership §4).
2. See each of them one-to-one first. Ten minutes is enough. The purpose is not to present — it is to hear their objection while it is still cheap.
3. Send a short pre-read. People process in writing before they judge in a room, and it is the only way to reach the ones who will not meet you.
4. Change the proposal where the objection is right. Pre-wiring that never alters anything is a sales tour, and people can tell. The visible incorporation of someone's point is what converts them into a supporter — they now have authorship.
5. Know where every attendee stands before you walk in. If you cannot name each person's position, you are not ready; that is a reason to move the meeting, not to hope.
6. Give a supporter something specific to say. "Would you make the delivery-risk point? It lands better from you." Advocates need a line, not just goodwill.

Objections raised in private are cheap; the same objection in the room is expensive, because now it is public, the objector is committed to it, and reversing costs them face.

Where this becomes factionalising: if the pre-wires would look like lobbying against a person rather than toward a decision, you are over the line in §0. The tell is whether you would be comfortable if everyone compared notes — because on a decision that matters, they will.

3. Getting the demo, deck or proposal through the door

• Lead with their problem, not your solution. The first line decides whether the rest is read. "Our reconciliation takes six days and closes late every month" opens; "I've built an AI tool" does not.
• Have a one-paragraph version, a one-slide version and the full version, and lead with the smallest. Senior attention is granted in increments, and the full deck is what you send after someone asks.
• Make the ask explicit and small. "Twenty minutes with you and the ops lead" beats "let me know your thoughts" — a vague ask converts to nothing because nobody knows what agreeing means.
• Who forwards it matters more than what it says. A proposal arriving from a respected internal sender is read; the same document arriving cold is queued. Ask someone to forward it, and give them the sentence to put above it.
• Time it to the cycle. Budget planning, quarterly planning and post-incident windows are when proposals get funded; three weeks after the budget closed is a good idea nobody can act on.
• Show it working. A three-minute demo of something real outperforms twenty slides about something planned, and it converts sceptics that argument does not.
• Name the cost, the risk and what you need. Proposals that omit these read as unserious, and the first question exposes it anyway.

Volunteer for the all-hands slot, the brown-bag, the demo day. These are consistently under-subscribed, they reach exactly the sideways-and-upward audience that matters, and the barrier is willingness rather than permission.

4. Internal channels — Teams, Slack, the intranet

Under hybrid working, proximity bias is real and measurable, and the counter is not being in the office more. It is sharing work beyond your immediate team, in writing, routinely — that correlates with promotion among otherwise equally productive people.

• Post in channels, not DMs. A DM reaches one person once; a channel post is visible, searchable and forwardable. Same effort, different half-life.
• Write the update people can act on. What changed · what it means for them · what you need. Status updates with no "so what" train people to skip you.
• Be useful in other people's channels. Answering a question well in another team's channel is the fastest cross-organisation reputation there is, and almost nobody does it deliberately.
• Convert the thread into an artefact. A Teams answer disappears; the same content as a page people link to keeps working (career-internal-visibility §7).
• Show up in the ambient moments. Turn the camera on for the meeting where decisions get made; join the informal channel; say the useful thing in the pre-meeting chatter. Presence at those is disproportionately what "he/she is around" is built from.
• Do not perform activity. Constant posting with low signal is visible as noise and costs credibility. One substantial thing a week beats five thin ones.

5. Business and industry social events

Set a small, specific goal: three real conversations. "Work the room" produces a pocket of cards and no relationships. Depth converts; breadth does not.

• Prepare, which beats extroversion. Check the attendee list beforehand — most events publish one or run an app — and pick three people worth meeting and why. Preparation is available to everyone; natural sociability is not.
• If you find these draining, your strengths are the right ones anyway. Listening properly and asking a genuinely good question is what people remember; talking most is not. Nobody remembers the person who talked the longest.
• Have a plain-language answer to "what do you do". One sentence, no jargon, ending somewhere the other person can pick up.
• Ask about their problems and listen. It is more useful than pitching and it is what makes the follow-up natural.
• Give something before you need something — an introduction, a reference, an answer.
• Follow up within 24–48 hours, referencing something specific from the conversation. This is the step that separates a contact from a memory, and most people skip it entirely.
• Build the next contact into this one. "I'll send that over — shall we talk again after your launch?" A relationship is several interactions; one is a business card.

Internal social events are work, and worth treating as such. They are where you meet the people two levels up and one department across who otherwise never see you — which is exactly the audience that decides things (career-internal-visibility §1).

6. External platforms, aimed inward

To reach people inside organisations you want to work with, the mechanics are in career-coach/references/linkedin-mechanics.md. The two moves that matter here:

• Comment substantively on the right people's posts. Being replied to by someone widely read puts you in front of their audience — far more reach than posting to your own network, and it reaches the author too.
• Post consistently on the target topic, because distribution is interest-based and topical consistency compounds into being one of the people associated with it.

Warm beats cold, every time. A message referencing a shared connection, a talk you both attended or something they wrote gets a reply; a generic outreach does not.

7. Making the ask

Most advocacy fails at the last step, because nobody was actually asked for anything.

• Specific. "Would you sponsor this at the platform review on the 14th?" not "any support welcome".
• Small and bounded. People say yes to a defined cost. Open-ended requests get deferred, and deferred is a no with better manners.
• Easy to act on. Attach the thing, draft the forwarding line, propose the time.
• Give a deadline and a reason for it. "Before Thursday, because that is when the slate closes."
• Make refusal cheap. "Entirely fine if not" gets more yeses than pressure, and it protects the relationship for the next ask.
• Then close the loop. Tell them what happened. People who never hear the outcome do not help twice.

8. Where this backfires

• Visibility with nothing behind it. Being known for being visible is a short-lived and damaging reputation. Advocacy amplifies work; it does not substitute for it, and the gap always shows.
• Appearing only when you need something. Transactional contact is recognised instantly and remembered.
• Over-claiming shared credit in a public channel where the people who did the work can see it.
• Pre-wiring that becomes lobbying, or a pre-wire framed differently to different people — inconsistency between rooms is the most reliably fatal error here, and people do compare.
• Volume as strategy — posting constantly, attending everything, following up too hard.

9. Anti-patterns

• Calling this "social engineering" and importing the instincts of an attack.
• Letting a proposal meet its audience for the first time in the meeting.
• Pre-wiring without changing anything — a sales tour, and it is transparent.
• Not knowing where each attendee stands before walking in.
• Timing a decision around an objector's absence.
• Leading with your solution instead of their problem.
• Sending the full deck first.
• A vague ask — nobody knows what agreeing to it means.
• DMs where a channel post would do.
• Status updates with no "so what".
• Collecting contacts instead of having three real conversations.
• Skipping the 24–48 hour follow-up, which is where the value was.
• Never closing the loop with someone who helped.
• Visibility exceeding substance.

See also

• business-writing — the pre-read, the covering email, the one-pager and the ask itself. This skill gets the thing in front of the right person; that one makes it land once it arrives.