top of page
Frequently asked questions
Is there a process map of your preferred way of working after purchase?
A process map is essential to guide configuration and training. It should clearly outline the “to-be” workflows agreed during prework, ensuring all stakeholders understand how tasks will flow post-implementation.
Is there an IT Lead who will take responsibility for project timelines?
Assigning an IT Lead ensures accountability for technical readiness, integration, and adherence to go-live dates. This role is critical for coordinating between the vendor, IT, and operational teams.
Do you need to book an “IT Sprint” based on a go-live date? How would you book this?
Yes, many trusts schedule IT sprints to prioritise configuration, testing, and integration tasks before go-live. Work with your PMO and IT team to allocate resources and confirm timelines early.
Have you created a plan for prior, during, and after implementation?
A phased plan should cover pre-go-live activities (training, testing), go-live support, and post-go-live stabilisation. This ensures continuity and minimises disruption.
Who will require training?
Identify all user groups - portering teams, clinical staff, supervisors, and administrators. Each group may need tailored training to match their role and responsibilities.
What resources do I need to train electronically?
Consider video tutorials, e-learning modules, and digital guides so staff can learn at their own pace. Combine this with hands-on sessions for practical experience.
Why is go-live support important?
On-site or remote support during go-live ensures quick resolution of issues, builds confidence among users, and reduces operational risk.
Is there a Business Continuity Plan in place?
Yes, this is vital. The plan should outline fallback procedures if the system experiences downtime, ensuring patient care and porter requests continue without disruption.
How important is change management during implementation?
Change management is critical to adoption. Communicate benefits clearly, involve stakeholders early, and provide ongoing support. A structured approach reduces resistance and ensures smooth transition.
Should we start small or roll out everything at once?
A phased rollout - “eat the elephant in pieces” - is best. Start with a pilot area, refine processes, and expand gradually. This minimizes risk and builds confidence across the organization.
What is the long-term strategy versus short-term rollout?
Define a long-term vision for full adoption but break it into short-term, manageable steps. This approach ensures progress without overwhelming staff or resources.
If you didn’t find the answer you were looking for, our team will always be happy to help. Please contact us.
Contact Us
bottom of page