Silo-ing as an organizational principle almost always goes wrong and what you end up with is a stovepipe organization.
IMO, the worst are the full page, content-blocking, app install requests that appear on thin-content sites.
It's preposterous.
You've proven that you can't be trusted to present your website content in an acceptable manner, and you want me to install your software?
Instant back button.
Almost all studio was Windows, and you had to use specific browser, with specific Java installed (for some reason our integration/use of it required java in the browser - that was at least year ago).
When you open the web-app, sometimes it might not work, when it does it starts with the "bereavement" page (wtf). Then if you want to request vacation that crosses weekends, you have to do it for individual ranges of normal work days. e.g. Also had to be careful not to select work holidays (MLK, 4th July, etc.)
That was my use of it... for very short amount of time I was manager to an intern, and had to watch and clock their hours. I had to be trained for 2hr, and still did not get it (I'm a software engineer... duh).
But then people claimed it had better new UI, which we did not use (reason unknown), and was pretty powerful.
Other than that it's pretty useable. At least compared to SAP, which is my only other timesheeting-experience.
The end users usually just have to deal with it, and go whereever they get jobs.
http://www.theguardian.com/technology/2006/feb/09/guardianwe...