Add offboarding checklists

[mercadon]

No description provided.

[nicksnyder]

I am worried about these offboarding checklists getting out of date and desynchronized with the onboarding checklists.

Is there anything on the offboarding checklist that doesn't map to an item in an onboarding checklist?

If not, I propose that we just maintain an onboarding checklist and the offboarding process is to execute the onboarding checklist except take the opposite action.

This would be easier if we rephrased the list items. For example: "on call rotation" not "add to oncall rotation", "recurring 1-1" not "create a recurring 1-1".

Then these list items can be copied into an issue/doc titled onboarding or offboarding and it is obvious what action to do.

[mercadon]

Is there anything on the offboarding checklist that doesn't map to an item in an onboarding checklist?

There are ~3 things that don't map to the onboarding checklist, and there are ~8 things from that onboarding list that don't map to the offboarding checklist. I hear you though– it is an extra list to keep updated and will require cross-referencing these two checklists, but I think there are enough differences that if we didn't have separate docs some items/actions would be unclear.

For now, I think it'll be valuable to have both an onboarding and offboarding checklist– if it does become too much of a burden to keep them both updated I'm happy to revisit combining them if we can make it clear what belongs to onboarding only vs onboarding+offboarding.

[sqs]

@mercadon Do you still intend to merge this PR? If not, please close it. I'll close it in a couple days if I haven't heard back (I'm just trying to clean up our PR list).