Fix the Bottleneck
A blank page can look like evidence that you have nothing to say. Yet the same person who cannot write the opening paragraph may explain the idea clearly to a friend. The knowledge is there. Something about getting it onto the page is stopping the work.
My note “Systems > Writers Block” suggests a practical response: use a system, such as transcribing audio, to remove the constraint. Map the flow of content creation, find the bottleneck and consider who could help the work move through it.
This is a more useful starting point than treating every stalled task as a character defect. Before demanding more discipline, ask exactly where the process breaks. Having an idea, explaining it, shaping a draft, checking it and publishing it are different activities. Being good at one does not make the others effortless.
Suppose you have ten useful ideas and no finished articles. Generating another ten ideas probably will not help. If you can explain them aloud but struggle to begin writing, record one explanation. Transcribe it. Now the task is to improve something that exists, which is a different problem from creating a polished piece out of silence.
If the transcript then sits untouched, you have found the next blockage. Perhaps the argument needs structure. Perhaps you need someone to ask which point you are actually making. An editor or a capable colleague may help more at this stage than another hour spent collecting material.
That is the significance of “who” in the original card. We often assume every improvement must come from becoming better at every part of the job ourselves. Sometimes the better arrangement is to let one person explain, another organise, and the original author check the result. The author still owns the judgment and the final words.
Change the stage where work stalls
An illustrative writing workflow.
There is a trap here too: designing systems can become another way to postpone the work. A complicated workflow, several new applications and an elaborate dashboard may leave you with precisely the same number of finished articles. The process has to earn its complexity by helping something useful get completed.
Start with one piece. Trace where it stops. Change the smallest part of the process that might release it, then take it through to completion. Once that works, repeat it. If work begins accumulating somewhere else, examine that stage next.
The measure is not how sophisticated your system looks. It is whether worthwhile work comes out the other end, at a standard you are prepared to stand behind. Before pushing harder on the whole machine, find the part that is holding it up.
Developed from the written description of my 2020 note, “Systems > Writers Block”: audio transcription, workflow, bottlenecks and finding someone who can help.