philcrissman's dashboard

var protocol = (("https:" == document.location.protocol) ? "https://" : "http://");
document.write(unescape("%3Cstyle type='text/css'%3E@import url('" + protocol + "s3.amazonaws.com/getsatisfaction.com/feedback/feedback.css');%3C/style%3E"));
document.write(unescape("%3Cscript src='" + protocol + "s3.amazonaws.com/getsatisfaction.com/feedback/feedback.js' type='text/javascript'%3E%3C/script%3E"));
document.write(unescape("%3Cscript type='text/javascript' charset='utf-8'%3E"));
document.write(unescape("GSFN.feedback('" + protocol + "getsatisfaction.com/[your company]/feedback');"));
document.write(unescape("%3C/script%3E"));

I think the trouble is, the average user of enterprise software has not chosen to use it; his or her CIO chose it, and now the user's stuck with it. ;-)

APIs. Let the users, the internal IT departments, etc, have access to the data that is in the systems. They should be able to *easily* write their own extensions, modules -- basically, enterprise mashups.

Something like these may already exist, but I've been thinking that the only way for Enterprise apps to mirror the success that consumer web 2.0 apps have had is to emulate the openness of the APIs, open up the data, so to speak.