We’ve had great success with our ITSM platform and now HR and Facilities want to hop on board. However, I’m worried about over-complicating the system for non-technical users. What are the best ways to scale these service principles to other departments while maintaining a unified employee portal? Should we use separate instances or one giant shared service catalog?
3 answers
The biggest mistake you can make is forcing HR to use IT terminology. We implemented a "Single Pane of Glass" portal but used different "Views" based on the service category. Behind the scenes, we kept a unified CMDB but separated the workflows. For example, a "New Hire" request triggers a sequence across IT, HR, and Facilities simultaneously. This creates a seamless experience for the employee while allowing each department to manage their own specific tasks and SLAs. Focus on the "Service Request" journey from the user's perspective rather than the internal silos.
When you combined these departments, did you face any major data privacy issues, especially with HR records being in the same system as IT?
Start small with a shared "General Inquiry" form to see how the departments interact before building out complex, multi-departmental workflows.
Great advice. Starting small allows you to iron out the governance issues before things get too complex to manage effectively.
Kevin, privacy was our #1 concern. We solved this by using strict ACLs (Access Control Lists) and data encryption at rest. IT administrators can manage the platform's health, but they have zero visibility into the content of HR cases marked as "Confidential." You must ensure your ITSM platform supports granular scoping so that sensitive data stays within the appropriate department while still benefiting from the shared infrastructure and reporting.