Edit Shift Times - Product Launch (Kelly)
Global launch date: March 18, 9am PT
Edit Shift Times - HCF KOps feature doc
Edit Shift Times - HCF KOps Post Launch Calls tracker sheet
Product Brief: Shift Time Editor
Articles/SOP Updates for Shift Time Editor
Project Summary
In the web app, registered facility users with Shift Posting permissions can now self-serve changing the start/end times for booked shifts, so long as the worker has not clocked in yet. Web app only. Not yet available in mobile.
When logged in as the facility user:
- Find the shift on the calendar page
- Click on “Edit time” on the bottom of the shift card
- Enter the new start and end times and click “Submit.“
- This will send the proposal to the professional through chat.
- They can make further edits to the proposal by repeating (1) through (3).
- The professional will be able to accept or decline the proposal on their end of the chat.
They can track the current state of their proposal via an indicator on the shift card.
Once the professional accepts the proposal, the shift will be updated to the proposed start and end times.
Progress Updates
March 21: I only give this play by play in the spirit of working in the open bc it was another day of small things adding up that felt derailing. I really did try to block out the noise, but the noise was mostly related to the post-launch work. And if it wasn't directly related to post-launch, it was very related to our working process and didn't feel like it should be skipped or put off to later.
12:53-2:30pm ET As I was about to settle into my focus block for listening and making calls, a thread was flagged that determined a need to pivot to making content updates in as real time as possible. Then shifted to collecting answers from Zack since launch and adding to Learnings section of the Feature Doc.
2:30-3:30 Was reminded to at some point create a project tracker post in our kops ZD space. Not wanting to forget next week, I shifted to this while discussing details in thread.
3:30-4 I decided to first add in some ticket info to the tracker so that I could jump right in after content updates. As was shifting back to content updates, my reminder alerted for Chris' post about adding TOC to guides as we go along. Figuring I was about to make edits anyway, may as well watch the loom and learn how to implement this new practice.
4-4:30 I paused to shove nutrients into my dome
4:22-5:42pm Reminder alert to read Libby's doc + 2 pings of comments in the doc, so I shifted to read and action those.
6-7:44 Finally was able to get the TOC added to the guide w/ anchor links. Made adjustments to the "edit shift time after clocked in" section, and rearranged some section to be more cohesive with the guide flow.
This is now already nearly 7hrs, with the morning having spent some time cleaning up the issues tracker and cleaning up my reminder alerts, fully expecting I'd get my focus block to knock out calls.
I tried for an afternoon block thinking it would be a good median of working/available hours for calling all time zones. On Monday I'll block the morning hours instead of afternoon, and start with east coast facilities if I can help it. Will be STERN about ignoring slack for this time to get caught up.
-
Update on the current progress of Shift Time Editor:
I continue to see agents not offering the shift time editor in both situations where it should be their first option (Shift is completely in the future) and more reasonably in ambiguous situations (i.e., Maple Shifts, shifts with a past start time where they are trying to shut down an urgent shift, a brief bug preventing edits between AM/PM/NOC shift time thresholds)The calls that have highlighted the ambiguous areas for the Shift Time Editor have been brought up with product in #proj-shift-time-editor:
- Discussions for Maple shifts: Thread 1 & Thread 2
- Addressing an urgent shift with an open proposal: Thread
- Shift type edit bug: Thread
- Automatically updating the shift type when the proposal is accepted: Thread
I will update the call tracker sheet to resemble the sheets that Libby put together for A-Team and WLE, providing more room for granularity in comments and feedback. This will also help bundle together some call examples for feedback to agents who are repeat offenders and not showing progress in offering self-services as a first option and hopefully give better overall insights into why the feature is or is not being offered.
Two additional areas that have been highlighted as concerns are:0
Please sign in to leave a comment.
Comments
1 comment