Lessons from the WFGC Hotel Blog-Hop Anthology: Part II

HOTEL Anthology logo

Hello! This is Part II of What I Learned from the WFGC Hotel Blog-Hop Project.

If you haven’t read Part I yet, I highly suggest you read it first.

 

In April of 2019, my friends and I from the WFGC released the Hotel Blog-Hop Anthology. As a spearhead of that project, I learned several lessons about people, leading, and what goes into creating a project. This is Part II of What I Learned. Have a laugh at my expense and, just maybe, avoid some of our mistakes. If you haven’t read the anthology yet, links to all the stories are on the WFGC website.

“Not Everyone is Going to Finish”Finish Line

When the second round of people dropped out of the project, I was getting discouraged. Brian Buhl had a conversation that turned things around for me. He told me to make sure, when people asked if they could do Thing A or Thing B, that I make every effort to say Yes instead of no. He reminded me this was not a professional contest, nor a book. We didn’t want to turn people away over silly rules that were not necessary.

He also explained that some people are always going to quit. They get excited initially, but either don’t have the wherewithal to complete it, or more likely, life gets in the way. Don’t get me wrong, I was still put out some, but it made sense. I extrapolated from this that it would be true with any contest/anthology/blog-hop, but it isn’t visible to contestants. Brian also helped ensure I didn’t hold any animosity towards those who quit by making sure I realized they were human…just like me.

What I learned about losing people on a project:

Everyone is human, and I must remember this always.

Your project may be your baby, but that doesn’t make it important to everybody else.

Everybody faces obstacles in life, and they have the right to decide what they want to take on. There’s no point in taking their decision personally.

 

Marketing NumbersMarketing is NOT My Strongpoint

Towards the end of the project, deadlines loomed over everybody. In a week, we were all supposed to be hitting Publish on our awesome Hotel stories, yet not many people outside the WFGC knew anything about it. And I had no plans save putting the links all over the Twittersphere the day of.

In swooped Chris Henderson Bauer wanting to know the plan. Discovering there is none, she took it upon herself to get our collective asses in gear. My words, not hers.  She also developed a tweet template for all involved authors to use for pre-published marketing. In short, Chris saved us from complete and utter anonymity after all this work.

What I learned about marketing:

A “day-of” plan is not good enough if you want to garner attention outside of those who already know what you’re doing.

If you can, allow an entity larger than yourself to help spread the word. In most cases, this probably involves money, but not always.

Marketing is one of the most important aspects of any project- having eyes on it and interest built up before release day is not going to hurt you. However, that means having a plan and enacting it an appropriate amount of time before the official release.

 

Hitting “Publish”

You can probably imagine that we had less than a perfect launch day. Imperfect (and in some case zero) systems in place, less information given out than usual, and unfinished stories all led to confusion on launch. I failed my responsibility for having systems and information in place, and it could be said I should have pushed those with unfinished stories to finish up faster.

Some might say I’m being too hard on myself. Maybe, but having a history of managing people, I think more could have been done on my part. I fell into a trap of “nobody will far apart if it’s not perfect” thinking, which I should have known better after that first week’s trials.

Regardless, the team managed to put out all the fires one by one, and by the thirteenth, every story was officially out in the world. I don’t know how much attention each individual author received from the Hotel project, and I hope it wasn’t so underwhelming that they wouldn’t consider doing something similar again.

What I learned from launch day:

If you’re leading a project, your job is not over until everybody else’s is, and you’d better be in the trenches or you’re not leading.

Having systems in place that work and are being actively used will help save you from putting out fires at the end of a project.

A “it doesn’t have to be perfect” mindset is a surefire way to ensure the end product is not as satisfying as it should be.

 

It may sound, at this point, like I did not enjoy the process of the WFGC Hotel Blog Hop Project. This couldn’t be further from the truth. I learned some hard lessons, sure, but a fairly large group of friends joined me in creating something cool in under three months. Sure, the process was harder than it needed to be at times. Those rough spots are behind us, the pain of them all but forgotten. The results are still live, and something all of us are proud to call our own. I’m proud of everybody who crossed the finish line with me, and even those who didn’t.

This was a project. I didn’t do it on my own, and I learned (in some cases, re-learned) excellent lessons. There’s really only one last question I have:

 

When are we doing it again???

Serious CircleHi! I’m James Neal, author of dark fantasy available on Amazon.

Granted, so is pizza. Mmmm…pizza.

Lessons from the WFGC Hotel Blog-Hop Anthology: Part I

HOTEL Anthology logo

