Hi, I am Mr Lark. In Chinese, I go by 拉克先生.
When work gets busy, I often write better. The best example was a small bug in an article summary: the mobile card left a blank line, and I found the root cause in the length check. The fix was tiny, but it gave me a real post.
Busy work filters topics
The most common excuse for not creating content is not having enough time. I have used it myself.
But limited time is not always a disadvantage. It pushes away broad topics that sound useful but stay vague.
You stop writing "how to improve productivity." You start writing "how I reduced one recurring task from 30 minutes to 5 minutes this week."
The first one sounds like an opinion. The second one is experience.
Creators do not always need more time. They need more specific problems.
Urgent problems are real material
If you are busy, you are probably dealing with real tasks every day.
Those tasks create concrete friction:
- Which workflow wastes the most time
- Which tool feels awkward
- Which sentence needs to be explained three times
- Which decision keeps circling back
- Which mistake you just made and others may repeat
That friction is content material.
People with plenty of empty time often start from "what do I want to say?" Busy people start from "what did I just solve?"
The second starting point is better.
Short time forces practical writing
If you only have 30 minutes to write, you have little room for filler.
You only need to answer three questions:
- What problem did I face?
- How did I solve it?
- Why is this useful to someone else?
That is enough.
An article does not need every background detail or the full theory. If it explains one concrete problem and leaves behind one reusable method, it already has value.
Do not chase completeness
Many people fail to publish not because they lack time, but because they want every piece to feel complete.
When you are busy, completeness is the first thing to drop.
You can write one observation, one workflow, one judgment, or one failure case. A short piece is fine if the information density is high.
For example:
- Why a tool does not fit your workflow
- Why a prompt failed
- Why a project was delayed
- Why a decision turned out wrong
- Why a small change saved a lot of time
Each one can become a standalone post.
Turn work into notes
The best material is not in a topic list. It is inside your work.
Track three types of notes:
- Problems you just solved
- Mistakes you just made
- Methods you just changed
Do not wait until the weekend. Details fade quickly.
The note does not need to be complete. One sentence is enough: what happened, why it got stuck, and how you handled it.
When you write, expand that sentence.
Busy people need a fixed structure
When you are busy, do not design a new structure for every post.
Use a simple fixed format:
- State the problem
- Name the old misconception
- Explain the new approach
- Define where it applies
A fixed format reduces startup cost. You do not need to figure out the article first. You only need to put real experience into a stable container.
Writing does not have to start from zero every time.
Being busy is not the blocker
Being busy reduces writing time, but it can improve topic quality.
You are not writing imagined problems. You are writing problems that just happened. You are not giving polished advice. You are sharing methods that were just tested.
If you always feel too busy to create content, change the goal.
Do not start by chasing output volume. Start by turning real friction into useful notes.
Limited time forces specificity.
Specificity is what most content lacks.