TiggerBouncy
DIS Veteran
- Joined
- Mar 4, 2013
- Messages
- 2,885
Totally understand. We were owners for about 6 years. It helped to know other visits were on the horizon, but if we were owners now I’d be really sad and frustrated.
TBH as a DVC owner, I am less bothered by G+ then I would be if I were not a DVC owner. The thing is, I know this will get worked out in time and I know that I will still be going when it does get worked out. Change is inevitable. Changes to G+ are inevitable, too.
While it may be a more open playing field, you are still ending up with the same (and actually probably more) amount of people who want to get a pass for a ride and can't. G+ doesn't change that because the capacity is the problem, not when people schedule it.
<snip>
There's no going back, but they could definitely make G+ more useful. Being able to modify your time/choose a time would help a lot. Or being able to book the night before or something if not farther in advance.
So I do not disagree with a thing you said. I agree that although a more open playing field, it doesn't actually solve the problem. The only REAL way to solve the problem is either more rides or less people. I personally do believe that there will be in the future some limited capacity to plan ahead. As far as I can tell, G+ has the CAPACITY for future planning. It's just not enabled yet. Probably because they are still feeling the system out. I think the single biggest thing they could do however to help the system RIGHT NOW is reserved time slots when doing a purchase. Believing you are buying a pass for 11am and then finding out it is really for 4pm is a serious problem.
I don’t think 7am is as big an issue as it first appears. As long as you book by park open there is usually pretty good availability for most rides and you can still book your next G+ LL at park open +2 hours.
I don't have a major problem with availability at 7am. I have a problem with not getting the time you are buying.
And THIS is why is chaps my behind so much….I understand projects have schedules and we drive to meet them. However, the ONLY schedule driver here was to START MAKING MONEY. There was no safety issue that had to be addressed immediately, or an event that huge software MUST precede of it would be moot, etc. They crammed this into the market whether it was ready or not so they could start monetizing it regardless of the experience it was going to provide the guests.
To be honest, it's probably not even directly related to making money. MOST TIMES I have seen this, It's driven by the PM or Management that doesn't want to be seen as failing to deliver. 99.9% of the time (and this is why I do not blame Chapek), if IT management came forward and said "we can deliver a product on the schedule we originally told you, but it will suck and piss off our guests, OR we can take another 3 months and do it right" management - given those choices - will choose option B.
The problem is that some new, inexperienced, insecure Project Manager or IT Management doesn't want to have that discussion. They want their boss to thing they are the bee's knees. They MISTAKINGLY believe that pushing to be on a schedule, even when failing on the product is better because they believe that the bugs are never as bad as the developers and testers claim they are. They think devs and testers make up stuff because they want to justify jobs and pay. So they make really moronic choices and push projects that shouldn't go out when they should just go up the chain and say "it's not ready yet, but here is our plan and when it will be".