Peter Haller

Remco, that is very nice and sympathetic and I am sure includes some reality. But people have also asked for the ability to simply disable it from the interface if it can't do anything whatsoever that we want it to and thus only serves to confuse new users. Nobody here who develops software honestly believes doing only that would be a multiyear challenge.

+1

The problem is that mistakes cost money, poor process costs money, training costs money, and anything someone has to hit every day that's clearly useless detracts from the solution, and detracts from the acceptance of that solution as a good thing. None of my users know what it would be like if we did everything on a different platform - at best someone who worked elsewhere knows how it used to be, but they do not have any present-day benchmark. Zendesk is only as good as it appears to be. 

Having to train every user that the main view on a system is useless and that using it will be a mistake would only make sense if fixing it were costly. Can it really be costly to provide a 'Default' view to use instead? Yes, you can bookmark a different view, but the Home button remains the Home button, so users will think that is what it is. So why not disable it or fix it?