We fixed the broken engine (Incident), and we found the root cause (Problem). Now, we need to make improvements so we can fly faster.
The Scenario:
Santa wants to install a new "Super-Speed" thruster on the sleigh to cut delivery times in half. But if he installs it wrong on December 23rd, the sleigh might explode over Chicago. He needs a plan, a test run, and a backup strategy in case the thruster fails.
The HR Reality:
In HR and IT, "Change Management" is risky business.
Example: You are switching from Health Insurance Provider A to Provider B.
The Risk: If you mess up the data migration, your employees might go to the doctor on January 1st and get rejected. You can't just "wing it" when people's livelihoods are at stake.
The JSM Solution:
Change Management Workflows. Use JSM to track organizational changes just like IT tracks software updates.
Standard Change: Pre-approved, low risk (e.g., updating a typo in the handbook). fast-track it!
Normal Change: High risk (e.g., Changing 401k providers). This requires review by the CAB (Change Advisory Board) - in this case, your HR Leadership Team - before execution.
π Tip of the Day:
Use the Change Calendar in JSM. Visualize when these big changes are happening. You definitely don't want to schedule a "New Benefits Rollout" on the exact same day that IT scheduled "System Maintenance." The Calendar saves you from these collisions.
βοΈ Letβs chat: Do you have a strict "No Changes on Fridays" rule, or do you live dangerously? What is the scariest "upgrade" or policy change youβve ever had to roll out?
Kate Pawlak _Appsvio_
Chief Product Officer & Co-founder
Appsvio
Wroclaw, PL
87 accepted answers
0 comments