A story has its own nature, much like the finest wool found in bolts in a master craftsman's shop. It has strengths, weaknesses, a grain, drape, weave, weight. A master craftsman doesn't force the cloth into something it cannot become - he studies it until it reveals what it wants to be. That's much like my craft of developmental editing.
An editor's task isn't to impose a design but to discover it: to cut with the story rather than against it, remove what distorts it, and reveal the form that's been present from the beginning. This has always been my editorial philosophy, and it's why I've resisted "fixing" stories by making them sound as though someone else wrote them. My instinct has consistently been to uncover the narrative that's already there.
The Two Clients
A story has integrity. It has architecture. It has an internal logic that even its own author sometimes can't yet hear, and my responsibility is to both the writer and the story. I've often told writers: I'm not rewriting your voice. I'm protecting the story's voice.
When I sit with a manuscript or screenplay, I'm not asking what story I want it to be. I'm asking what this story is trying to become - where the natural grain runs, what the author has accidentally cut against, what's already beautiful but buried beneath poor construction. In that sense, my "customer" is really two clients: the writer who has entrusted me with years of their work, and the story itself.
Respecting the Material
When a client says, "There's something wrong with the script, but I can't figure out where," they may correctly sense that something's wrong, even suspect a specific cause, while struggling to identify what's actually underneath it. I keep their read in mind while I observe the narrative, but my job isn't built on assumption - it's built on evidence and on diagnosing the underlying problem. In practice, I help the author understand the concerns I've identified, whether they involve structure, character development, emotional progression, thematic coherence, narrative clarity, dialogue, or other elements of the work. What the author chooses to do with that information remains their decision.
That's the ethical position of a developmental editor: the craftsman respects the material enough not to force it, the editor respects the writer enough not to usurp authorship, and the editor respects the craft enough not to pretend the client's diagnosis is correct just because the client made it. I might say, in effect, "You've identified X as the issue, but I believe Y is the underlying one, and here's why." If the writer chooses to address X instead, that's their prerogative - I've fulfilled my responsibility by making the underlying architecture visible.
People often think of an editor as someone who "fixes grammar," but that's one distinct type of editing. Becoming a developmental editor - someone who can diagnose narrative architecture and understand character, pacing, causality, and voice - isn't something learned in a weekend course. It takes years; in my case, decades.
I've been doing this since 1999, but something older is at work too. My background in Quality Assurance trained me to recognize systems, patterns, and causality long before I applied any of that to fiction. Years of editing novels and screenplays refined that instinct into narrative craft, and when I formally opened my editorial practice, I began articulating those accumulated years into a coherent philosophy and methodology.
Once the mechanics become second nature, the mind is free to think at a higher level. That's tacit knowledge - and there's a line from the philosopher Michael Polanyi that has always captured this for me: we know more than we can tell. It explains why real expertise eventually resists being reduced to rules.
My Editorial Framework may allow me to document the reasoning and evidence supporting individual judgments. What cannot be fully reduced to documentation is the accumulated experience and tacit knowledge informing those judgments.
That's the difference between methodology and mastery.
Observation Before Acting
Most people imagine editing begins with making changes. For me, it begins with observation. I read, I listen, I ask questions, and I let the author’s work tell me what kind of story it is before I offer a single recommendation. It's not a passive exercise - it's a practice born from years of disciplined restraint.
In this first stage, I'm simultaneously tracking character arcs, emotional causality, internal logic, thematic coherence, scene function, and the larger narrative question underneath all of it. To someone watching from the outside, it probably looks like I'm "just reading." Internally, I'm playing a game of chess across the entire work.
After observing the architecture, the next step is mapping the story - not to "fix" scenes, but to take the story's measurements. Only when I understand its proportions can I start recommending where the architecture might be strengthened. I've come to genuinely enjoy this mapping process; my Editorial Framework system isn't just a tool for me, it's a companion. When a manuscript or screenplay has deep structural problems, I don't look at it with disapproval - I get curious. Why isn't this working? What is this scene actually trying to accomplish? What promise did the story make that it later forgot?
Observation tells me what is present in the work. Analysis asks what that material is doing, how its elements relate to one another, and what consequences those relationships create. It is through that examination that patterns begin to emerge.
Recognizing the Patterns
The next step is analysis: recognizing the patterns that emerge when the narrative is examined as a whole. When I complete mapping a screenplay, treatment or manuscript, I'm revealing the pattern, laying out the architecture and identifying where each piece belongs and how the pieces fit together before anything gets cut.
Much of this phase is about noticing repetition and outliers and treating them as evidence rather than coincidence.
When a protagonist behaves inconsistently, heed the pattern. When supporting characters all perform the same narrative function, heed the pattern. When Act II keeps stalling in the same way, or every emotional beat lands half a scene too late - heed the pattern. Such repetitions warrant investigation. I don't map in order to force a manuscript into a predetermined structure; I map so I can discover the structural behavior that's already there.
This is one reason my QA background translated so naturally into developmental editing. In QA, patterns point toward the underlying system - one bug can be incidental, but five related bugs tell you the architecture itself is breaking down. In a story, one awkward scene can be isolated, but seven scenes sharing the same weakness may reveal a structural cause, an issue with a character relationship, or logic, to name a few. This was already my natural workflow when I opened my practice; it was only later that I started thinking about it explicitly as a craft.
A tailor doesn't begin with scissors, and a developmental editor doesn't begin with tracked changes. Both begin by learning the pattern. Only once I understand it do I dare to cut.
Pattern versus Formula
I once watched the film The Outfit and was struck by something its protagonist, Leonard, says about his 228-step process for making a suit - that proven patterns aren't the craftsman's enemies, they're his friends. Patterns aren't prisons. They're accumulated wisdom. Three-act structure, character arcs, cause and effect, scene objectives, dramatic irony, setup and payoff - these aren't arbitrary rules, they're patterns that have endured because they work. Only once you understand why they work can you decide when to bend them.
A formula tells a story what it must do. A pattern reveals what the story is already doing.
Structure isn't the enemy of creativity, and originality doesn't require abandoning it - but writers and editors first need to understand the craft well enough to recognize when structural principles are serving the story, and when this particular story needs something else. Skill is what gives originality somewhere to stand.
During a recent developmental edit, a client wanted to heighten a particular dramatic effect. My instinct wasn't "no, because that violates three-act structure." It was "no, because that violates the narrative contract this particular story has already established." That distinction matters - a formula applies an external expectation, while an experienced developmental editor understands structural principles well enough to recognize the internal logic of the story in front of them.
Tools of the Trade
My editorial methodology is supported by a structured framework that allows me to examine the narrative systematically, document evidence, investigate relationships across the work, and develop informed recommendations grounded in that analysis.
Someone looking at this from the outside might ask: if you're using an analysis framework, doesn't that make the work formulaic? It doesn't. This method doesn’t replace my thinking; it frees it. The Editorial Framework handles what can be standardized, so my attention stays available for what can't be - this manuscript, this screenplay, this story, this author.
Judgment: Trusting the Disciplined Process
When I'm deep in a developmental edit, the uncertainty of a manuscript doesn't overwhelm me. I map, I look for patterns, I ask questions, and gradually the architecture reveals itself. That confidence comes from trusting a disciplined process refined over decades - trusting process over impulse, knowing that a small misalignment near the beginning of a story can become a glaring flaw by the end, respecting tradition without being imprisoned by it, because there's always room to improve the process itself.
In a developmental edit, I don't stop at the primary structural issue. I'm also looking for the secondary weaknesses that might emerge once that first issue is corrected - already asking, if they make this change, what new imbalance might it create? My framework helps me examine structure, relationships, and causality while recognizing patterns, anticipating failures, and preparing for consequences. A craftsman doesn't just see what's wrong; a craftsman anticipates what the repair will disturb.
A structural change is never isolated. Change the protagonist's motivation and five scenes may lose their causality. Remove a supporting character and another relationship may suddenly carry too much narrative weight. Move a revelation earlier and dramatic irony may disappear elsewhere.
Resolve an ambiguity and you may inadvertently destroy the story's central question. Developmental craftsmanship includes modeling those consequences before recommending anything.
Only after observing the story, mapping its architecture, and doing that analysis can I diagnose and recommend - because that's what years of craft actually produce. Not rules, not a framework, not procedures. Judgment: knowing when a pattern matters, when an anomaly is meaningful, when not to intervene, when the writer's stated "problem" is really a symptom of something else, what will break if something else is repaired, and when an imperfection belongs to the voice and shouldn't be polished away.
Evidence does not automatically prescribe an intervention. It must be interpreted, its implications weighed, and its possible consequences considered before determining whether change is warranted at all. When the developmental work is complete, the foundation should be sufficiently understood and sound enough for refinement to proceed without polishing something structurally unstable underneath it.
The editor must interpret it, weigh possible consequences, and determine whether change is warranted at all. When the developmental work is complete, the foundation is sound enough that refinement can proceed without polishing something structurally unstable underneath it.
Mastery and Humility
Mastery doesn't eliminate humility. It produces it. The more sophisticated your judgment becomes, the more aware you become of what remains unknowable, improvable, or entirely dependent on the particular work in front of you.
The principles of craftsmanship stay remarkably consistent: observe before acting, respect the material, learn the proven forms before abandoning them, develop judgment rather than shortcuts, practice until the mechanics disappear, stay humble before the work, and keep learning. There's a quiet dignity in devoting decades to a craft that most people only see after the work is finished - the finest tailoring is almost invisible because it feels inevitable, and the finest developmental editing works the same way. Readers don't notice the editor. They simply experience a story that feels whole.
Craft lives in that space. I know these principles - I've lived them. And when I'm finished with this essay, tomorrow there will be another story to explore and edit, another problem to understand, another pattern to discover. I'll lay out my tools. I'll observe. I'll map. I'll look for the pattern. And then I'll begin again.
Mastery isn't arriving at the place where you no longer need the process. Mastery is returning to the process every time.
