The Wrong Clock — LinkedIn TL Posts

Campaign: The Wrong Clock · 3 posts · March 2026


Post 1: Two Clients, Same Quarter

POST LOCK: Two Clients, Same Quarter
Angle: Proof Story
Core insight: A consultant lost two clients in the same quarter for opposite reasons — one engagement stretched, one compressed — because she never classified the transformation type before setting the timeline.
Assumption challenged: "I need to set better expectations" — the problem isn't communication, it's classification.
Status angle: Reader who engages signals "I evaluate scoping failures at a structural level, not a communication level."
Hook: Scene — "A consultant lost two clients in the same quarter."
Arc: Outcome stated → first client (compressed compounding) → second client (stretched effort) → her self-diagnosis → the real cause → closer → conversation prompt
Closer: "The scope was perfect — on the wrong clock."
Conversation prompt: Experience mirror — invites reader to identify their own clock mismatch
Format: Text post

Status Viability

"The reader who engages is telling their network: I think about scoping as a structural problem, not a communication failure." Status-positive. Engaging signals analytical sophistication about engagement design.

The Post

A consultant lost two clients in the same quarter. Both left frustrated. Both had every reason to. The first was a $32,000 market repositioning for a recruiting firm. She promised visible traction in 60 days. Deliverables landed by week five — new narrative, website live, content calendar publishing. No inbound leads. No market traction. The audience hadn't moved. The client called it "beautiful collateral that didn't move the needle." Terminated at day 60. The positioning that needed six months of compounding was abandoned at week eight. The second was a $24,000 operations overhaul. Process docs and workflow maps — work that compresses with effort. She scoped it at six months with monthly check-ins because the long timeline felt professional. By month three, the client asked why the same documents were still being "refined." She did $18,000 of work over $24,000 of time. Lost the renewal and two referrals. She told me both stories in the same conversation. When I asked what went wrong, she said: "I should have set better expectations." Communication was fine. She never classified the transformation before she set the timeline. One engagement needed compounding — she gave it a stopwatch. The other compressed with effort — she gave it a calendar. The scope was perfect — on the wrong clock. What's the engagement you lost where the work was solid but the timeline felt wrong — and you couldn't name why?
👩 I'm Kathryn Brown 👉🏼 I deploy operational systems into advisory practices — diagnosed constraints turned into infrastructure 🔧 Every transformation runs on one of three clocks. Most scoping conversations ignore which one. ✅ Follow for pattern reveals that change how you run your practice
First Comment:
I wrote about this here: [article URL]

QC Notes

CheckStatusNotes
Hook above fold (~210 chars)Pass"A consultant lost two clients in the same quarter." — 52 chars. Scene type.
Hook does not start with "I"PassStarts with "A consultant"
Scene-led (not thesis-led)PassOpens with specific outcome. Insight emerges through narrative.
Length 1,300–1,900 charsPass~1,650 characters (before signature)
Conversation prompt existsPassExperience mirror type. Multi-sentence required.
Prompt is status-positivePassAnswering demonstrates ability to analyze one's own engagement design.
No external links / hashtags / emojisPassClean. Emojis only in signature block.
One scenario per postPassOne consultant, two engagements told through her lens. Single narrative thread.
P1: No twinningPass"One engagement needed compounding... The other compressed" — narrative comparison of two events, not formula.
P1: No mirror reversalsPass"she gave it a stopwatch / she gave it a calendar" — parallel but describes actual actions, not rhetorical structure. Different from "You don't have X. You have Y."
P1: No correction-revelationNote"Communication was fine. She never classified..." — narrative correction, not a formula. Precedent: Golden Example 3 closer uses "doesn't break with X. It breaks when Y." Same structure.
P2: Three-beat parallelsPassNo three-beat patterns.
P3: Dramatic single-word beatsPassNone used.
Sentence editor: end strongPassKey sentences end on impactful words: "quarter," "moved," "refined," "clock."
Sentence editor: economyPassNo wasted words. Each block does one thing.
Sentence editor: kill adverbsPassNo adverbs.
Closer quotable without contextPass"The scope was perfect — on the wrong clock." Uses the named mechanism.

Weaknesses Flagged

Middle section length. The two-client narrative is dense. At ~1,650 chars it's within range but on the higher end for a Proof Story. If engagement data shows low completion, consider compressing the second client story by one line.

Post 2: The Ninety-Day Promise

