Ideation and Credibility Systems
Rule: Start From Specific Topics
Description: Specific topics generate clearer and more reusable angles. Negative example: "I write about productivity." Positive example: "I write about weekly planning for remote engineering teams."
Rule: Define Audience Bucket First
Description: Choose whether the draft is for general, niche, or industry readers before writing the opening. Negative example: A single post trying to satisfy beginners, specialists, and executives at once. Positive example: A niche-targeted draft that assumes shared baseline knowledge and solves one precise problem.
Rule: Use Multi-Angle Expansion
Description: Expand one topic through multiple lenses. Negative example: Repeating the same generic advice in every post. Positive example: One topic explored through actionable, analytical, and reflective angles.
Rule: Use 4A Lens Selection
Description: Pick one lens (actionable, aspirational, anthropological, analytical) before choosing your title. Negative example: Headline promises data but body delivers only motivation. Positive example: Actionable lens with a step-by-step container and execution examples.
Rule: Make Credibility Explicit
Description: Briefly state why your claim deserves attention. Negative example: Advice with no source or experience context. Positive example: "This pattern comes from 30 weekly updates across three teams."
Rule: Choose a Structural Container Before Drafting
Description: Decide whether piece is steps, lessons, mistakes, or checklist before writing. Negative example: Random structure that changes format mid-piece. Positive example: "5 mistakes" format with one concrete fix per mistake.
Rule: Mine Recurring Community Signals
Description: Capture repeated questions, complaints, and recommendation requests before drafting. Negative example: Choosing topics in isolation without checking what readers repeatedly ask. Positive example: Tracking recurring subreddit questions, then building one focused post per pattern.
Rule: Borrow Community Vocabulary Responsibly
Description: Use audience-native language while preserving precision and clarity. Negative example: Forcing unfamiliar terminology that makes the post sound imported. Positive example: Using the community's standard terms and then defining any technical nuance.