At QuickSchools, we often debate on the best ways to present a new module, feature or enhancement. There is indeed a fine balance between control and flexibility. Too much control on a particular module and it can be regarded as too rigid, cumbersome, or hard to use. Too much flexibility and it might not fit what you’re looking for.
Here’s an example:
We recently posted a rather lengthy article on how to set up a QuickSchools account if you don’t have academic terms. Non-overlapping academic terms make it easy for schools to control which information (grades, subjects, enrolment, schedules, etc) is active, and which is archived. But this method of doing things impedes on the flexibility for QuickSchools to cater to schools that don’t have academic terms.
So how would we make the system both flexible enough to cater to schools that do not have academic terms, while still allowing the control for the term-based schools to easily move between academic terms?
This is one of the many challenges we face as a Software-as-a-Service (SaaS) vendor, where all customers work off the same code base. Rest assured, our engineers are continually looking for improvements that will work well for everyone.
We welcome suggestions to improve our product and services. If you’re not sure about something, come chat with us, or send us an email at email@example.com.