Based on Dan Koe's writing system, this guides you through the complete writing process from topic selection to publishing.
Applicable Scenarios
- Writing social media posts (Twitter/LinkedIn)
- Writing Newsletters / blog articles
- Writing video scripts
- When you need structured writing guidance
Writing SOP (Standard Operating Procedure)
1. Topic Selection: Opinions and Perspectives
Core Strategy：
- One-Person Niche: Combine 2-3 core interests to solve yourpast problems. The best reader is your "old self".
- Vision vs Anti-Vision:
- Anti-Vision (Enemy): What do you hate/avoid?
- Vision (Destination): Where are you taking the reader?
- Topic Selection Formula: How to go from [anti-vision] → [vision]
Specific Actions：
- Creative Museum: Capture inspiration at any time (books, tweets, life), don't rely on memory.
- Refraction Principle: "Refract" universal ideas through your unique perspective to form new viewpoints.
2. Opening: Hook
The hook must include:Relevance、Pain Point or Curiosity。
Hook Formula(choose one):
- Big Problem + Negative Consequence: "If you continue to ignore [problem], you will end up in [bad outcome] after [time]"
- Big Idea + Expectation Break: "Most people think [popular opinion] is correct, but that's exactly why they fail"
- If/Then: "If you want [desired result], then you must stop [common mistake]"
- Brutal Truth: State counterintuitive facts in short sentences
3. Body: APAG Framework
| Stage | Name | Content |
|---|---|---|
| A | Attention | Hook/big idea, open with a pain point |
| P | Perspective | Establish the enemy: describe the public's wrong viewpoint, amplify the pain point, use personal stories to enhance resonance |
| A | Advantage | Propose a new perspective/solution, educate and argue, show the beautiful future after adoption |
| G | Gamify | Provide steps/challenges, make the solution as clear as a game quest |
Simplified Version (BPAS)：Big Idea → Problem → Amplify → Solution
4. Ending: Gamification and Action
- List steps: Step 1, Step 2, Step 3
- Create a challenge: "Try doing X today and see what happens"
- CTA: Guide readers into the ecosystem (subscribe/purchase)
Writing Principles
| Principle | Description |
|---|---|
| Imitate Structure | Break down the article structure of creators you like, fill it with your topic (imitate the structure, not the content) |
| Text a Friend | Imagine writing to a confused friend/younger self, eliminate the expert tone |
| 6-Step Thinking Method | ①Choose an idea ②Ask 3 questions ③Write a first draft ④Read it like a passerby ⑤Question it like a contrarian ⑥Format |
| Organize mental entropy | If you can't write it clearly, you haven't thought it through. Write it down first, then sort it out. |
| Write to share | Ask of every paragraph: would it be retweeted if posted on its own? Aim for high-density punchy lines. |
30-Minute Writing Checklist
When a user asks for help writing, follow this process:
- Topic selection: Pick a concept from your notes that can solve the pain of your "past self"
- Hook: Write the first sentence using a "counterintuitive viewpoint" or by "amplifying the pain point"
- Body:
- What is the old belief (the enemy)? Why is it wrong?
- What is the new belief (the hero)? Why is it right?
- End: Turn it into a 3-step action checklist
- Review: Reread it like a passerby, cut boring words, make sure it feels as natural as sending a text
Example
User request: "Help me write an article about 'Why most people never learn to program'"
Execution process:
- Topic confirmation: Anti-vision = giving up halfway, self-doubt; vision = solving problems independently, gaining freedom
- Hook: "Most people fail to learn programming not because they aren't smart enough, but because they use the wrong method."
- Body (APAG):
- P: Describe the vicious cycle of "watch tutorial -> copy code -> hit a problem -> give up"
- A: Offer a new perspective of "project-driven learning"
- End: List a 3-step beginner plan + CTA (subscribe to get the project list)
- Review: Cut the fluff, make sure the punchy-line density is high