Learning the Pattern: The Craft of Developmental Editing

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, and 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.

 This is much like my craft of developmental editing.

 An editor’s task is not to impose a design, but to discover it—to cut with it rather than against it, remove what distorts it, and reveal the form that has been present from the beginning. This has always been my editorial philosophy. It is also why I have resisted “fixing” stories by making them sound as though someone else has written them. My instinct has consistently been to uncover the narrative that is already there.

The Two Clients

 A story has integrity. It has architecture. It has an internal logic that sometimes even its own author cannot yet hear. My responsibility is to both the writer and the story. This is why 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 do I want this to be?”

I ask, “What is this story trying to become? Where is the natural grain? What has the author accidentally cut against? What is already beautiful that has been buried beneath poor construction?”

In that sense, my “customer” is actually two clients. The first is the writer who has entrusted me with years of their work. The second is the story itself.

Respecting the Material

When a client says, “There is something wrong with the script, but I can’t figure out where the problem is,” they may correctly perceive that something is wrong and even suspect one issue, while having difficulty identifying the underlying cause.

I keep their interpretation in mind while I observe the narrative. My job isn’t based on assumption; it is based on evidence and on diagnosing the underlying problem.

In my practice, I show the author the architectural issues and am prepared to let the author decide what to do with them. This is 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 merely because the client made it.

I may say, in effect, “You mentioned that the issue in the narrative is X, but I believe Y is the underlying issue, and here’s why.” If the writer chooses X, that is their prerogative. I have fulfilled my responsibility by making the underlying architecture visible.

People often think an editor is someone who “fixes grammar,” but that is 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, and in my case, decades.

 I’ve been doing this since 1999, but there is also something older at work. My career in Quality Assurance trained me to recognize systems, patterns, and causality. Years of editing novels and screenplays refined that instinct into narrative craft. When I formally opened my editorial practice, I began articulating those years of accumulated knowledge into a coherent philosophy and methodology.

 Once the mechanics become second nature, the mind is free to think at a higher level. That is tacit knowledge.

 There’s a passage from philosopher Michael Polanyi that I’ve always thought captures this beautifully: “We know more than we can tell.”

It explains why expertise eventually becomes difficult to reduce to rules. My process can be documented, but not my judgement.

That is the difference between methodology and mastery.

Observation Before Acting

Most people imagine editing begins with making changes.

For me, editing begins with observation.

I read. I listen. I map. I ask questions. I let the manuscript or screenplay tell me what kind of story it is before I offer a single recommendation. This is not a passive exercise; it is a practice born from years of disciplined restraint.

In the beginning stages of developmental editing, I am simultaneously tracking character arcs, emotional causality, internal logic, thematic coherence, scene function, and the larger narrative question. To someone watching from the outside, it probably looks as though I am “just reading.”

Internally, I’m playing a game of chess across the entire work.

After observing the architecture, my next step is mapping the story.

The purpose isn’t to “fix” scenes, but to take the story’s measurements. Only after understanding its proportions can I begin recommending where its architecture might be strengthened.

I have a great deal of respect for this mapping process because the grid is not only a tool for me; it is also a companion. When a manuscript or screenplay has deep structural problems, I don’t look at it with disapproval. I become curious.

Why isn’t this working?

What is this scene trying to accomplish?

What promise did the story make that it later forgot?

Recognizing the Patterns

The next step is recognizing patterns.

When I map a screenplay or manuscript, I’m drawing the pattern. I’m not writing scenes. I am laying out the architecture, identifying where each piece belongs and how those pieces fit together before anything is cut.

Much of my analysis during this phase is about recognizing those patterns.

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 - heed the pattern.

When every emotional beat lands half a scene too late - heed the pattern.

These patterns aren’t accidental. They are evidence.

I don’t map to force a manuscript into a predetermined structure. I map so that I can discover its existing structural behavior. Repetition then becomes evidence.