In April of 2019, my friends and I from the WFGC released the Hotel Blog-Hop Anthology. As a spearhead of that project, I learned several lessons about people, leading, and what goes into creating a project. This is Part I of What I Learned. Have a laugh at my expense and, just maybe, avoid some of our mistakes.

What is the WFGC Hotel Project?

The WFGC Hotel Project is a blog-hop/ anthology of stories which was unleashed upon the world on April 10, 2019. The story however, begins in February. As you might expect, the theme of the project is a hotel. What is WFGC you ask? It stands for Write Fight Gif Club, a group of writers on Twitter who support each other. Often, we help with writing questions. Sometimes, if you prefer, we also provide procrastination.

If you haven’t read the anthology yet, links to all the stories are on the WFGC website.

Office Man

My Role

I sparked the idea of the project by having a short story that I didn’t know what to do with. When I asked WFGC members what I should do, talk of publishing a group anthology started heating up. The reality of the idea set in eventually, but many (including myself) were already excited. We decided to do a free blog-hop instead of publishing a paid anthology that would require contracts, rights, the whole nine yards.

I became the de facto “leader” of the project. I was to be the one to keep these forty or so interested writers invested in the project, follow through on commitments, and ensure the project came to fruition. Which it did, with a grand total of 18 stories!

I did not do it alone.

I did not do it alone. Fellow WFGC’rs Rhiannon Amberfyre and L.C. Marblewood handled damn near all of the registries and people tracking required for this project. Brian C. E. Buhl developed the timetable which we worked, almost exclusively, off of. Chris Henderson Bauer actioned our very short (not her fault) marketing campaign. What did I do? I answered questions, developed the Blog-Hop logo, wrote the project’s Survival Guide (with live updates as they happened), and created the projects website which is, essentially, a blog.

So what did I learn from this role?

People will lose the fervor of the initial idea and leave the project.

If you’re doing this for the first time, you have no idea what you’re doing.

Eventually, you must solidify ideas the group can work with, and this often includes compromise from your original vision.

 

Compromise

My initial idea for the project was simple: every story takes place in the same hotel, but within each room, absolutely anything can happen. It was even going to have the tagline: Every room tells a story. Why could absolutely anything happen? Because we wanted our authors to have room to write in any genre, and allow anything to happen, so long as the hotel as a whole wasn’t destroyed in the process.

Ultimately, it was decided that this vision was too limiting. Many people wanted to be able to exit the room and still have events happen. Several wished to have their characters meet with other author’s characters to create a sense of unity. Some people wanted to write stories outside of a singular hotel. All good ideas, and my initial vision did not support them.

We managed to make all of things possible, though it did steer my own story in a specific direction…the hotel needed to be a quantum, metaphysical space, and my story allowed that to happen…at least canonically.

This is what I learned about compromise:

The initial idea is not always best for the group.

I need to better my ability at persuasion.

Most times, it’s better to say yes, than no.

 

Everyone Needs to Understand What’s What. What?

Question Mark

The first three days after deciding we were actually going to do this were hectic. No, that’s an understatement. It was chaos. Forty people were throwing out ideas, nobody wanted to say no to anybody, and there was no plan of action. Attempting to answer those questions without a roadmap was pointless, but I was trying anyway (along with Rhi and L.C.).

We knew we didn’t want to limit genres pretty much from the get-go, but nobody understood how that was going to work if we kept to a single hotel. Many questions revolved around due dates, and on that we had absolutely no clue until we were almost a week out. We lost several people during this time. Not that I blame them. People are busy, have lives. If you cannot give them a simple piece of information such as “when do you expect me to get this to you,” they are not going to commit.

Rhiannon and L.C. came up with the idea of allowing people to “register into the hotel,” by assigning them a room number within our theoretical hotel. This worked wonders. People knew they were being kept track of, and would receive information as it came about.

I then created the Hotel Project Survival Guide, which put all known information in one place. I put that on Google Drive and allowed all interested parties to download it. It occurred to me soon after that the Guide would need to be updated regularly, and that is when I decided to create a website for the project. I’d never created a private one before, but thankfully, the process did not prove all that difficult.

This is what I learned about organization:

People need a clear plan of action, and it will be easier on everybody if that plan is already established.

When people do not have an actionable timetable, they will not commit b/c real life is hectic already and they don’t need to add stress to their life.

Simple systems which insure people will be informed and up to date create a sense of safety and take much of a project’s stress off your people.

This is Part I of What I Learned from the WFGC Hotel Project. Part II is also available. Thanks for reading!

 

Serious CircleHi! I’m James Neal, dark fantasy author with a novel on Amazon.

Granted, toilet paper is on there too…