Rachel M-Keyser, PMP

Training or learning doesn't end. Some trainees might become competent, however others coming behind them will still need the training. It is always good to learn from the feedback, change some things that maybe can be taught better or differently. Feedback is critical to creating an overall organizational or SMB Training program for your team, business and organization as a whole. Additionally, perhaps looking to incorporate new tech workflows and methods of doing things to make things better overall. Process improvement is important, where appropriate, to incorporate. Does it make sense where appropriate to add: AI capabilities in some sense Create Training materials with AI Add gamification Leader Boards...etc. to Differentiate it?

Yes there is always a review of Software Implementation training, as it is an on-going process. Where the feedback comes in for the trainer, is perhaps how someone might need more training. Since we all understand things differently, a trainer might need to change up their way of training on a topic or platform to help different trainees understand that training in the best way possible for them. On the other hand, for a traineed/someone that's trained, when we train on items we will use more regularly, we become better at it. For those not used often, we might forget and need to go back and remind ourselves every so often. Getting that feedback during and post training is what's important. Then the follow-up is what gets results!

There are so many training tools on the market currently, and you will find that many of these might have the training tracking tools right inside of these "Learning Management Software" (LMS) tools themselves. Some are already listed here, and others might have these tracking surveys or capabilities too, inside of them include. Others include: HealthStream - Specific to Healthcare mostly Teachable Thinkfic LearnWorld Podia Kajabi LearnDash For Video: Let's not forget a popular mode of learning and platforms housing these YouTube Venmo and others Afew more for report feedback I would add are: Jotform

Healthcare Projects are known to have several stakeholders from different angles. Several Projects tend to have come from a new guideline, rule or changes in operations especially with the Federal Govt. Stakeholders, therefore, tend to/or could be any of these: 1) Patients/Residents: First and foremost 2) Policy Makers: Like the Federal government: CMS - Centers for Medicare & Medicaid Services 3) Providers: Clinicians, Hospitals, Other Health Services Facilities and the Employees within these Organizations 4) Payors: Insurance companies 5) Pharma Co 6) Medical Manufacturers: Device making + others 7) Biotech 8) Research and the like 9) And other supporting sectors Therefore, when determining who to interface with, determine accordingly

Training evaluation for me has mostly be low key or low level = straight up types of evaluations for the most part: 1) How many people need to take a particular training -But how many showed up? 2) For those that were trained, are we seeing tickets in or requests for additional training? - If so how many 3) A post-training survey - immediately for an idea of how teams are finding use of the new software 4) What levels of difficulty are we seeing? - Is additional over-the-shoulder type training needed? 5) Is there a need for office hours - post launch? If yes: - If there is a need, how many of the total people trained so far? - What is feedback? If no: - Why? - How can we evaluate right and proper use of the software by users? 6)KPI numbers?

The questions above are good considerations but come later in the process. The most important items to consider from the start should be what was communicated at the Project start: in the Project Charter statement. Even though there are others, start from: a) The Project objective, b) Expected outcomes, c) Resources, and Stakeholders, d) What a successful deliverable looks like and what it will do for the organization, and e) any known potential risks or issues. Additionally, the end-users need to be involved with their feedback on their experience and use of the software. Then the above questions can be answered and communicated to the Project team. What is important is to show that the audit objective isn't punitive, but better for all.