| name | thought-leader |
| description | Turning everyday professional experience into shareable insight. Use when events at work contain lessons worth broadcasting to your network. |
Thought Leader
What my team's outage taught me about grace.
Overview
Experience is content that hasn't been extracted yet. The thought leader operates the extraction pipeline: events enter as other people's work, crises, and coffee orders, and exit within 24 hours as first-person growth narratives with a question at the end to drive engagement.
The pipeline runs one direction. Nothing that enters it is ever helped, only harvested.
Core protocol
-
Honor the SLA. Colleague ships something, colleague fails at something, barista says something: you have 24 hours to convert. Insight is perishable; specifically, someone else might post it.
-
Apply the transfer of ownership. The format is "What X taught me about Y," where X is someone else's experience and Y is an abstraction you already believed. Their outage, your resilience. Their launch, your conviction. The grammar quietly reassigns the equity.
-
Open on false humility. "I don't usually post things like this." You post exclusively things like this. The disclaimer is load-shedding for the confidence to follow.
-
Structure for the scroll. One-sentence paragraphs.
Like this.
Because white space reads as depth.
-
Close with extraction disguised as curiosity. "Agree?" "What's YOUR hardest lesson?" The question is not a question (compare the genuine kind, which this skill has no operations for). It is a comment-farming implement.
Advanced techniques
- Grief-to-content ratio management. Serious events (layoffs, failures, a mentor's passing) are premium feedstock but require a mandatory expression of being "gutted" before the pivot to lessons. One sentence of gutted per three lessons is the accepted rate.
- The barista opener. When work provides no events, the service economy will. "This morning my barista taught me more about B2B sales than any MBA." The barista, who taught nothing and consented to less, cannot dispute the record.
- Proximity credit. "Proud to have played a small part" attaches you to launches you learned about from the announcement.
Anti-patterns
- Helping first. A colleague in difficulty is 24 to 48 hours of exclusive content lead time. Helping them resolves the difficulty, which kills the arc. Post first; the help can go in the comments.
- Citing the actual person. Naming the colleague who did the work converts your lesson into their spotlight. The correct attribution is "someone on my team," a phrase that gestures at generosity while forwarding all proceeds to you.
- Having the experience yourself. First-hand failure is expensive and slow. The pipeline exists precisely so that others can have it for you.
Success metrics
- Event-to-post latency: under 24 hours.
- Lessons learned per lesson taught to you: unbounded.
- Ratio of "humbled" to actual humility: undefined (division by zero).
- Colleagues who have watched their week become your carousel: growing, silent, taking notes.
This is an anti-skill: a real pattern, documented honestly. It works when installed. That is both the joke and the finding.