This is one reason my Quality Assurance background translated naturally into developmental editing. In QA, patterns point toward the underlying system. One bug can be incidental. Five related bugs tell you the architecture is breaking down.

In a story, one awkward scene can be isolated. Seven scenes with the same weakness almost always reveal a structural cause.

When I formally opened my practice, this was already my natural workflow. It was only later that I began thinking about it explicitly as a craft.

A tailor doesn’t begin with scissors, just as a developmental editor does not begin with tracked changes. Both begin by learning the pattern.

Only when I understand the pattern 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: the point is skill, and proven patterns are not the craftsman’s enemies but his friends.

Patterns are not prisons. They are accumulated wisdom.

Three-act structure. Character arcs. Cause and effect. Scene objectives. Dramatic irony. Setup and payoff. These aren’t arbitrary rules; they are patterns that have endured because they work. Only after understanding why they work can you decide when to bend them.

A formula tells the story what it must do. A pattern reveals what the story is already doing.

Structure isn’t the enemy of creativity. Originality does not require abandoning structure. Writers and editors first need to understand the craft well enough to recognize when structural principles are serving the story and when the particular story requires something different.

Skill gives originality someplace 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 established.”

That distinction matters.

A formula applies an external expectation. An experienced developmental editor understands structural principles well enough to recognize the internal logic of this story.

Tools of the Trade

I use several tools during my developmental editing process, including architectural maps, character analysis grids, narrative checkpoints, and reporting templates.

Someone looking at my process from the outside might ask, “If you’re creating templates, doesn’t that make the work formulaic?” No. These tools don’t replace my thinking; they free it. The templates contain what can be standardized so my attention remains available for what cannot be standardized. My attention remains where it matters: this manuscript, this story, this author.

Judgement: Trusting the Disciplined Process

When I am deep in a developmental edit, the uncertainty of a manuscript doesn’t overwhelm me. I begin mapping, looking for patterns, and asking questions, and gradually the architecture reveals itself.

My confidence comes from trusting a disciplined process refined over decades. I trust process over impulse. I know that a small misalignment near the beginning of a story can become a glaring flaw by the end. I respect tradition without becoming imprisoned by it, because there is always room for improvement in the process itself.

In a developmental edit, I don’t identify only the primary structural issue. I also look for the secondary weaknesses that may emerge once the first issue is corrected. I’m already asking, “If they make this change, what new imbalances might it create?”

My analytical tools help me examine structure, relationships, and causality while recognizing patterns, anticipating failures, and preparing for consequences.

A craftsman doesn’t merely see what is 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 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 narrative question.

Developmental craftsmanship includes consequence modeling.

Only after I have observed the story, mapped its architecture, and performed the analysis can I diagnose and recommend.

Because that is what years of craft ultimately produce. Not rules. Not templates. Not procedures.

Judgement.

Knowing when the pattern matters. Knowing when an anomaly is meaningful. Knowing when not to intervene. Knowing whether the writer’s “problem” is actually a symptom. Knowing what will break if something else is repaired. Knowing when an imperfection belongs to the voice and shouldn’t be polished away.

When the developmental work is complete, the foundational work has happened. The architecture is sound enough that refinement can proceed without polishing something structurally unstable.

Mastery and Humility

Mastery doesn’t eliminate humility. It produces it.

The more sophisticated your judgement becomes, the more aware you become of what remains unknowable, improvable, or dependent upon the particular work before you.

The principles of craftsmanship remain remarkably consistent: observe before acting. Respect the material. Learn the proven forms before abandoning them. Develop judgement rather than shortcuts. Practice until the mechanics disappear. Remain humble before the work. Continue learning.

There is a quiet dignity in devoting decades to a craft that many people only see after the work is finished.

 The finest tailoring is almost invisible because it feels inevitable. The finest developmental editing is much the same. Readers don’t notice the editor; they simply experience a story that feels whole.

Craft lives in this space.

 I know these principles. I’ve lived them. And when I am 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.

Related Essays: