I appreciate the technical difficulties inherent in legacy code and systems; probably much more than the average scoutmaster as I work in an environment where we have to to support code from 1995, yet incorporate cutting edge code and modern systems as well. I don’t disagree with any of the engineering you are talking about, and logically it all makes sense to me.
My issue with these new implementations is that they don’t seem to be user focused solutions; at least from my perspective. It appears these are engineering solutions with no unified design structure.
You seem to be suggesting that I should adapt and change my workflow to accommodate engineering difficulties?
From my perspective you are making it more difficult for me in order to make it less difficult for engineering. It’s problematic for me to constantly be flipping between websites where I need to reenter my credentials each time and learn new interfaces for each module. It’s also a big deal to learn, then train other volunteers and parents, each time you change how various modules work.
I like to give concrete examples for engineers so here’s one example: To add service hours I used to log in to scoutbook, select quick entry -> service hours -> select scouts, put in the date, event, and hours in decimal format (i.e. 1.5 hours), and hit enter.
In the new interface, I need to either know to go directly to a new website, or select quick entry -> select enter activity logs -> log into IA -> select roster -> know to checkbox scouts without selecting them-> know to scroll back to the top of the page to select a dropdown that changes from light grey text to white text -> create a new activity -> enter a lot of information that I’ve never had to enter before, but looks at lot like JTE, in order to add service hours. Even after I do all that, it appears that 1. I can’t delete the event if I make a mistake and 2. the hours from new events are not adding up correctly with the hours of past events.
That’s a single example that is making it more time consuming and difficult for me. So yes, change is difficult, especially when the change makes it 1. harder to do basic tasks, 2. is buggy, 3. doesn’t add any additional functionality from a user’s perspective.
Furthermore, am I expect to keep up with the forums in order to know that workflow design changes are being implemented? Is there a specific thread about workflow changes I can follow, and set to get email alerts with updates, like the old scoutbook forum used to have?