I was having coffee with my friend Bill Seaver recently and extolling the virtues of “Avoiding a Goat Rodeo” when he asked me a question that stopped me in my tracks.
“So, in this scenario, who is the goat?”
Honestly, I didn’t have a good answer. I mean I knew the title was perfect for the book once I heard myself say it out-loud. I knew it worked because the definition of a goat rodeo is a perfect definition for a lot of web projects. That having been said, I really hadn’t spent the time to define the roles. I had to sit, sip my coffee and think for a moment.
The answer is of course, there doesn’t have to be a goat. The potential goats in your website project are all the people and processes that revolve around it. Yes, your webdesigner is a possible goat in your goat rodeo, so is your developer, the person in charge of hosting your website and your domain registrar as well as your SEO person and content strategist.
All of them are potential goats because they are all players in your website project. They are only goats though, if your project actually turns into a goat rodeo. That is what “Avoiding a Goat Rodeo” is all about. It teaches you how to think about your project, how to plan your project and how to communicate your project so that your project does not become a Goat Rodeo.
Want more helpful advice?
Are you looking for more helpful advice? Check out our book, Avoiding a Goat Rodeo. It was written to help non-programmers understand website development. It shows you how to get the website you want.