July 5, Sunday, raining in Shijiazhuang. I spread an A4 sheet on the desk in my rented flat and wrote down everything I had going. Seven things: Fumamx customers, a training deck for a company, my own sales tool, front-end learning, tennis, this journal, and this website.
Seven things, all of which felt important.
I was not doing any of them well. The week before, halfway through the training deck, I remembered a bug in the tool, switched over for two hours, and came back unable to remember where the deck had stopped. At night I lay in bed scrolling my phone, tired, not sleeping.
Two problems
The first is attention. When I do one thing, part of my head is queuing another. Writing code, I think about customer follow-ups. Making calls, I think about the essay I have not written. Half my brain is always on hold.
The concrete version: I work with a dozen browser tabs open, WeChat, Feishu, Obsidian, several web pages at once. When someone messages, I answer instantly. Then getting back into whatever I was writing takes five minutes.
The second problem is volume. Too many things makes me anxious; anxiety makes me grab at all of them; and everything ends up half done. Goals are vague too. “Front-end learning” — what exactly, up to what level, when is it finished? I never wrote that down.
The two feed each other. Scattered attention makes everything slow. Unfinished work makes me more anxious, and the attention gets worse.
Last Tuesday I tried a pomodoro timer. Twenty-five minutes without touching my phone, but half of it went to thinking about who I needed to reply to. A timer does not fix the queue in your head.
How the list got long
The seven things did not appear at once. They accumulated.
In March I took on a training deck because I wanted to practise teaching. In April I turned the sales scripts into a small system because doing customers by hand was annoying. In May I started learning front-end because the tool will need an interface eventually. Tennis and the journal were always there. The website had been on my mind since last year.
Each one, alone, is reasonable and has long-term value. Together they step on each other.
What I understood later: not every long-term-useful thing should be done now. Order is itself a choice.
What counts as important
That week I was reading The 7 Habits of Highly Effective People on the train. The book itself is nothing new, but it made me redo the word “important”.
My definition now: it pays off over time, and I chose it.
The first condition removes a lot. Replying to messages, routine meetings, ad-hoc chores — these have returns, but the returns are spent immediately. Nothing accumulates.
The second condition is harsher. Some things pay off over time but I do not want to do them; other people say I should. Those are not my important things either.
Very few things pass both. Out of seven, three and a half were left.
Quarantining the urgent-but-unimportant
You cannot remove urgent, unimportant things. Someone is always in the group chat, a customer can ask something at any hour, a script occasionally breaks.
My approach is quarantine rather than removal: two fixed slots a day where I handle all of it, and the rest of the time I note it down and do not jump.
Execution is hard. When the phone buzzes, my hand moves. I put the phone in another room now, physically out of reach, which helps a little. Honestly, when a colleague messages me, I still reply immediately. That part is not solved.
Time budget
I gave each kind of work a weekly hour cap. Not a minute-by-minute plan, just an upper bound: company work 4 hours a day, my own output 2, study 5, exercise 1.
That leaves roughly 12 hours a day I can allocate — based on sleeping at 10 and waking at 6, commuting under 1.5 hours, half an hour per meal, one hour for chores.
The numbers look great on paper. The first week I actually ran it for two and a half days. On Wednesday a customer needed a quote, on Thursday I worked until ten, and the plan collapsed. On Friday I woke at six, sat up, thought for ten minutes, and went back to sleep.
On the weekend I did nothing at all and slept for a day. On Saturday night I read back the week’s journal and saw where the time actually went: commuting, ad-hoc meetings, and scrolling. The first two I cannot control. The third I can.
What it looks like now
The time budget is still taped to my desk. I treat it as a reference, not a rule. Sixty percent is a pass.
The list is shorter too. Front-end is paused until the tool actually needs an interface. The training deck is squeezed into two focused weeks. The website moves to weekends. Four things are on the paper now, and one of them says “not this month”.
Cutting hurt. I bought a front-end course and have not finished it. But keeping it there only means one more thing to feel bad about.
Whether I cut the right things, I do not know. I might pick them back up in two months.
For now I run it this way. Writing it down beats holding it in my head. That is about it.
