top of page

Writing the Stories of Falcon Hollow

Finding my own way from an idea to a finished novel

I Never Really Planned to Become a Novelist

​

When I first started working on what would eventually become Father's Day, I wasn't sitting at a desk with a carefully prepared outline, a complete cast of characters, and a detailed plan for writing a novel. Actually, I wasn't entirely sure what I was doing. I had an idea that had been floating around in my head for years, an interest in mysteries and police procedurals, and a growing desire to see whether I could finally turn some of those thoughts into an actual story.


At first, I spent as much time learning about writing as I did writing anything. I watched tutorials, experimented with different software, explored outlining methods, and tried to understand how novels were supposed to be structured. I was learning about chapters, scenes, pacing, character development, and all the other things that experienced writers probably take for granted.


Somewhere in the middle of all that experimentation, something unexpected happened. The story started growing. A scene became a chapter, a chapter raised questions that led to another scene, and characters began developing personalities as the investigation started taking shape. Before I really understood what was happening, I wasn't simply experimenting with the idea of writing a novel anymore. I was writing one.


The problem was that my mind wasn't approaching it in anything resembling a straight line.

 

From A to G to R to Z

​

I've never been particularly good at thinking in a straight line. If most people approach a story by moving from A to B to C, my mind tends to go from A to G to R to Z, back to F, over to Q, down to D, and eventually finds its way to B. That's probably the simplest way I can describe how my creative process works.


I might sit down intending to write a conversation between two characters, but somewhere in the middle of that conversation, I'll suddenly think of something that should happen three chapters later. That idea leads to another question, perhaps involving a piece of evidence, a character's motivation, or something that happened before the story even began. Then I'll remember a location that needs more development, which raises another question, and before long I'm thinking about something completely different from what I originally sat down to write. Meanwhile, the conversation I started with is still sitting there, unfinished.


It isn't that I don't know what I want to say. Quite often, I can see an entire scene playing out in my head. I can picture where the characters are standing, hear the conversations they're having, and understand what they're feeling. Sometimes I know exactly how a scene should end before I've figured out how it begins. The difficulty is taking all those pieces and arranging them into something that makes sense to someone who isn't inside my head.


For a long time, I thought that meant I simply wasn't very good at writing. I imagined that real writers sat down, opened a document, and worked their way through a story from beginning to end. Chapter One led to Chapter Two, which led to Chapter Three, and eventually there was a completed manuscript. That certainly wasn't happening for me.


What I eventually came to understand is that having ideas and organizing those ideas are two very different things. And for me, the second part has always been the harder one.

 

Learning to Give the Story Structure

​

The early development of Father's Day was, to put it mildly, scattered. I would work on a crime scene, then jump into how the crime had been committed. From there, I might start thinking about a suspect's background, only to find myself working on an interview scene that wouldn't happen until much later. The material was accumulating, but it wasn't necessarily becoming a coherent novel. I had pieces of a story; I just didn't always know how they fit together.


That was when I began taking outlining more seriously. I started studying how novels were organized, how mysteries revealed information, and how individual scenes needed to contribute to the larger story. For a mystery, that last part is particularly important. The investigator might eventually know everything that happened, but the reader can't be given all that information at once. Evidence has to be discovered, questions need to be raised, suspicions have to develop, and sometimes those suspicions need to turn out to be wrong.


The order matters.


I also began to understand that a scene could be interesting on its own and still not belong where I'd originally placed it. Sometimes it needed to move, sometimes it needed to change, and occasionally something I'd spent considerable time developing simply didn't belong in the finished story. That wasn't always easy to accept, especially when I'd become attached to a particular scene or idea.
Learning to organize a story didn't mean I suddenly started thinking in a straight line. I still don't. What changed was that I began finding ways to bring those scattered ideas together.


 

The Story I Started Wasn't the Story I Finished

​

One of the best examples of how my writing evolved is Father's Day itself. The earliest version of the mystery was very different from the book it eventually became.


Originally, I was working with a concept built around resentment and jealousy within a family. It involved a stepdaughter who had spent years feeling overshadowed by her father's biological daughter. The idea was that this resentment eventually turned into violence directed toward fathers who treated their daughters like princesses while neglecting others.


It was a workable premise for a crime story, but the more I explored it, the more something bothered me. It didn't have the emotional depth I wanted. As I continued developing the characters and their motivations, the story began moving away from simple jealousy and toward something much darker: trauma, abuse, and the lasting emotional damage that can follow someone for years.


That change reshaped the entire novel. Suddenly, I wasn't interested in writing a mystery where the only question was whether Duke Mantz would identify and arrest the person responsible. I wanted readers to understand the human circumstances behind the crimes, even if they couldn't excuse what had happened. I wanted accountability, but I also wanted compassion.


Getting there meant revisiting earlier ideas, changing motivations, and reconsidering how the investigation would unfold. It also taught me something important about writing: sometimes the first version of an idea isn't wrong. It simply isn't finished becoming what it needs to be.
 

Why I Choose to Use AI

​

This is probably the part of my writing process that generates the most opinions. I use artificial intelligence as part of my writing, and I'm not going to pretend otherwise or try to hide it.


