flynnibus
Premium Member
You have more or less outlined our plan. There are a few differences, but you've more or less broken down the user interface and backend that I had in mind.
The key notion is "Now what you do is encourage people to update the list of effects and their status each time they ride - not just when things are broken"
The flaw with any 'effect tracking' thread and efforts in the past is the lack of frequent checks. This leads to misleading data. When was the last time anyone really even checked? That's why you need 'check-ins' all the time that include updates of bad AND goods.
The real problem is two fold
1) Managing the size of checks - you want to keep it managable and not have people checking in on every rail in the queue
2) Contributor frequency and ride coverage - need frequent updates, not once per quarter
If I had this tool and I wanted to make an impression? I'd create 'show effects reports' for each attraction in a one sheet printable format and I'd print them out every time I went to the park and I'd find the best person to share this list with every time. Every time I saw someone of importance I'd leave a copy with them. Will they throw it away? More than likely.. but if you just get them thinking about it just for a second.. you are making progress. You might trip guilt... You might make things aware they may not have been.. like they knew somethings were broke, but maybe they didn't know HOW much was broke, etc. Such an effort is all about raising awareness.
The backend and GUI isn't really complex at all - but you need someone to stop trying to shoehorn this into forums, etc. Use the right tool for the job.. and this is something that needs to be built. The good news is, this is completely generic and there is no reason such a backend could not be used for any park.