Short Form Observation

Metadata

• inherits: ../short-form-voice-adjustments/SKILL.md
• formats: X single, LinkedIn, Threads

short-form-observation

A single noticed thing, stated clearly. The most disposable format AND the most viral one — because when an observation lands, it lands hard.

Structure (X single)

[Observation as a single sentence. Declarative. Specific enough that the reader can imagine it.]

[Optional: 1-2 follow-up lines — the implication, the example, or the reframe.]

Structure (LinkedIn — longer)

[The observation as the hook, 1-2 lines.]

[2-3 short paragraphs:
  - Where you noticed it.
  - Why it matters.
  - The tiny implication.]

[Closer: a one-liner, often the observation rephrased as a rule.]

Rules

• One observation per post. Combining two splits the impact.
• Specific > universal. "Most newsletters die in month 3" beats "Newsletters are hard."
• No teaching tone. You're noticing, not instructing. Let the reader draw the lesson.
• Earn the observation with detail. "Three of the four indie founders I talked to this month said the same thing about X." — vs "I keep noticing that founders…".

Anti-patterns

• "Just realized that…" — weak opener. Cut.
• Observation that's actually advice in disguise. If you're saying "you should X", it's not an observation, it's a how-to.
• Vague universals ("Life is hard", "People are weird"). The whole point is specificity.
• Adding a CTA. Observations don't sell — they earn trust.

Example shapes

Three illustrative observation shapes (replace with examples in your own niche / voice):

• The reframed-pattern observation: "Most people don't have a content problem. They have a thinking problem."
• The metaphor-collapse observation: "People don't follow dictionaries, they follow humans."
• The honest-paradox observation: "The week I shipped least was the week I learned most. That should bother me more than it does."

For specific author/post references you want to model, store them in writing-style/SKILL.md.