@fred - thanks for all the explanations!
If there is a big difference between summer 10 and Christmas 10, shouldnât they have different numbers? This doesnât make sense to me.
Recalibrate, redifine and reset didnât really explain anything to me.
Yeah, it makes it hard to do apples-to-apples comparisons if the scales differe based on the time of yearâŚ
Why not just make it go to 11?
It does make sense. Itâs important to understand that each crowd level represents a * range* of wait times. Check out, for example, the 43-minute peak wait time range for Peter Pans Flight on a 10 day.
The scales donât differ based on the time of year. A 10 is a 10. But a 10 doesnât tell you exactly how long youâll wait. It indicates a likely range of (long) wait times per attraction. So, on December 26 youâll probably see lines in the highest end of the range and in July you may see wait times somewhere lower in the range. But both are still within the range expected at a 10 level day.
our times went up in October as well. disappointing but we will still go. But with regard to the 9, we have gone in the past over spring break when it was that busy. And yes, it is VERY crowded mid-day. But if you get there at RD and follow your plan, it can still be worth it. The first time I did that was a few years ago, when I think my kids were about 2-3 & 5, so it can be worth it even with little kids.
Arrive at rope drop. Follow a plan. Set your FPP as early as possible, super demand rides only. With heavy crowds, your opportunities for your fourth, fifth FPPs will diminish, especially for the big rides (Splash and Space Mountain), but you have a good shot at things like Pooh, Pirates, etc, so donât âwasteâ your first 3 on those. My dream scenario goes something like this: rope drop straight to Space Mountain, 9-10 SDMT FPP, 10-11 Peter Pan, 11-12 Splash. Set those, and Optimize a TP around it.
Perhaps the better approach is to ask one to consider the alternative. If the crowd levels stayed static for the sake of consistency but less accurate would that be preferable? Our philosophy is that accuracy is more important than consistency but our job is to balance the two. We feel that making a year-wide adjustment twice a year is fair.
Weâve considered that actually, and the statistics support it. Something like a separate label like âExtremeâ or âCapacity Crowdâ and then applying the 1 to 10 levels to everything else.
Though, if you had an 11, people would wonder why you didnât just make 10 louder
Why not more frequent updates? Even monthly or weekly? Wouldnât that result in the accuracy you (we) are looking for and less dramatic jumps so users wouldnât freak out as much when their numbers jump?
Arenât you inevitably going to have to extend the range for it to maintain meaning.?If attendance figures are going to increase year on year, therefore increasing queue lengths there are going to be more and more days that are 10. As a user I will not be able to differentiate between a âgoodâ 10 and a âbadâ 10. And isnât that the part of the reason for the crowd calendar - to help me decide when to go, in addition to preparing me for what my trip is going to be like?
Ok, some of us have been a little frustrated over this, especially those of us who are travelling within the next 30 days. But admittedly, you have a difficult job of maintaining accuracy, being realistic, and not angering the people you are trying to provide a service to. That being said, how much confidence do you have in your updated crowd predictions? I would like to make some changes to my plans based on the new information. For example, I have FPâs for Epcot on 6/16/15. I have just seen the predicted crowd level go from a 7 to a 10. I do not want to be at Epcot when the crowd level is a 10. Would you say that your crowd predictions through the end of June are now conservative? I need to make my changes ASAP. Please respond.
Also, have your updated crowd predictions been filtered through to the software for the personalized touring plans? If I re-evaluate all of my plans today, will the new crowd levels be reflected in the plans? Thanks.
I look at it like weather forecasts. Most local weathermen make 10-day forecasts - they are pretty much useless, but people want them so they make them anyway. However, what would you want your weatherman to do as it gets closer to the day in question - say âI predicted sunshine a week ago, so Iâm going to stick with itâ or âThunderstorms tomorrow, better not go to the beachâ? Iâll go with accuracy every time.
Though, if you had an 11, people would wonder why you didnât just make 10 louder
Because⌠it goes to 11.
I donât think that we are in danger of that yet. Looking at the current CC for MK, there is still a good distribution of days:
CL - Count
1 - 14
2 - 24
3 - 23
4 - 37
5 - 45
6 - 58
7 - 52
8 - 52
9 - 43
10 - 18
The biggest problem with rescaling is maintaining a constant frame of reference. If you rescale, then inevitably users will say âI went last year on a 5 and it was fine, and I went this year on a 5 and it was horrible - it should have been a 7!â
Thatâs easy - Christmas week = bad 10, and other time = good 10.
DISCLAIMER: I am not an employee or otherwise affiliated with TouringPlans.com (although I do have a âstaffâ t-shirt). All conjectures about the validity of the TP projections are based on hours of pointless experimentation making TPs that I will never use, and analyzing CC data because I am a total geek.
Fred - the extreme level would probably be helpful to the layman. I understand the math but most donât. Only adjusting twice a year is going to cause these big swings, but know itâs hard to balance being precise in the numbers, with understandability for your consumers. Internally I could see the rational for only 2 times - thatâs only 2 times a year you have to field dealing with mad people about this issue. :).