Insights on writing craft, productivity, and building your best work with Plotiar.
"Kill your darlings" gets quoted like it settles the matter. It does not -- it names the problem and leaves you alone with a character you spent two years building. Here is the actual process: what counts as a darling, the three questions that replace nerve with method, and why exile beats deletion.
Screenplays can now leave Plotiar as Fountain-formatted files for Final Draft, Highland, Slugline, and Fade In. A cluster of paste and clipboard bugs are fixed, including a broken Ctrl+V and markdown tables that pasted as plain text. Tables render at the correct width and are now readable by screen readers, plus fixes to Plot Grid chapter names, editor mode persistence, mobile battery drain, footnote clicks, and a rare collaborative paragraph-loss bug.
Editing the same document across two devices no longer freezes the interface, and a run of caret and undo bugs that could delete or replay against the wrong text are fixed. Footnote editing and table cell editing are more reliable, the Snapshots panel finally shows your saved snapshots, AI Studio now confirms before replacing your document, and Inspect, Analyze, and lore extraction no longer stop short or bill you for results you never got to use.
Desktop typing in Korean, Japanese, and Chinese is fixed end to end -- input, the Enter key, font persistence mid-composition, and Korean line breaking -- and Korean translation coverage is complete, including AI Studio and the right-click menu. A real first-line indent, a character count with a script-aware reading time, PDF fonts that survive export, and several lore mention-counting and search bugs are fixed as well.
Most revision fails for the same reason: writers fix whatever catches their eye first, in whatever order the pages fall open. Here is a strict three-pass order -- structure, then continuity, then sentences -- and why skipping the order wastes months.
Four canvas editor bugs that let mobile keyboards duplicate words, mangle swipe-typed corrections, or corrupt emoji and accented characters on a single backspace are fixed, along with a link-deletion shortcut that was firing by accident on touchscreens. Promo codes also now redeem correctly on the first try, and a failed redemption no longer burns one of the code's uses.
Notion is the most flexible workspace ever shipped. It is also a database disguised as a writing app, and the disguise wears off around chapter eight. Where each tool earns its place, and the case for keeping both.
A family tree is not a reference document you draw once and file away. It is a structural tool that shows you where a story's pressure is concentrated -- and it works whether your novel has a crown in it or not. From García Márquez to Steinbeck to Yanagihara, here is what the chart is actually for.
A protagonist picked a lock she had no business picking, and it took an afternoon to figure out why the scene felt cheap. The fix was three sentences written before chapter one -- what the magic does, what it costs, and what it flatly cannot do -- drawn from Sanderson, Le Guin, Jemisin, and, unexpectedly, the Breaking Bad writers' room.
A napkin sketch of a mountain pass fixed a plot hole that a spreadsheet never could. The practical companion to worldbuilding-as-pressure: how to build geography, culture, politics, magic or technology, and language in the order your story actually needs them, and when to stop.
Three split view bugs that could strand you mid-session are fixed, from a shortcut that went dead to a project picker that ejected you out of the app entirely. Pro subscribers no longer see contradictory upgrade prompts for a plan they already have, AI Studio only offers projects you can actually write to, and a handful of smaller fixes cover Android swipe typing, Inspect error messages, and snapshot failures.
"Raise the stakes" is the advice everyone gives for a sagging middle, and it is usually wrong. A midpoint has three real jobs, none of them about volume, and most broken second acts are missing exactly one of them.
AI Studio regenerate is fixed end to end, from a permission error that blocked nearly every attempt to old content quietly resurfacing after a successful rewrite. The mobile keyboard now shows up reliably on tablets and sideways phones, Dialogue Voice Profile generates a readable document instead of a raw dump, and a couple of smaller calendar, map, and statistics fixes round out the week.
I cut a chapter because my critique group agreed it was slow. Three drafts later I put it back, because it was never slow. It was quiet, and those are not the same problem. A five-question diagnostic, with examples from Robinson, Ishiguro, and Tana French.
Lore extraction now runs reliably on full-length manuscripts, with no more false "no lore found" results or misleading failure messages. Plot Grid saves are honest about failures instead of silently showing a blank grid, mobile tapping now reliably opens the keyboard, and document export and weekly AI credit accounting are both fixed.
A four-step method for outlining a novel in about four hours: the spine, the beat sheet, the scene list, and the flowchart. Fast is not the same as shallow.
Plotiar now tracks daily writing streaks and word-count goals, with a celebration card when you hit your target and a streak calendar that keeps the record. The Studio and AI Studio are now two clearly labelled tabs, with a new Plot Grid from Document generator in the instant Studio tab. Plus: a first-login recovery fix, full keyboard navigation for the templates gallery, and several editor and mobile fixes.
Most "how to write a novel" guides describe a fantasy version of the process. This one describes what working novelists actually do -- including the parts that feel like failure but are part of the work.
Every "best Scrivener alternative" list reads like an affiliate page. This one is not. Eight tools, the same 35,000-word manuscript, a working writer's verdict on which one fits which kind of brain -- including the tools that are not Plotiar.
Analyze has been rebuilt as a real async pipeline that can pass over a manuscript-length project without falling over -- with both AI and non-AI sections, lore-aware checks, a section table of contents, and a per-job cost ceiling. Plus five new UI languages, cross-linked worldbuilding tools, a map editor that pushes toward feeling like a dedicated app, font fixes that finally make exports look right, and another round of mobile and PWA polish.
Three months running the same 95,000-word novel through both tools. Where Scrivener still wins decisively, where it has aged badly, and which kind of writer should pick which -- including the parts I was wrong about.
Most worldbuilders build too much and write too little. Worldbuilding has one job - creating pressure on your characters - and the rest is either texture or vanity. A field guide to load-bearing worldbuilding from Tolkien to Jemisin, plus the audit that cuts the fat.
Four new worldbuilding tools: an interactive map editor, customizable calendars, family trees with real relationship logic, and a Lore knowledge base that the editor reads as you write. Plus Scrivener import, markdown mode, a publication-ready book preview, document styles, bookmarks in the margin, and another round of mobile and spellcheck work.
A visual corkboard for story planning. Focus modes that highlight dialogue, parts of speech, or just the sentence you are editing. Eight ambient soundscapes. Document split and merge. A font library, five page sizes, and a complete mobile redesign.
Writers misuse archetypes as character templates — slapping "the Mentor" or "the Trickster" on a character and calling it depth. The real power of archetypes is in subversion, blending, and the friction between competing patterns inside the same character.
A full version system with snapshots, drafts, and compare. A redesigned layout with more room to write. Notes and tasks available everywhere. And thirty editor fixes you will feel immediately.
Public content sharing, persistent track changes, multi-language support, tables, equations, AI formatting tools, and a proper recycling bin — the biggest week of shipping we have had yet.
Nabokov used index cards. Tolkien kept expanding notebooks. McPhee pinned fragments to a bulletin board. They all arrived at the same organizational architecture. Here is that system, why it works, and how to build it before your novel becomes unnavigable.
Most writing advice on subplots boils down to 'make sure they connect to the main plot.' Here is a structural theory for how subplots actually work together — mechanically, at the level of chapters and scenes.
The checklist approach to character arcs produces structurally correct, emotionally dead protagonists. Here is how to use want vs. need, the Lie the character believes, and scene-level behavioral shifts to write arcs that feel human instead of mechanical.
Every plotting method works. None of them work universally. Here is an honest assessment of four major approaches — where each one shines, where each one breaks down, and how to combine them into a system that fits your brain.
We teach three-act structure wrong. It is not a recipe for building a story. It is an X-ray for diagnosing one. Here is how to use it to find and fix what is broken in your manuscript.