TEMPLATE #35 OF 111TrustHow-to

Diagnose before you fix Template

A decision tree proves expertise better than advice, and the CTA fills your comments with real problems.

Goal: Trust
Format: How-to
Fill-in boxes for every blank
Live LinkedIn preview
Shows where “see more” cuts (210 chars)
Free, no signup needed

Choose Your Opening HookBefore LinkedIn “see more”

Select an opening angle that fits your personal story:

Fill in the blanks (0/10)

SymptomSymptomCondition ACauseFixCondition BCondition CThe one diagnostic questionThe popular fixOne branch

Let AI write it in your voice →

Pro Tip: Give away your playbook for free, sell the implementation. Serious buyers will gladly pay you to execute what you just explained.

Live LinkedIn Preview

501/3000

Your Name• 1st

Founder & Consultant • LinkedIn GrowthJust now • Edited •

[Symptom] is never the problem.

Here is how to find what is.▲ Hook sits above the fold (~210 chars)▼ Below expands on “...see more”
If [symptom] and [condition A] → the problem is [cause], fix with [fix].
If [symptom] and [condition B] → the problem is [cause], fix with [fix].
If [symptom] and [condition C] → the problem is [cause], fix with [fix].

The quickest way to tell them apart: [the one diagnostic question].

Most people jump straight to [the popular fix]. That only works for [one branch].

Tell me your symptom and I will tell you where I would look first.

👍 Like💬 Comment🔄 Repost📤 Send

Showing full post: every word is crisp, dark, and copy-ready. The divider shows where LinkedIn folds the feed.

Template Playbook

How to write a killer Diagnose before you fix post

Designed to demonstrate deep domain competence, authenticity, and empathy so lurkers convert to followers.

✓ What works on LinkedIn

Define the exact starting state and end state before step 1
Explain the 'why' behind each step, not just the mechanical 'what'
Provide copy-pasteable prompts, templates, or checklists
Clarify who this works for and who should deliberately skip it

✕ Mistakes to avoid

Do not skip the hard steps or pretend complex implementations are effortless
Do not gate the crucial secret behind a paywall in an annoying way
Do not use jargon without defining it in plain English
Do not assume the reader has your specialized background or tools

When to use this template

When sharing a repeatable system, standard operating procedure, or audit
To demonstrate hands-on expertise and proof of execution
When offering a quick 10-minute fix to an urgent operational pain point
As a teaser for your full service, workshop, or consulting engagement

Topics & Tags:#diagnosis #expertise #inbound