I don’t know if my situation will help you but let me talk about it anyway.
I worked for years as a tech journalist. During that time, I’d be working on two or three articles at a time, and nearly all of those articles would be done within 24 hours. In addition to that, I’d have one or two longer-term projects going along, with completion times in days, weeks, or months.
It was easy for me to hold the status of all that in my head.
Almost two years ago, I transitioned to a job doing content marketing. Now, I write articles for a corporate website. These articles can take weeks or months to complete, and I’ll generally have a half-dozen going at once. Too much for me to simply hold the status and context for all of them in my head! I have had to evolve new ways of working, and use new tools.
I have tried simple documents in the Mac Finder, DevonThink, and Obsidian. I used Obsidian for most of 2021, went to DevonThink for a couple of months, and now I’m back to Obsidian again.
Previously, I used one folder per project, but from my perspective, Obsidian does not handle folders that well. So instead now I’m using one MoC per project. The MoC contains links to each document required for a project, along with a brief description of what each document is. Here is a list of source materials from my colleagues in marketing, here are some emails discussing the project with colleagues, here are the drafts I wrote before submitting to my editor, here are versions that came back after edits and review by colleagues in the company and by partners.
I rely extensively on Microsoft Office documents, web documents, PDFs, recordings, and my own typed Markdown notes. For now at least, I store all of those in the Obsidian vault. (And, by the way, when I say “notes,” I don’t mean them in the meaning that’s come up in the PKM community. I’ve been a journalist for 30+ years — my notes are one document per interview or source document, they are typed very very fast, nearly stream of consciousness, and contain big blocks of interview transcripts.)
I also use “status” documents, one per project, containing a chronological list of actions on the project. Mostly I’m just interested in the latest action, so if my boss asks me what the status is of the Spacely Sprockets article, I can respond, “That went out to George Jetson for review last month — I emailed George three days ago, he says it’s still under review, and I have a tickler to nag George again if I haven’t heard anything next week.”
I also use daily notes for internal meeting notes and other miscellany.
Helpful?