Last month, I took on a task: writing a 40-page industry research report. The writing process for this report can conveniently be broken down along a progress bar—because I used two different tools for the first half and the second half.
0%: A smooth start.I started writing with WorkBuddy. The prose flowed smoothly, and it quickly provided a framework. At the time, I thought I could finish this report in two days.
25%: Context gap.By page eight or nine, the problem appeared: it began to lose track of the settings we had discussed earlier, and I had to feed the background in again every time I continued a section. I spent half my time acting as a "human context restorer."
50%: The knowledge base takes over.I switched approaches: I filed all the written chapters, references, and data materials into a personal knowledge base in MuchSci. From then on, the background stayed resident—I could ask questions and get answers while writing, and materials could be used immediately with their sources attached, so I never had to reintroduce myself again.
75%: Materials at hand.In the second half, the biggest test was retrieval: which document contained a certain data point, and what was the original source of a certain conclusion. A single search in the knowledge base gave me the answer, and the annotations were still there.
100%: The manuscript is submitted.The full draft was finalized, citations were checked one by one, and there were no loose ends.
Looking back on this report, my biggest takeaway is this: the enemy of long-form writing is not writing ability, but memory length. No matter how smart a single conversation with WorkBuddy is, it is a "sprinter"; a long run requires a "supply system" like MuchSci, where background stays resident and materials are always at hand.
If your next long report is also 40 pages, I suggest building the knowledge base from 0%—don't wait until 25% to switch approaches. That half-journey of archaeological digging could have been avoided.