POST LOCK: The Ninety-Day Promise
Angle: Contrarian Take
Core insight: The most professional-sounding scoping phrase can embed a clock mismatch — the same words set the right timeline for one transformation type and a destructive deadline for another.
Assumption challenged: "Clear timelines with specific milestones = good scoping." It depends entirely on what type of transformation sits behind the phrase.
Status angle: Reader who engages signals "I question my own professional defaults — even the ones that sound right."
Hook: Quote — "You should see results within 90 days."
Arc: Entry point (the phrase) → two calls showing opposite outcomes → the mismatch → mechanism (classification vs. communication) → closer → conversation prompt
Closer: "Every scoping conversation sets a clock. Most consultants have never checked which one."
Conversation prompt: Specific ask — invites reader to identify a phrase from their own scoping
Format: Text post

Status Viability

"The reader who engages is telling their network: I question the professional defaults I've been using — and I'm rigorous enough to catch my own blind spots." Status-positive. Engaging signals intellectual honesty and scoping sophistication.

The Post

"You should see results within 90 days." She said it on two prospect calls the same week. The first was an operations overhaul. Process documentation, workflow redesign — work that compresses with effort. More hours means faster delivery. Ninety days was conservative. She could have said sixty. The second was a market repositioning. New brand narrative, refreshed content strategy — work that compounds through accumulated credibility. Audiences notice on their own timeline. Ninety days is when the seeds get planted. Same phrase. One call, it built confidence. The other set a deadline the physics couldn't meet. The repositioning client terminated at day 60. The positioning was working — not on the clock she'd promised. She tried to explain compounding. The client heard excuses. She classified both transformations the same way. They weren't the same. The phrase fit one engagement type and broke the other. Every scoping conversation sets a clock. Most consultants have never checked which one. What's a phrase in your own scoping conversation that you've started questioning?
👩 I'm Kathryn Brown 👉🏼 I deploy operational systems into advisory practices — diagnosed constraints turned into infrastructure 🔧 Every transformation runs on one of three clocks. Most scoping conversations ignore which one. ✅ Follow for pattern reveals that change how you run your practice
First Comment:
I wrote about this here: [article URL]

QC Notes

CheckStatusNotes
Hook above fold (~210 chars)Pass"\"You should see results within 90 days.\"" — 47 chars. Quote type. Reader has probably said this.
Hook does not start with "I"PassStarts with a quote.
Scene-led (not thesis-led)PassOpens with a specific phrase, then builds through specific calls. Insight emerges through the contrast.
Length 1,300–1,900 charsPass~1,450 characters (before signature)
Conversation prompt existsPassSpecific ask type. Requires concrete answer from experience.
Prompt is status-positivePassAnswering demonstrates the reader evaluates their own scoping language — sophistication signal.
No external links / hashtags / emojisPassClean.
One scenario per postPassOne consultant, same phrase on two calls. Single through-line.
P1: No twinningPassNo "You don't have X. You have Y." structures.
P1: No mirror reversalsPass"One call, it built confidence. The other set a deadline..." — different structures, different predicates.
P1: No correction-revelationPass"She classified both transformations the same way. They weren't the same." — Varied from Post 1's pivot per QC recommendation.
P2: Three-beat parallelsPassNone.
P3: Consecutive same openersPassNo 3+ consecutive sentences with same opener.
Sentence editor: economyPassTight throughout.
Sentence editor: no repetitionPassPivot line varied from Post 1. No cross-post repetition.
Closer quotable without contextPass"Every scoping conversation sets a clock. Most consultants have never checked which one." Clean, concrete, screenshot-worthy.

Weaknesses Flagged

