Quote:
Originally Posted by Aerosmit
We struggled last year with team communication, parent communications, event/trip management and taking payments; most through Google Docs.
|
If you struggled with Google Docs, consider specifically what was not working. Was it a problem with the software, or with your processes or training? View this upgrade the same as you would when designing an improvement to an underperforming robot - what isn't working? What features are required to fix it? Can you fix it with driver practice (or mentor/student/parent training)?
For example, if the problem was that many people did not log in to GD regularly, and you feel it unlikely that you will change that behavior, then an important feature of your software solution might be to distribute e-mail/text/twitter/whatever to get the word out to as many people as possible, preferably from initial "posts" in as few forums as possible.
And OBTW: How much training will it take each class of people to learn to use the new software/system? Once you have an initial set of possibilities, also look for deficiencies that may cause your experience to degrade further.