Soft Landing · Chapter 11 · Context Before Contact

The Network Activation Workflow

Networking after a layoff can feel like putting your private ledger on the reception desk. You aren't confessing. You're making one bounded professional ask and leaving the other person room to say no.

Output: One bounded outreach sequence and one follow-up boundary.

Readiness0/5 ready

ContextContext open

Message0/9 checks

PromisesUnresolved

Cycle0/7 counts

The sequence still has an open boundary.

Next: record the Professional narrative, all five readiness answers, and a sustainable capacity limit.

The six-step workflow

The templates can help with structure. They don't get to invent the relationship.

1. Pass the readiness gateOpen

2. Map relationship contextOpen

3. Choose an optional templateOpen

4. Run the message checksOpen

5. Track the relationshipOpen

6. Close promises and review the boundaryOpen

1. Pass the readiness gate

Read the Chapter 8 Professional version aloud. If bitterness, disclosure risk, or emotional flooding changes the purpose, pause external outreach.

Chapter 8 Professional versionI read this version aloud once. It is factual, professional, and inside the privacy boundary.

Can you state what happened without invented euphemism or unnecessary private detail?

Can you state the target without pretending certainty you don't have?

Can you discuss the former employer without turning the recipient into an investigator, witness, or therapist?

Can you receive a no or no response without retaliating or escalating?

Can you ask a specific question and listen to the answer?

Pause external outreach. A no or unresolved answer keeps sending locked. Use the safe preparation list instead.

Safe work during a pause

Verify target companies from current public sources
Build the contact map without sending messages
Prepare questions and test the Professional narrative with a trusted person
Review agreements or professional-support routes when the boundary is unclear

Capacity boundary

There is no universal message quota. Set a volume you can research, send, and maintain without leaving promises open. Hours are capacity, not a demand to fill every inbox.

Maximum new messages before the reviewMaximum open promises I can maintainNext capacity review date

2. Map relationship context

Use actual shared work, current facts, legitimate contact records, and the smallest ask this relationship can carry.

Use only records you're authorized to keep. Don't export a former employer's contact database, copy restricted customer information, or contact someone when an agreement, investigation, representation boundary, or known request prohibits it.

NameRelationship distanceHow we know each otherWhat they directly observed about my workWhat I know about their workLast meaningful contactCurrent role and sourceConflict, privacy concern, or contact restrictionWhat I can offer or answer truthfullySmallest useful ask

Relationship context, not title or presumed influence, determines the message and the ask.

3. Choose the smallest useful ask

Use a source template only when it fits. The message still has to sound like you and every fact still has to be true.

InformationAsk for one factual distinction or market term.PerspectiveAsk what problem or pattern became visible from their seat.ConversationAsk for a brief, bounded conversation about one topic.ConnectionAsk for a connection only when the conversation supports it and a decline is easy.ReferralAsk only when the person knows enough about you and the role to act honestly.

The person knows enough about me and the role to make a referral honestly. Referral is locked until the person knows enough.

Optional source templates

Close professional contact

[Name], I wanted to let you know that [truthful transition sentence]. I am targeting [specific role or problem]. You have seen my work in [relevant context]. Would you be open to [specific question or bounded conversation]?

Professional acquaintance

Hi [Name]. We know each other from [specific context]. I saw [verified relevant observation]. [Truthful Professional transition sentence.] I am exploring [specific target]. Would you be open to [narrow question or brief conversation]?

Distant connection

Hi [Name]. We haven't met directly. [Mutual context or specific work that makes the contact legitimate.] I work in [truthful function and scope] and am researching [bounded topic]. Would you be open to [small request]? If not, no response is needed.

My message

A vague note makes the recipient design the conversation before deciding whether to accept it. That's not personalization. It's unpaid project management.

4. Run the message checks

Verify the context, transition, observation, target, ask, privacy boundary, easy decline, natural language, and follow-through.

Relationship or legitimate context is accurateTransition sentence matches Chapter 8Recipient-specific observation was opened and verifiedTarget is clear enough to routeAsk matches relationship distanceNo confidential or unnecessary private detail, and no request for confidential employer information, appearsDecline or silence remains easyLanguage sounds like you when read aloudYou can complete the likely follow-through

Message locked by the readiness gate.

5. Track the relationship

Record the response, useful information, promises, next action, and conversation quality without turning private context into a public lead.

NameContextDate sentResponseConversation dateUseful informationPromise I madeNext actionNext dateStatus

Every promise recorded above is closed. Close your own promises before asking for an introduction.

Tracking is open. Match the status to the dates, response, promise, next action, and follow-up boundary.

Conversation quality

If a conversation date is recorded, all four notes are required.

Fact learnedInferenceActionBoundary

One-follow-up boundary

Use no more than one follow-up when a legitimate reason exists. Keep the original purpose visible, use the original channel, make declining easy, and mark the entry inactive after silence.

The recipient invited a follow-up.The original message had legitimate context and may have been missed.You owe an item or update you promised.New information materially changes the reason for contact.

Follow-ups sentFollow-up dateOriginal channelFollow-up message

The follow-up keeps the original purpose visible and makes declining or silence easy.

6. Close promises and review the boundary

Every two weeks, count what happened, close your own promises, correct factual trouble, and decide whether the next cycle should keep, reduce, or redirect volume.

Cycle startTwo-week review date

Blank review counts stay unresolved. Enter an explicit count, including zero. No universal message quota turns ten messages in someone else's example into your weekly obligation.

Messages sentSubstantive responsesConversationsRelevant informationIntroductionsPromises still openMessages requiring correction

Did any message create regret or disclosure risk?If yes, which message type and what must stop or be corrected?Next cycleNext weekly message volumeEvidence and rationale

Record the cycle start and review date.

Ask ladder reference

Information

Ask for one factual distinction or market term.

Perspective

Ask what problem or pattern became visible from their seat.

Conversation

Ask for a brief, bounded conversation about one topic.

Connection

Ask for a connection only when the conversation supports it and a decline is easy.

Referral

Ask only when the person knows enough about you and the role to act honestly.

Recruiter-channel boundary

Keep recruiter work in Chapter 9's separate channel, even when the same tracker records the relationship.

Completion test

Pass all five readiness questions, map one legitimate relationship, draft one specific message, pass all nine message checks, set the tracking and follow-up boundary, and record a dated two-week review with explicit counts, including zero.

Monday Move

Choose one person with real shared context. Write the cause of resistance beside the name, set the smallest useful ask, and stop after one truthful message. A connection count isn't a contact map. It's just a large number wearing business casual.

This workflow stays in this browser with LocalStorage until you clear it.