I often wonder why IT projects within the healthcare sector, always takes a lot of time or end up so big, that the project management cannot handle them and the project schedule is delayed.
Often in IT projects there are a clear understanding of the business case, the goals and purpose of the system. But people never the less does not talk about what a pilot is for and why they have chosen that particular method and for example not a lab test instead. In healthcare there are no such things as a pilot, because we need to focus on patient security and a high quality of the delivered treatment. Pilots with less functionality or even simulated data flows, do not go well within that paradigm.
In my time in IT management in a big university hospital I heard more than the opposite doctors and nurses argue, that a pilot project would be ok, but not until that integration or that functionality is implemented as well. If project management give in, the project is growing and the pilot will not start until the entire system is in place, and that can take a lot of time. Low hanging fruit slowly ascends into the three tops so to speak, and are harder to reach.
Projects in the healthcare sector can be illustrated with one of my personal favourite Gifs. Everything is lined up, the field is well described and marked, the goal is clear and in sight and you has even implemented some organizational and functional routines to help the system into implementation. But quick the project gets to big and crashes half way towards a milestone.
I guess one way to solve the above paradox is to really understand and communicate the purpose of the pilot and not let the project grow out of its initial scope. Furthermore, always make it clear, that the system after ending the pilot might get shut down, so you will not make severe adjustments for a lot of money on a system that might not be implemented fully within the organization.
So my I guess my point is, that be careful with your health IT projects, get it aligned exactly with the business needs and don’t overdue the functionality. Keep the fruit low and don’t let perfect be the enemy of good.
Often in IT projects there are a clear understanding of the business case, the goals and purpose of the system. But people never the less does not talk about what a pilot is for and why they have chosen that particular method and for example not a lab test instead. In healthcare there are no such things as a pilot, because we need to focus on patient security and a high quality of the delivered treatment. Pilots with less functionality or even simulated data flows, do not go well within that paradigm.
In my time in IT management in a big university hospital I heard more than the opposite doctors and nurses argue, that a pilot project would be ok, but not until that integration or that functionality is implemented as well. If project management give in, the project is growing and the pilot will not start until the entire system is in place, and that can take a lot of time. Low hanging fruit slowly ascends into the three tops so to speak, and are harder to reach.
Projects in the healthcare sector can be illustrated with one of my personal favourite Gifs. Everything is lined up, the field is well described and marked, the goal is clear and in sight and you has even implemented some organizational and functional routines to help the system into implementation. But quick the project gets to big and crashes half way towards a milestone.
I guess one way to solve the above paradox is to really understand and communicate the purpose of the pilot and not let the project grow out of its initial scope. Furthermore, always make it clear, that the system after ending the pilot might get shut down, so you will not make severe adjustments for a lot of money on a system that might not be implemented fully within the organization.
So my I guess my point is, that be careful with your health IT projects, get it aligned exactly with the business needs and don’t overdue the functionality. Keep the fruit low and don’t let perfect be the enemy of good.
Ingen kommentarer:
Send en kommentar