Author Brad Taylor & A Book Signing

Photo by Rod Pasibe

It’s my pleasure to welcome author Brad Taylor as the special guest blogger today at Thoughts in Progress as his book is released.

Brad’s book, ONE ROUGH MAN, has a level of authenticity unrivaled in thriller fiction and that’s because of him. Lieutenant Colonel (ret.) Brad Taylor has firsthand knowledge of cutting edge counter-terrorism strategies because of his experience in combat operations from more than 20 years in the U.S. Army Infantry and Special Forces.

Library Journal raves, “[Taylor] brings such incredible realism and authenticity that readers feel like they are looking over the shoulders of a real antiterrorist operation.”

To say that this is going to be an exciting series is an understatement. Brad’s unique military experience makes it hard to determine what is fact and what is fiction, and his writing keeps readers turning the pages. 

There’s an added bonus for those readers of this blog that are in the Atlanta, GA, area - Brad will be at a book signing on Sunday, Feb. 27, at the Eagle Eye Book Shop located at 2076 N. Decatur Road in Decatur, GA, beginning at 2 p.m. For more about the signing, contact the Eagle Eye Book Shop at (404) 486-0307 or visit their website at www.eagleeyebooks.com .

Brad stops by today to discuss his thorough research methods – including personal interviews and location scouting, such as with the Atlanta airport escape scene.

Ask twenty different authors what they think about the relative importance of research for a novel, and you’ll get twenty different opinions. On one side of the scale, some will say it’s irrelevant and that people read for good writing, not good research, and that water-tight research will never overcome bad writing. 

I’m on the other side of the scale. Yes, the writing comes first, but nailing the details only adds to the effect. There is no downside. Not bothering to conduct rudimentary research into the subject matter, in my mind, is insulting to the reader. It smacks of laziness, especially if the reader has some grasp of the subject. In fact, as a reader I can only get so far in a book if the information blatantly conflicts with the facts that I know. I’m not asking anyone to be an expert, but at least show me you can find Wikipedia. Or buy a Guns and Ammo magazine. I’ll forgive almost anything if the author shows me he tried.

Because of this, I’m rabid about research.  The knowledge base I gained from my previous career is absolutely essential as a starting point, but I don’t have an encyclopedic memory. Suffice it to say, I have to do an enormous amount of fact checking, from something as minute as how long a certain flight would take and the time-zones involved to whether a particular weapon fires from the open-bolt position. Invariably, whenever I try to wing it based on my memory and experiences alone, I find out I’m wrong. I’ve learned to fact-check just about everything. Luckily, if I can’t find the answer on my own, odds are very good that I know someone who can.

There is a trap with this, and I’ve fallen into it more times than I can count, and that is you want to show off the research you’ve done, babbling on about interesting but irrelevant tidbits, with the plot suffering as a result. I’ve just come to understand that out of all the research I do, only about two percent will make it into the book. Especially when talking about locations.

I’m a little bit of a perfectionist when it comes to real-world settings, and I research them relentlessly. I’ve traveled all over the world, which is a good thing when I want to describe a setting, but make no mistake; I have to really study locations to get them right. For example, I’ve been to both Central and South America, but I have never been to Guatemala or Belize, major settings in ONE ROUGH MAN. I had to research both forever, and ultimately didn’t use 99% of what I found, and in the end I’m sure that someone who’s actually spent some time there will find flaws. I’m okay with that, because I gave it my best shot. 

