$ man content-wiki/anti-patterns

ANTI-PATTERN

Performing wisdom instead of sharing lessons. Abstract principles without concrete examples. Three perfect parallel examples that illustrate the point with suspicious symmetry. Branding concepts instead of explaining them — this is what I call the velocity framework. The fix: replace every abstract principle with a specific story. Instead of leaders need to communicate clearly, try last tuesday I told my team we were pivoting the campaign targeting and three people had completely different interpretations of what that meant. Specifics are interesting. Abstractions are forgettable.

ANTI-PATTERN

Use data to make better decisions. Focus on your ICP. Optimize your CRM. These are worthless without specifics. Everyone knows they should use data. Nobody knows which data field in which tool to look at for which decision. The fix: always add how, why, and what exactly. Instead of optimize your CRM, try add a custom property in HubSpot called source_campaign that tracks which Clay table pushed the contact and filter your pipeline reports by it to see which enrichment flows actually convert. That is useful. The generic version is wallpaper.

ANTI-PATTERN

Spending 4 hours on a post that should take 30 minutes. Optimizing language instead of adding substance. Making it perfect instead of shipping it. The over-polish trap is insidious because it feels productive — you are improving the content. But past a certain point, you are improving the words while the ideas stay the same. The rule of thumb: if you have edited a post more than 3 times without adding new information, you are polishing, not improving. Ship it. The feedback from publishing teaches you more than another round of editing. A good post published today beats a perfect post published never.

ANTI-PATTERN

Using jargon without context. Assuming everyone knows Clay, HubSpot, or MCP servers deeply. Skipping the why this matters framing. Technical content without accessibility is just notes for yourself. The balance: be specific enough to be useful, accessible enough to be interesting. A LinkedIn post about Clay should make sense to someone who has never used Clay but understands the problem Clay solves. Name the tool. Explain what it does in one sentence. Then go deep. The one-sentence context frame takes 5 seconds to write and makes your content accessible to 10x more people.

ANTI-PATTERN

The purple gradient template post is the visual equivalent of AI slop. Inspirational quote on a gradient background. Leadership wisdom in a carousel with smooth transitions. These perform well in vanity metrics (likes, impressions) but build zero credibility and zero relationship with the reader. Why they fail for builders: the audience you want — technical operators, GTM engineers, startup founders — sees through template content instantly. A purple gradient carousel about the 5 principles of effective leadership tells them nothing about your actual expertise. A raw screenshot of your terminal with a one-paragraph explanation of what you just built tells them everything. The rule: if a post could have been written by literally anyone, it should not have your name on it. Your content should be impossible to attribute to someone else because it contains your specific tools, your specific workflow, and your specific results.

ANTI-PATTERN

What my failed startup taught me about leadership. What running taught me about business. What my dog taught me about patience. This template has been so overused that it triggers an immediate scroll-past from experienced LinkedIn users. The analogy structure (thing from life = lesson for business) is the laziest form of content because it lets you avoid saying anything specific. If you actually learned something from a failure, share the failure with specifics. What went wrong, what the numbers looked like, what you changed. The lesson emerges from the details. You do not need to frame it as what X taught me — the teaching is implicit when the story is good enough.