Data Transparency

When looking for the 10X in application design, one key concept that should be considered is access to the underlying data elements. Whether its in the delivery of reporting services, or in the fundamental permissions of the users, providing access to the underlying data schema is essential. The end user needs to feel that he (she) owns the information. If you put barriers between the data layer and the user, they become immediately disenfranchised with the application.
One of the greatest tool sets that I have ever worked with is called Query Builder. Tucked inside the reporting services of this particular browser-based application, Query Builder provided a drop-down list of all the tables AND views used by the application. When a particular table or view was selected, and the field names were displayed. Using this interface, I am then able to select and query against distinct fields or all. Resulting queries can be viewed, or exported through XML or Excel. For support staff, this is an incredibly powerful tool in troubleshooting the data elements. For the end-user, in provides an unlimited ability to generate literally any view of the data.
Microsoft's 2005 SQL Reporting Services offer much of the same empowerment through a different perspective. I will be providing more on that topic in the upcoming months.