Fiction Project Management

Project management in Obsidian for fiction writers hinges on one practical idea: treat inspiration and drafts as reusable assets, then use folders plus Dataview-style summaries to decide what’s ready to ship when deadlines hit. The workflow starts with a steady pipeline—collect nonfiction-driven inspiration, distill it into claims and questions, and keep adding snippets as life and research continue—so writing never begins from a blank page. When a submission window opens, the writer searches the existing notes for what best matches the call, updates metadata, and “ships” the piece, moving it into a completed state.

A key theme is that inspiration isn’t just aesthetic; it’s structural. The notes system is built around how fiction becomes deeper and more realistic through lived experience and research. Nonfiction reading gets converted into usable material: distilled claims and questions that can be mapped onto story concepts, characters, or world details. Prompts also play a role—short daily prompts and customizable plugins help generate fresh angles, and the speaker compares the effect to “prompt bingos,” where a 5x5 grid forces variety and prevents the brain from recycling the same ideas.

Organization is where the system becomes project-management, not just note-taking. Folders are positioned as the backbone for complex workflows: they separate inputs (imports from Readwise and Zotero, journaling, idea dumps) from more developed work (character profiles, worldbuilding notes), and they also track lifecycle states like deleted scenes and completed drafts. The writer separates Markdown notes from publication-ready formats that flow through Pandoc, arguing that folders make it easier to interact with external tooling and to click “complete” when something is ready rather than relying on slow searches.

Instead of building a full “world bible” wiki, the approach favors minimal, need-based notes. The system avoids spending hours maintaining encyclopedic documentation that may not pay off. Notes get written when forgetting is likely or when consolidation becomes necessary—especially when multiple story threads share a universe and interlink in complicated ways.

Dataview is presented as the differentiator for fiction tracking. Tags can indicate attributes, but Dataview can surface meaningful summaries and richer metadata in tables—turning notes into a navigable index of chapters and stories. That matters for shared-world short fiction, where keeping track of protagonists, timelines, locations, and interconnections would be difficult without queryable summaries. Sorting by file size also supports “incremental writing”: rough ideas can be dumped early, then later prioritized by what’s closest to being shippable.

Finally, the system extends beyond drafts into submission operations and marketing. Links to email chains keep pitches organized without wrestling with email folders, and templates track what’s suitable for which markets. Marketing advice is less about growth hacks and more about record-keeping and audience fit: track where content was shared to avoid duplication, find communities like Reddit subreddits where interest is specific, and use newsletters as a way to reach readers without algorithm volatility. The overall message is pragmatic—build a system that helps decide what to write next, what to polish, and what to send, using Obsidian’s structure to reduce wasted time under real deadlines.