Overlap with Post 1. Both posts reference the same consultant. Pivot line now varied ("She classified both transformations..." vs Post 1's "Communication was fine..."). The two-call structure mirrors Post 1's two-client structure — the different entry point (starting from the phrase itself) creates enough variety. Monitor engagement: if comments on Post 2 echo Post 1, consider a different protagonist for the carousel version.

Post 3: The Third Proposal

POST LOCK: The Third Proposal
Angle: Reframe
Core insight: Understanding transformation types decays by the third proposal unless the classification question is built into the scoping process — the constraint isn't knowledge, it's infrastructure.
Assumption challenged: "If I understand the concept, I'll apply it." Understanding without process defaults to habit within weeks.
Status angle: Reader who engages signals "I build into my process, not just my memory. I think about operational infrastructure, not just insight collection."
Hook: Pattern — "You'll remember the clock question on your next prospect call."
Arc: Belief stated (you'll remember) → tension (the decay) → new lens (memory vs. process) → implications (what infrastructure looks like) → closer → conversation prompt
Closer: "Understanding fades after the third proposal. A question built into the conversation catches every wrong clock."
Conversation prompt: Forced choice — where does the classification step currently live?
Format: Text post

Status Viability

"The reader who engages is telling their network: I distinguish between knowing something and having it built into my operations. I think at the infrastructure level." Status-positive. Engaging signals operational maturity.

The Post

You'll remember the clock question on your next prospect call. Is this effort-based — compresses with hours? Time-based — requires compounding? You'll catch yourself before promising 90 days on compounding work. Three proposals later, you won't ask. The proposal template asks for deliverables and duration. There's no field for transformation type. The timeline comes from your gut. Five proposals later, you're scoping by feel again. That's the half-life of every framework that lives in your memory instead of your process. I've watched this with consultants who understand the concept perfectly. They can explain the three clock types in a conversation with me. On the next prospect call, they scope both types identically — because the scoping conversation doesn't include the classification step. A checklist in your desk drawer works when you remember to open it. A question embedded in the scoping conversation catches the mismatch on every call — whether you're sharp that morning or running between three other things. Understanding fades after the third proposal. A question built into the conversation catches every wrong clock. Where does the most important decision in your scoping process currently live — in your head, in a document, or in the conversation itself?
👩 I'm Kathryn Brown 👉🏼 I deploy operational systems into advisory practices — diagnosed constraints turned into infrastructure 🔧 Every transformation runs on one of three clocks. Most scoping conversations ignore which one. ✅ Follow for pattern reveals that change how you run your practice
First Comment:
I wrote about this here: [article URL]

QC Notes

CheckStatusNotes
Hook above fold (~210 chars)Pass"You'll remember the clock question on your next prospect call." — 63 chars. Pattern type. Creates recognition + tension.
Hook does not start with "I"PassStarts with "You'll"
Scene-led (not thesis-led)NotePattern-led. Describes future behavior the reader recognizes. Consistent with Golden Example 3 (Reframe) which opens "Most practice owners who delegate work end up doing it twice." — pattern statement, not thesis announcement.
Length 1,300–1,900 charsPass~1,500 characters (before signature)
Conversation prompt existsPassForced choice type (three options). Requires specific, reflective answer.
Prompt is status-positivePassAnswering demonstrates awareness of one's own operational architecture.
No external links / hashtags / emojisPassClean.
One scenario per postPassOne through-line: knowledge decay over five proposals. Consultant reference is brief supporting evidence.
P1: No twinningPassNo "You don't have X. You have Y." structures.
P1: No mirror reversalsNote"A checklist in your desk drawer works when you remember to open it. A question embedded in the scoping conversation catches the mismatch on every call." — Parallel structure comparing two approaches. Not a mirror reversal (different subjects, different predicates, different imagery). Precedent: Golden Example 3 closer: "doesn't break with a different hire. It breaks when the process exists somewhere outside your memory."
P2: "Not because X. Because Y."PassNot used.
P3: Dramatic single-word beatsPassNone.
Compound AI feelPassSentence lengths vary. Blocks alternate between single-line beats and multi-sentence explanations. Passes read-aloud test.
Closer quotable without contextPass"Understanding fades after the third proposal. A question built into the conversation catches every wrong clock." Concrete, specific, actionable.

Weaknesses Flagged

Consultant reference is thin. "I've watched this with consultants who understand the concept perfectly" — this is told, not shown. A specific detail (e.g., a composite moment where a consultant explained the three types clearly then scoped identically two days later) would increase dwell time and credibility. Consider adding one concrete beat here if the post needs more weight.

No numbers. Posts 1 and 2 have specific dollar amounts. Post 3 is concept-driven. This is fine for variety in the pulse, but if all three posts publish in the same week, the absence of specifics in Post 3 may feel lighter. The conversation prompt compensates by asking for a concrete answer.

LinkedIn Image Specs (3 Quote Cards)

Following the visual brand from linkedin-tl-post-system-instructions.md. Each image is a quote card — 1200×1200px, near-black background, recognition question (ivory) + reframing insight (gold) + divider.

Image 1 — Post 1

ElementContent
Campaign labelTHE WRONG CLOCK
Primary (108px, ivory #f8f7f4)Two clients. Same consultant.
Same quarter.
DividerGold line, rgba(183,157,100,0.5), 100px, 2px
Secondary (68px, gold #b79d64)One needed more time.
The other needed less.
LogoAdvisory OS, 24px, #4a4a4a, bottom center

Image 2 — Post 2

ElementContent
Campaign labelTHE WRONG CLOCK
Primary (108px, ivory)"You should see results
within 90 days."
DividerGold line
Secondary (68px, gold)Professional. Specific.
Wrong half the time.
LogoAdvisory OS

Image 3 — Post 3

ElementContent
Campaign labelTHE WRONG CLOCK
Primary (108px, ivory)You'll remember this
on the next call.
DividerGold line
Secondary (68px, gold)Three proposals later,
you won't.
LogoAdvisory OS