I know there are people who look down on writers who use AI. I understand some of their concerns, especially when it comes to originality, creativity, and the role of technology in producing written work. Those are legitimate subjects for discussion, but I also wish people understood that not everyone approaches the creative process the same way.


For me, the challenge has never been a lack of imagination. It's been organizing that imagination into something coherent. I can have an entire scene playing out in my head while another part of my mind is already three chapters ahead, and a third part has gone back to something I should have established earlier. Sometimes I need to talk through an idea before I can understand where it belongs. Other times, I need to examine a scene from several different directions before I can figure out why it isn't working. And sometimes I simply need help keeping track of everything.


That's where AI has become useful to me. It gives me a place to think out loud, explore possibilities, organize story material, examine continuity, and work through revisions. It can also help me develop and refine prose, but that doesn't mean I accept everything it produces. There are times when a suggestion works beautifully. There are other times when it misses the character, changes the tone, or takes the story somewhere I never intended it to go. When that happens, I change it.


I still have to decide what belongs in the story, what doesn't, how the characters behave, and whether the finished result says what I intended it to say. The technology can help me get there, but those creative decisions remain mine.


And I think that distinction matters.


I'm not asking everyone to agree with my decision to use AI. People are entitled to their opinions about it, but I do hope they'll consider that there are people who genuinely struggle with the conventional process of writing. People who have stories they want to tell but can't necessarily sit down and write them from beginning to end in one uninterrupted sequence. People whose ideas arrive faster than they can organize them, and people who may have spent years carrying stories around in their heads because they couldn't find a practical way to get them onto the page.


I know I'm not the only person who thinks this way. If a tool can help someone turn those ideas into something they can finally share with other people, I think that's worth understanding before dismissing their work simply because AI was involved. For me, AI isn't about avoiding the creative process. It's about finding a way to participate in that process that works with the way my mind operates.

 

Writing a Mystery Means Paying Attention

​

Another thing I discovered while writing Father's Day is that a mystery requires more than an interesting crime.


It requires consistency.


A character can't know something they haven't learned yet. Evidence can't suddenly appear without an explanation. Investigators need reasons for making decisions, and those decisions have consequences for what happens next. That becomes especially important when writing police procedurals, where the investigation itself is such an important part of the story.


I've always enjoyed investigative television shows and crime fiction, but enjoying those stories isn't the same as understanding how an investigation should unfold. There were things I needed to research, procedures I needed to understand, and assumptions I needed to reconsider. Sometimes I discovered that something which sounded perfectly reasonable in my head didn't make much sense once I examined it more closely. That's part of the writing process, too.


I don't want Duke Mantz to solve a case simply because the plot needs him to find the answer. I want him to reach conclusions through observation, evidence, experience, and the work of the people around him. I want the other characters to have meaningful roles in the investigation rather than existing simply to give Duke information, and I want the people involved in these cases to feel like people, not just names attached to clues.


That means slowing down sometimes, questioning scenes I've already written, and accepting that an idea I like may need to change because it doesn't fit the facts of the story. It also means going back through earlier chapters to make sure everything still works. It's a lot of revision, but I've come to appreciate that part of the process.
 

One Story Leads to Another

​

When I began writing Father's Day, I wasn't planning an entire collection of stories set in Falcon Hollow. I was trying to finish one novel. But as Duke Mantz developed, I began realizing there was much more to his life than the investigation taking place in that particular book.


He had a past, relationships, and experiences that shaped the way he approached his work. Other characters had stories of their own, and the town itself was becoming more than a setting. Eventually, those questions began leading toward other projects, including stories that explore Duke's earlier life and investigations that take Falcon Hollow in different directions.


What's interesting is that the process hasn't really changed. I still jump between ideas, discover things about characters while working on something completely unrelated, and occasionally find myself going back to an earlier chapter because something I've written much later has made me reconsider it.


The difference is that I'm more comfortable with that process now. I don't expect every idea to arrive in the correct order. I expect to have to work out where it belongs.
 

Finding My Own Way to Tell a Story

​

If there's one thing writing Father's Day taught me, it's that I needed to stop measuring my creative process against the way I imagined other writers worked. For years, I assumed there was a proper way to write a novel, and that if I couldn't follow that process, perhaps I wasn't meant to write one. I don't see it that way anymore.


I've learned that writing involves far more than sitting down and producing page after page of perfectly organized prose. For me, it involves exploring ideas, asking questions, making connections, revisiting earlier decisions, and occasionally discovering that something I thought was a distraction was actually the missing piece of the story. It involves research, patience, a willingness to admit when something isn't working, and yes, using tools that help me bring everything together.


I still have days when I sit down intending to accomplish one thing and end up working on something entirely different. I still find myself jumping from A to G to R to Z, but these days, I'm a little better at finding my way back to B.


Somewhere in that process, the stories of Falcon Hollow continue to take shape. They don't always develop in the order I expected or turn out exactly as I originally imagined, but they're stories I've wanted to tell. And after years of struggling to organize those ideas, I've finally found a way to bring them to life.
 

bottom of page