Seen it done through many methods, some smart and collaborative, others not.
Word documents, Excel spreadsheets, SharePoint, System Center Service Manager, other bespoke tools (Onyx/Vantive/etc.) Ironically, one of the best I saw was a Lotus Notes database. I know, I know. I'd go SCSM if I had the option....otherwise, pick your poison. On 28 October 2014 17:09, Dave Lum <[email protected]> wrote: > We are defining a new change management process at %dayjob%. The current > consensus is to do it all via email, which for reason’s I can’t fully > explain gives me fits. I’ve been asked why not email and I can’t come up > with anything more useful than “new engineer starts and has no way to > review previous changes”. Kind of a weak argument… > > > > %dayjob% is a smallish company (~250 employees) that does have to worry > about HIPAA but currently shows no interest in following ITIL guidelines. > > > > What do you guys use and if not email, why not? > > > > *Dave Lum* \\ I.T. Garage > > [email protected] \\ 503.267.9764 (voice/text) > > www.theitgarage.com > > > > > -- *James Rankin* --------------------- RCL - Senior Technical Consultant (ACA, CCA, MCTS) | The Virtualization Practice Analyst - Desktop Virtualization http://appsensebigot.blogspot.co.uk
