Good and bad of QuickBase
Overall Satisfaction with QuickBase
It's used for various projects that our company undertakes for clients. The predominant use is for managing PMOs (Project Management Office), specifically tracking high level milestones and dependencies of complex health programs. These QuickBase apps also had a risk and issues management component.
Other uses of QuickBase include:
• Defect management tools where software defects are logged, allocated for fixing, tested and closed.
• Risk management tools where risks are logged and actions developed, assigned and tracked individually
• Readiness assessments, e.g. delivery of large scale new public service facilities
Other uses of QuickBase include:
• Defect management tools where software defects are logged, allocated for fixing, tested and closed.
• Risk management tools where risks are logged and actions developed, assigned and tracked individually
• Readiness assessments, e.g. delivery of large scale new public service facilities
- Powerful reporting. Initially challenging for non-technical people, but once they get a grasp, this is really one of the key features of QuickBase which I sell to both internal and external clients.
- Generally user friendly.
- Licencing costs are cheap and since there is no installation, it's easy to deploy adn customise a base generic app and deploy it into a project.
- Control of width of columns in tables.
- Better reference guides on APIs.
- Better triggers, not just when a record is changed but when a threshold is reached, certain value is inputted, etc.
I have built some standard app templates which are about 85% completed. The remaining 15% have to do with business processes which would differ from project to project.
I was not involved in the original selection process but from what I understand, it was a mix of functionality and price which was the deciding factor.
All support in development is pointed towards the technical team. The most complex thing which users do is reporting and data import/export.
- Improving our ability to drive insights from our data
- Improving collaboration across one or more teams
- Solving a specific business challenge
Very easy to do for anyone with technical knowledge. Relationships are probably the hardest thing for someone who has not built the system to understand.