I wrote some SharePoint code, couldn't help myself. A customer wanted some default text inserted as the description of a site in their new site provisioning process to save them a bit of time instead of opening a document where they store this standard text and copy & paste it in. Turns out that their process involves an awful (as in sickening) amount of copy & past between an email, 3 spreadsheets, employee directory, Portal Site Directory page and the new WSS site settings pages. Oh, and this process takes 20 minutes!
So I did the change they requested (took 5 minutes) then proceeded to document the current process and propose a new process that should cut the 20 down to 2 minutes.
Only problem, it means I have to write more code…
I'm on a mission with this particular customer to eradicate all no-financial spreadsheets and make this data visible and able to be used directly in supporting the business process that it supports (SharePoint Lists and connected Data Views). I've used the term "Workbench" to provide pages for specific tasks. All the pages share the same list/library data but aggregate in ways that assist with the task people need to perform.
It all comes down to information architecture and getting people to see that SharePoint is not just about documents & collaboration.