Edition 1: Wait Times
For those of you who know me, you know that I have a tendency to sometimes be a little long-winded. So buckle up.
There is no doubt that over the past few years, the overall quality of Busch Gardens Williamsburg has been in decline. More than anything, though, guest service has certainly been slipping. However, it seems to me that there is a growing attitude of superiority on this forum over many of the park employees. No matter how small this may be, I don't like it. Yes, I've had my beefs with the quality of guest service by management and team members alike over my past few visits, but I still respect them for what they do.
As the guests who know the park the best, it's easy for us to feel like we know how things are supposed to run, how long a wait should be, or how an employee should handle certain situations. Compared to the GP, we're much more knowledgeable, but compared to the team members who work the park and run the rides day in and day out, I assure you, we don't know nearly as much as we think we do. The team members absolutely owe it to us to provide the best service possible, but as the guests who know the park the best, we are equally responsible for being the best guests in the park.
As someone who has operated rides for a major theme park, I have experienced both sides of the industry. Sometimes guests are just impossible to deal with. Sometimes you'd swear they left their brains in their cars. And you'd think that the pass holders, the fans who loved the park the most, would offer you a reprieve, but they are often the worst. I don't care if a guest had been a pass holder for thirty years, they never knew the SOP better than I did. That seventeen year-old who operates Apollo's Chariot may not know that Ireland was once Hastings, but you better believe he knows the ride SOP better than you do.
I'd like to offer you some insight into the theme park world from the perspective of a ride operator. Please consider these things when you visit the park.
An issue that has come up recently on the site is that of wait times, so I'll tackle that one first. Let's get started!
The posted wait times at the front of a queue are there to give you a rough estimate of the wait so that you don't unwittingly enter a two-hour line. That's it. Nothing more. Rule #1:
Never take a posted wait time as gospel.
If a wait is posted at 45 minutes, but it looks like it may be closer to 30, we're not going to fret about it. If a team member is at the entrance and feels so inclined to change it, they might. Typically, if the posted wait is +/- 15 minutes, that's accurate enough. There are far too many variables that affect a wait time to try and constantly keep it accurate. Remember, our primary job is to safely and efficiently operate the ride, not to provide accurate wait times.
But that's ok, because you've been here before and you've ridden the ride. You can eyeball the line yourself based on past experience. Rule #2:
Never estimate a wait time based on your past experience.
Yes, the posted wait may very well be off by 15 minutes, just like you think. But remember, there are a lot of variables involved in estimating wait times. Team members are given some rough guidelines to providing the wait times. For example: "If five queues are open, the wait on average is 45 minutes." So on an average day, that guideline should be correct.
However, it is quite possible to have a line that is the same length three different days that produce three completely different wait times. And I'm not taking downtimes into account here. Assuming normal, smooth operations that are the same across all three days, the wait times can still be completely different.
But how, Franco? Good question.
The speed of the crew is a huge factor in the overall wait time. If you ever see a crew doing a great job and working really hard to get people through a line quickly, get some names and leave a compliment at GR. That crew is going way above and beyond, and many parks give monetary awards for guest compliments, which are relatively rare.
So let's say the wait is accurately posted at 45 minutes. This crew is on their A-game, though, and you get through the line in 30. Lucky you! You were just saved 15 minutes. (For anyone who doesn't believe that a crew can make such a big impact on the wait, they absolutely can. I used to operate a popular coaster with a fellow team member, and we were very, very fast. If the park closed at ten, we could take over an hour-long wait after 9:30 and have the ride shut down before 10:15).
On an average day with an average crew, the wait is posted at 45 minutes and should come out to around 45 minutes. You're not there that day, though. You come back the next day when...
There's a slow crew working. It only takes one. Even if there's three lightning-fast team members running the ride, one molasses-slow employee will drag them all down to his/her level. It can't be avoided. And if the park is understaffed that day, the faster team members are usually the better ones, and the better ones are usually cross-trained on more rides in more units. The odds are greater that you will face slow crews on these days.
So now you show up, and you see the wait posted at 45 minutes. You peer into the queue. It's the same length as last time! So now you know that it should really only take 30 minutes. Except this time, it takes an hour. Keeping with the over/under 15 minute rule, this is still ok, but since it took thirty minutes longer than you thought it should, you're going to get angry. You're only setting yourself up for failure here.
Throw a downtime or two in the mix, and things get crazy in a hurry.
Sometimes, a wait time may be considerably overestimated. If you get in a line that has a posted hour-long wait and it only takes ten minutes, then you probably came right on the heels of a downtime without realizing it. Following a downtime, I'm not going to change the wait time. Why? Because during the downtime I have to stay in a fixed position, and I cannot always accurately judge how many people left the line, or how long the wait in the queue is now. It is better for the wait to be overestimated for a period before the line returns to a sense of normalcy. If it takes you only half as long to get on as you thought, that's a pretty good deal for you, and you're going to be happy. But if I guess when I change it and it's too low? It takes twice as long as you expected, and now you're mad. Better to under-promise and over-deliver in that scenario.
If you do, however, encounter a wait time that is grossly underestimated (off by 30 minutes or more), you should inform GR on the way out of the park.
So there you have it. An inside look at wait times and how they affect you. I hope this helps you consciously try to be a great guest. Guest service is a two-way street. Being an accommodating and understanding guest can help team members deliver great guest service to others.
Next time, I'll cover downtimes, a topic that most guests, even the most well-intentioned ones, make most team members, even the most well-intentioned ones, go crazy.
For those of you who know me, you know that I have a tendency to sometimes be a little long-winded. So buckle up.
There is no doubt that over the past few years, the overall quality of Busch Gardens Williamsburg has been in decline. More than anything, though, guest service has certainly been slipping. However, it seems to me that there is a growing attitude of superiority on this forum over many of the park employees. No matter how small this may be, I don't like it. Yes, I've had my beefs with the quality of guest service by management and team members alike over my past few visits, but I still respect them for what they do.
As the guests who know the park the best, it's easy for us to feel like we know how things are supposed to run, how long a wait should be, or how an employee should handle certain situations. Compared to the GP, we're much more knowledgeable, but compared to the team members who work the park and run the rides day in and day out, I assure you, we don't know nearly as much as we think we do. The team members absolutely owe it to us to provide the best service possible, but as the guests who know the park the best, we are equally responsible for being the best guests in the park.
As someone who has operated rides for a major theme park, I have experienced both sides of the industry. Sometimes guests are just impossible to deal with. Sometimes you'd swear they left their brains in their cars. And you'd think that the pass holders, the fans who loved the park the most, would offer you a reprieve, but they are often the worst. I don't care if a guest had been a pass holder for thirty years, they never knew the SOP better than I did. That seventeen year-old who operates Apollo's Chariot may not know that Ireland was once Hastings, but you better believe he knows the ride SOP better than you do.
I'd like to offer you some insight into the theme park world from the perspective of a ride operator. Please consider these things when you visit the park.
An issue that has come up recently on the site is that of wait times, so I'll tackle that one first. Let's get started!
The posted wait times at the front of a queue are there to give you a rough estimate of the wait so that you don't unwittingly enter a two-hour line. That's it. Nothing more. Rule #1:
Never take a posted wait time as gospel.
If a wait is posted at 45 minutes, but it looks like it may be closer to 30, we're not going to fret about it. If a team member is at the entrance and feels so inclined to change it, they might. Typically, if the posted wait is +/- 15 minutes, that's accurate enough. There are far too many variables that affect a wait time to try and constantly keep it accurate. Remember, our primary job is to safely and efficiently operate the ride, not to provide accurate wait times.
But that's ok, because you've been here before and you've ridden the ride. You can eyeball the line yourself based on past experience. Rule #2:
Never estimate a wait time based on your past experience.
Yes, the posted wait may very well be off by 15 minutes, just like you think. But remember, there are a lot of variables involved in estimating wait times. Team members are given some rough guidelines to providing the wait times. For example: "If five queues are open, the wait on average is 45 minutes." So on an average day, that guideline should be correct.
However, it is quite possible to have a line that is the same length three different days that produce three completely different wait times. And I'm not taking downtimes into account here. Assuming normal, smooth operations that are the same across all three days, the wait times can still be completely different.
But how, Franco? Good question.
The speed of the crew is a huge factor in the overall wait time. If you ever see a crew doing a great job and working really hard to get people through a line quickly, get some names and leave a compliment at GR. That crew is going way above and beyond, and many parks give monetary awards for guest compliments, which are relatively rare.
So let's say the wait is accurately posted at 45 minutes. This crew is on their A-game, though, and you get through the line in 30. Lucky you! You were just saved 15 minutes. (For anyone who doesn't believe that a crew can make such a big impact on the wait, they absolutely can. I used to operate a popular coaster with a fellow team member, and we were very, very fast. If the park closed at ten, we could take over an hour-long wait after 9:30 and have the ride shut down before 10:15).
On an average day with an average crew, the wait is posted at 45 minutes and should come out to around 45 minutes. You're not there that day, though. You come back the next day when...
There's a slow crew working. It only takes one. Even if there's three lightning-fast team members running the ride, one molasses-slow employee will drag them all down to his/her level. It can't be avoided. And if the park is understaffed that day, the faster team members are usually the better ones, and the better ones are usually cross-trained on more rides in more units. The odds are greater that you will face slow crews on these days.
So now you show up, and you see the wait posted at 45 minutes. You peer into the queue. It's the same length as last time! So now you know that it should really only take 30 minutes. Except this time, it takes an hour. Keeping with the over/under 15 minute rule, this is still ok, but since it took thirty minutes longer than you thought it should, you're going to get angry. You're only setting yourself up for failure here.
Throw a downtime or two in the mix, and things get crazy in a hurry.
Sometimes, a wait time may be considerably overestimated. If you get in a line that has a posted hour-long wait and it only takes ten minutes, then you probably came right on the heels of a downtime without realizing it. Following a downtime, I'm not going to change the wait time. Why? Because during the downtime I have to stay in a fixed position, and I cannot always accurately judge how many people left the line, or how long the wait in the queue is now. It is better for the wait to be overestimated for a period before the line returns to a sense of normalcy. If it takes you only half as long to get on as you thought, that's a pretty good deal for you, and you're going to be happy. But if I guess when I change it and it's too low? It takes twice as long as you expected, and now you're mad. Better to under-promise and over-deliver in that scenario.
If you do, however, encounter a wait time that is grossly underestimated (off by 30 minutes or more), you should inform GR on the way out of the park.
So there you have it. An inside look at wait times and how they affect you. I hope this helps you consciously try to be a great guest. Guest service is a two-way street. Being an accommodating and understanding guest can help team members deliver great guest service to others.
Next time, I'll cover downtimes, a topic that most guests, even the most well-intentioned ones, make most team members, even the most well-intentioned ones, go crazy.