You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A topic for future brainstorming - if someone is serving in a role that supports many departments (a LATIS DC for example) and they leave that role and are replaced, what would an interface for swapping them across all those units look like?
My initial take is that this might be a good-in-principle, bad-in-reality kind of thing, especially considering the peak-related changes in the pipeline. But it could be doable with the right interface? There's <1 of these a year, so maybe just having a process for us to do in the DB is enough?
Things to consider
There's almost never a direct handover from one employee to another
Some departments might remove an employee from their group after that person leaves, and before the new person is hired. Then a bulk swap would potentially miss that person? Would we need a rollback window?
With these jobs (HR, Fiscal, Payroll, LATIS, etc) there's rarely a 1:1 map from new employee to old, but maybe 90% overlap and a UI for previewing changes would be enough?
The text was updated successfully, but these errors were encountered:
A topic for future brainstorming - if someone is serving in a role that supports many departments (a LATIS DC for example) and they leave that role and are replaced, what would an interface for swapping them across all those units look like?
My initial take is that this might be a good-in-principle, bad-in-reality kind of thing, especially considering the peak-related changes in the pipeline. But it could be doable with the right interface? There's <1 of these a year, so maybe just having a process for us to do in the DB is enough?
Things to consider
The text was updated successfully, but these errors were encountered: