I find myself in the position of doing more & more drupalling- at work (IT department of large chemical company). I have started using drupal for documenting code I write for internal clients, and now have delivered a few proofs of some new concepts (e.g. a front end for department-wide Subversion repository).
IT leaders in my dept have started asking me to deliver features for them. There is a push to move our monthly progress reports from Lotus Notes into Drupal. People are getting interested in the idea of newsletters, discussion forums & even internal blogs (unheard of in our corporation)! People have been trying to get more collaboration in my company for decades (and spent millions)- is it outrageous to try to position Drupal for this?
I am sure there are a million gotchas here. I was thinking I should deliver a single bit of functionality at a time and resist to much "diarrhea of the modules". Also, since no newsletter module is available for 4.7 yet, some in my dept have taken to using discussion forums to capture monthly progress reports. This is not the intended purpose of forums, and I wonder what trouble I am in for if I let it go.
Any advice as to how to effectively roll out Drupal for a corporate intranet? I did not see a site recipe in the handbook on using Drupal for fostering collaboration among employees of corporations. Maybe we could capture some such ideas here?