LinkedIn Thought Leadership Post — Golden Examples
How to Use These Examples
Each example is annotated with structural notes, distribution mechanics, and status analysis. Study the architecture AND the distribution design — what generates dwell time, what generates comments, what makes engaging a status-positive act.
Example 1: Pattern Call-Out
Angle: Pattern Call-Out Hook type: Scene Length: ~350 words (~1,700 characters) Core insight: 80% of advisory work is invisible to clients. They judge the service by the 20% they see. Status signal: Reader who engages is signaling "I think about client perception as a system, not just service quality."
A wealth advisor lost her second-largest client last year. ← HOOK: Scene. Specific. Gap created.
The exit email said: Above the "See more" fold.
"The service just isn't what it used to be."
Nothing had changed. ← THE TURN: Two words. Maximum dwell time —
Investment philosophy was the same. reader slows down here.
Returns were steady.
Same team.
What changed was invisible. ← REFRAME LANDS
When the client first came on, the advisor handled ← PATTERN: Escalating specifics.
everything personally. Each line is more concrete than the last.
Pre-meeting research. Dwell time increases with each detail
Post-meeting summaries. because the reader is recognizing themselves.
The call about their kid's college fund.
The text before a volatile week.
As the practice grew, those touches got delegated. ← MECHANISM: How the pattern operates.
Then dropped.
The client never saw the 6 hours of quarterly prep. ← INVISIBLE COST: Three specifics.
The tax-loss harvesting analysis stayed invisible.
3 rejected options that led to the final
recommendation — never mentioned.
They saw fewer personal touches. ← CONSEQUENCE
And concluded the service had declined.
80% of what you do is invisible to your clients. ← CLOSER: Quotable. Specific ratio.
The 20% they see determines whether they stay. Screenshot-worthy.
When a client says "the service changed" —
the service didn't change.
What they could see did.
What's the invisible 80% in your practice that ← CONVERSATION PROMPT: Experience mirror.
your clients never see? Status-positive to answer — the reader
demonstrates expertise by describing
their own invisible work.Distribution Analysis
Dwell time drivers:
- "Nothing had changed" creates a pause — reader slows to understand the contradiction
- Escalating specifics ("kid's college fund," "text before a volatile week") are vivid enough to picture, which increases reading time
- The post is ~1,700 characters — in the optimal range for completion rate
Comment generation:
- The conversation prompt ("What's the invisible 80%?") invites multi-sentence answers because the reader has to describe their specific work
- Answering makes the commenter look competent — they're demonstrating the depth of their own practice
- High potential for comment threads: one person's answer reminds another person of their own version
Status mechanics:
- Engaging signals: "I think about client perception at a systems level, not just a service level"
- Sharing/reposting signals: "I understand something about advisory work that most practitioners miss"
- Commenting signals: "My practice has depth and complexity that my clients don't see" (expertise display)
Example 2: Contrarian Take (with Hand Raiser CTA variant)
Angle: Contrarian Take Hook type: Claim Length: ~300 words without CTA (~1,500 characters) Core insight: Charm on a triage call predicts bad client outcomes. Discomfort predicts good ones. Status signal: Reader who engages is signaling "I use systems and data for prospect evaluation, not gut feel."
Your most charming prospect is your biggest risk. ← HOOK: Claim. Counterintuitive. Must verify.
Here's what a typical "great first call" sounds like: ← VALUE BODY: Reader recognizes the pattern.
"This is exactly what we need!"
(agreed with everything)
"Our last consultant just didn't get it"
(blamed everyone)
"Just tell me the price"
(resented the cost before hearing it)
"Can you just handle it? I'm swamped"
(won't engage)
"I love your approach"
(never described their actual problem)
Feels great in the moment. ← SCORING REVEAL: New framework introduced.
Scores a 2 across the board.
2s become scope creep. ← CONSEQUENCE CASCADE: Deliberate repetition.
2s become payment chasing. (copy-qc.md Pattern 2 exception: data pattern)
2s become "I'm disappointed in the partnership."
Now compare: ← THE FLIP
"I'm skeptical, but I'm here because
the problem is real."
Feels uncomfortable.
Scores a 5.
5s become retainers.
5s become referrals.
5s become "What else can you help with?"
Politeness is a social skill, not a buying signal. ← CLOSER: Principle. Quotable.
What's the phrase you hear on triage calls that ← CONVERSATION PROMPT: Specific ask.
sounds like a green light — but isn't? Answering requires real experience.
Status-positive: reader demonstrates
pattern recognition from their own calls.Distribution Analysis
Dwell time drivers:
- Five dialogue examples, each with a parenthetical decoder — reader processes each one
- The flip structure (2s vs 5s) creates a comparison the reader must read through completely
- ~1,500 characters — solid range for completion
Comment generation:
- The conversation prompt ("What phrase sounds like a green light but isn't?") generates highly specific answers
- Each answer is a mini-story from the commenter's own experience — multi-sentence, substantive
- High thread potential: readers will recognize each other's examples and riff
Status mechanics:
- Engaging signals: "I evaluate prospects with rigor, not vibes"
- Commenting signals: "I've seen enough triage calls to have real pattern recognition" (experience display)
- The scoring framework (2s and 5s) gives the reader vocabulary they can use in their own conversations — that's the status transfer
Note on Hand Raiser Variant
This post can run as pure thought leadership (ending at the closer + conversation prompt) OR as a hand raiser (replacing the conversation prompt with a CTA: "I built a decoder for this. Comment TRIAGE and I'll send it."). See the Hand Raiser kit for the CTA version. The body is identical — only the ending changes.
Example 3: Reframe
Angle: Reframe Hook type: Pattern Length: ~280 words (~1,400 characters) Core insight: Delegation fails in advisory practices because the process lives in the founder's head. The team isn't underperforming — they're guessing. Status signal: Reader who engages is signaling "I think about delegation as a systems problem, not a people problem."
Most practice owners who delegate work end up ← HOOK: Pattern. Names something recognizable.
doing it twice. Above the fold. Gap created — reader needs
to know why.
The pattern looks the same every time.
You hire the associate advisor. Spend 3 weeks ← SETUP: Specific enough to picture.
training them — shadow sessions, review Escalating investment makes the payoff
walkthroughs, Friday debriefs. feel earned.
Hand off client prep, follow-ups, quarterly reviews.
Two months later, you're re-prepping every client ← THE COST: Concrete details increase
file the night before. Rewriting follow-up emails dwell time. Reader recognizes themselves.
before they go out. Reviewing quarterly decks
line by line.
The conclusion: bad hire. ← OLD FRAME: One line. Common belief.
The hire was fine. ← THE PIVOT: Four words.
The process — the actual sequence of decisions, ← NEW FRAME: Names what's really happening.
the judgment calls, the priority logic — lived
entirely in your head. The associate had nothing
to follow except your corrections after the fact.
Which clients get a personal call after a volatile ← ESCALATING SPECIFICS: Three operational
week? How does a quarterly review get prepped — decisions the reader makes unconsciously.
which reports to pull, which benchmarks to Each one is more specific than the last.
highlight, which life changes to ask about?
When does a prospect follow-up shift from
nurture to close?
You've made those calls in real time for 8 years. ← MECHANISM: Why it stays invisible.
Never documented. Never had to.
The associate improvised. You corrected. ← THE CYCLE: Compressed repetition.
They adjusted. You corrected again.
The work kept routing back. The associate was ← REFRAME LANDING: No twinning structure.
capable — running their version of a process that States the real cause directly.
was never written down.
That cycle doesn't break with a different hire. ← CLOSER: Quotable. Specific. Actionable.
It breaks when the process exists somewhere
outside your memory.
What's the process in your practice that only ← CONVERSATION PROMPT: Experience mirror.
works when you're the one doing it? Status-positive: answering demonstrates
the reader's awareness of their own
operational architecture.Distribution Analysis
Dwell time drivers:
- "Two months later" creates a timeline the reader follows — they're invested in the outcome
- The three operational questions (volatile week call, review prep, nurture-to-close) are specific enough that the reader pauses on each one to check against their own practice
- ~1,400 characters — at the lower boundary of the sweet spot but the concept is tight enough to work
Comment generation:
- The conversation prompt ("What process only works when you're the one doing it?") invites multi-sentence answers because the reader has to describe a specific workflow
- Answering is status-positive: the reader demonstrates awareness of their own operational architecture
- High thread potential: practice owners will recognize each other's bottlenecks and compare notes
Status mechanics:
- Engaging signals: "I diagnose delegation failures at the systems level, not the people level"
- Commenting signals: "I'm self-aware enough to name where my practice depends on my personal presence"
- Sharing signals: "I think about infrastructure, not just effort — and I want my network to know it"
Copy QC Notes
- "The conclusion: bad hire." / "The hire was fine." — Not twinning. These are sequential narrative beats (conclusion → correction), not a parallel contrast structure. The correction is a single statement, not a reframe formula.
- Three operational questions — P2 exception: these are concrete operational examples illustrating a specific claim, not a rhetorical list.
- "The associate improvised. You corrected. They adjusted. You corrected again." — Deliberate cycle compression. The repetition serves the argument (showing the loop, not decorating prose).
Example 4: Math Post (Proof/Math)
Angle: Math Post Hook type: Pattern (behavioral recognition) Length: ~270 words (~1,400 characters) Core insight: Advisors rank deliverables by effort. Clients rank by experience. The lists are inverted — and they've never compared them. Status signal: Reader who engages is signaling "I think in specific numbers, not vague aspirations. I make plans, not wishes."
You already know which deliverables you'd cut first. ← HOOK: Behavioral recognition. Every advisor
Here's how most advisors rank them: has this mental list. "You already know" —
acknowledges, doesn't accuse.
← FIRST LINE: Proof setup. Opens the list.
"Most advisors" gives distance before the mirror.
1. Quarterly strategy reports (8 hrs each) ← LIST #1: Effort ranking with hours.
2. Custom onboarding docs (6 hrs) Time per item makes invisible cost VISIBLE.
3. Progress dashboards (4 hrs) Ranked by effort (highest time = highest
4. Monthly recap emails (2 hrs) priority to cut). Reader recognizes their
5. Post-call summaries (30 min) own logic.
6. Weekly check-in calls (1 hr)
Cut the top two. ← QUICK MATH: Each number gets its own line.
Save 14 hours a month. Own beat. Steve's DNA.
168 hours a year. Validates their thinking — sets up the reversal.
Now here's what your clients rank as most valuable: ← LIST #2: Same items, different order.
1. Weekly check-in calls The inversion is the gut punch.
2. Post-call summaries
3. Monthly recap emails
4. Custom onboarding docs
5. Quarterly strategy reports
6. Progress dashboards
Your #1 cut is their #6 priority. ← THE MISMATCH: Each statement its own line.
Fine — they won't notice. The gap is visible. No explanation needed.
Your #6 cut is their #1. "Cut that." — two words. Dares them.
Cut that.
One client notices...$30K gone. ← COMPOUND MATH: Multiplies the mismatch
Two clients notice...$60K. to annual cost. Ellipsis here is
Three. $90K. cause → effect, not dramatic pause.
168 hours saved. The trade-off hits harder when they
$90K lost. land separately.
Per year.
Every year.
You're ranking by effort. ← ANCHOR LINE: "And" at start of final line
Your clients are ranking by experience. ... makes it land as realization, not lecture.
And you've never compared the two lists. The real insight: not that they're ranking
wrong, but that they've never asked.Distribution Analysis
Dwell time drivers:
- Two parallel lists force the reader to read both completely to see the inversion
- Time per deliverable (8 hrs, 6 hrs) creates concrete anchors the reader processes individually
- The compound math ($30K → $60K → $90K) creates escalating stakes that hold attention
- ~1,400 characters — in the optimal range
Comment generation:
- The two-list structure is inherently shareable — readers will mentally run their own version
- High potential for "I ran my numbers and..." responses
- Conversation prompt type would be Application challenge: "Run the napkin math for your practice — what number surprised you?"
Status mechanics:
- Engaging signals: "I think in specific numbers, not vague aspirations"
- Sharing signals: "I've discovered a blind spot most advisors miss — and I want my network to see it"
- The two-list framework gives readers vocabulary they can use with their own teams — that's the status transfer
Copy QC Notes
- "Your #1 cut is their #6 priority." / "Your #6 cut is their #1." — Not twinning. These are data points from the two lists, showing the specific inversion. The structure serves the math, not rhetorical decoration.
- "2s become..." / "5s become..." repetition (if combined with Contrarian Take example) — P2 exception: data pattern showing cause → consequence.
- Three-item compound math ($30K, $60K, $90K) — P2 exception: data escalation, not rhetorical list.
- "168 hours saved." / "$90K lost." — Deliberate juxtaposition. The contrast is the argument, not a twinning formula.
Structural Notes (Steve's DNA)
This is the Proof/Math post type. Note the structural spine:
- Hook (behavioral recognition) → First line (proof setup) → List #1 (effort ranking with hours) → Quick math → List #2 (client ranking, inverted) → Mismatch → Compound math → Anchor line
Each number, each beat, each statement gets its own line. No narrative prose. No paragraphs. The math is the argument.
What All Four Examples Share
- The conversation prompt is designed, not appended. Each prompt invites a specific, substantive answer that makes the commenter look good.
- Specificity drives dwell time. "The call about their kid's college fund" and "scores a 2 across the board" and "re-prepping every client file the night before" — readers slow down for concrete details.
- Status is baked in, not bolted on. Engaging with any of these posts signals something positive about the reader's professional identity.
- The closer and conversation prompt do different jobs. The closer is the quotable takeaway. The prompt generates the comments that earn distribution. Both are required.
- Voice is consistent. Direct, specific, warm without casual. Surgeon, not guru.
- Length is in the zone. All four posts fall in the 1,400–1,700 character range — the sweet spot for dwell time and completion.
- All four stay in the Advisory OS topic lane. Client perception, prospect evaluation, delegation infrastructure, invisible costs. Operational systems for advisory practices.
- Two structural types are represented. Examples 1–3 are Worldview/Insight posts (scene-led, no math). Example 4 is a Proof/Math post (behavioral hook, lists, napkin math). Both follow Steve's DNA: short lines, white space, scannable.