When I have the ability to do first-hand research, I do so. The Atlanta airport scene is a pretty good example of that. Basically, Jennifer and Pike get stopped at customs and have to break out of the secondary interrogation facility. I tried to write how they would evade capture, and escape what’s become one of the most secure areas since 9/11, using my own recollection of the airport. When I was done, I realized that I really didn’t know enough about the security of the airport, and that the way I had written it was a little hokey. I have been through that airport probably 500 times, but I’d never looked at the security from an evasion standpoint. One thing I was convinced of, though, was they weren’t going to escape by using normal passenger corridors. I called up some pilot friends of mine and proposed a simple question: how can I get out of the Atlanta airport without going the usual passenger route? They gave me the breakdown of what crew members do, to include locations of employee lounges and employee bus routes. From there, I simply flew to the airport and retraced Pike and Jennifer’s steps from customs, noting the security in place such as cameras, alarms, and checkpoints. After casing the place it was pretty easy to figure out how they could do it. 
Since I’m not independently wealthy, I couldn’t afford to do what I did with the Atlanta scene for the scenes in Bosnia, Oslo, or Guatemala. In those cases, I had to rely on the internet, my memory and friends with specialized knowledge. There’s a military phrase called Open Source Intelligence, which basically means, “read the paper and see what you can find out.” In today’s times, that means the internet, and it’s amazing what’s out there, from airport databases and flikr, to Google Earth and 360cities. Surprisingly, my favorite source is a blog from backpacking college students. Those folks go everywhere, and talk about everything from security at border crossings to the best way to get a taxi, complete with pictures. Suffice to say, just about anything can be found if one looks hard enough.

For instance, I’ve been inside the White House situation room – once – but I’m certainly not well versed on the White House floor plan, something I needed to be if Kurt was going to keep seeing the president. Obviously, getting in and stomping around the president’s personal space was problematic. Luckily, there’s an entire website dedicated to the history of the White House, complete with the floor plan through the years and photos.

I try to do that with any scene I write, but I’ll be honest, if I need something, I’ll create it. For instance, the Four Courts pub where Pike is ambushed is a real location in Clarendon, Virginia. The streets around it are accurate, as are the Metro stops to get there. I cased that area as well, trying to figure out how I would ambush Pike (and get a Guinness at the pub). I planned the ambush realistically, but added an alley to the left of the pub. It doesn’t exist in real life, but it does in my book. I know that sounds hypocritical, but I did this because in the end the writing does come first. The alley was critical to the story. 

I’ll fake things for reasons other than the story as well. Writers without my background can guess how widget X works, and if they get it right everyone wonders how they got the information. My problem is the opposite: I do know how things work, and most of that knowledge is classified, so I have to spend a lot of time tempering what I know when I write, even if it seems mundane. For instance, I’m currently working on a scene for book two where terrorists attack an Army Ammunition Supply Point. I traveled to and studied the ASP, then simply wrote how I would hit it to get to the ammunition inside. After I was done, I read it and thought, “What the hell are you doing? You’ve just written a blueprint on how to attack a U.S. Federal facility!” My insider knowledge, coupled with my tactical skill set, had made it too real. I had to go back and throw in some red herrings. I know I’ll get dinged on that by someone with the same knowledge as me, saying, “That would never work,” but that’s the point. 

In the end, I fall on the “research” bandwagon, although I realize there’s no way I’m going to be perfect. Mistakes will happen, no matter how much research I do, and I want to kick myself when that occurs, but it’s just the way of writing. Pike steals a Chevy Cutlass in Guatemala City to escape, and after all of the research on the city itself, I’m told by an advanced copy reader – after I’d blessed the final manuscript – that Chevrolet didn’t make the Cutlass. Oldsmobile did. 

Mistakes like that don’t make me throw my hands up at the futility of it all, because I owe it to the reader. My cut-line on real versus make-believe is the story itself. If you make something up for the purposes of the plot, knowing it’s wrong, and it makes the story stronger, then you’ve enhanced the enjoyment of the reader. On the other hand, using the story as an excuse for a lack of research is really just a shortcut – and the reader will know it. Maybe not all readers will care, but even if only one does, you’ve failed.

Brad, thanks so much for guest blogging here today. Research does add another layer to the story. From a reader’s viewpoint, I appreciate when an author has gone that extra step to do research for their book. It means to me they care.

For more on Brad and his writing, check out his website at www.bradtaylorbooks.com 

What are your thoughts on research? Do you think readers pay more attention to details than they once did?

REMEMBER -- if you live in the Atlanta area you can meet Brad on Feb. 27 at his book signing. Tell him you heard about it here!