Benefits of Early IT Project Involvement
In the 90s, you didn’t need an IT department to get involved when installing foodservice software in a hospital. There were times when the foodservice director was all the person you needed to interact with. To be fair, software systems and computers weren’t as complex back then as they are today. Time travel to the present and you can’t (and should not) exclude them when it comes to installing an enterprise-level software system. Here are a few reasons why:
- It is important in any project to engage with IT early on in the analysis stage in order to not only gauge the level of effort but to see where this would fall on IT’s project schedule.
- IT typically has a booked project schedule spanning years. So getting on that schedule early is critical to the project’s success. We have seen many times IT being pulled in during the implementation stage only to have the timeline missed because IT could not commit the resources to the project. This happens many times when IT doesn’t have the project on the schedule and it is deemed a lower priority over the projects currently on the schedule.
- In any enterprise-level software deployment there are typically infrastructure requirements in order to implement the solution. These can be things like servers, workstations, mobile devices, printing or other peripheral hardware, and networking requirements. It is important to get IT involvement early on in order to not only properly cost out your project but to ensure the solution fits into your current technology stack.
- There are also other considerations to take into account that could have an impact on the proposed solutions deployment methodology. Discussions early on can lead to the solution being tailored in a certain way that may not be appropriate if IT has not been informed. Starting this process early on will help to smooth things out as you remove any surprises that could have a cost or timeline impact.
- It is also important to engage with IT to go over the project scope in order to truly determine costs and put together your ROI.
- In any organization there is typically some sort of IT security posture that dictates policies and procedures used. In most cases this means IT will have some sort of internal approval process that they must go through in order to make a new purchase. Our experience has shown this to be anything and everything from very minimal, maybe just a few calls and emails explaining the system architecture, to a full IT security and compliance review that could entail various highly detailed questions and/or legal documentation. These can take some time to complete and approve so the earlier in the process it can start the less likely they will impede the project.
The IT department’s role is critical in today’s healthcare environment. So get them involved early in your project, so they can help contribute to its success.
Article by: Benjamin Blood, Technical Sales Engineer; Fusion, 2nd Quarter, 2016