memo: fix offboarding checklist (#92)

operations/checklists/offboarding-checklist.md

@@ -4,44 +4,63 @@ tags:
   - operations
   - checklist
 title: "Checklist: Offboarding"
-date: 2020-01-01
+date: 2024-08-19
 description: The process when an employee offboard from the team.
 authors: 
   - tieubao
   - hnh
+  - innno_
 ---
 
-An off-boarding process must ensure three things
-- Your employee feels good
-- The departure causes minimal disruption.
-- The termination process must be well-wrapped to make sure the company policy and procedures are all conformed.
-
-## Account removal
-Account removal should be applied for work channels, such as Basecamp or Jira. Otherwise, we welcome the employee to stay around in Discord and participate in community events. 
-
-## Device collecting
-Once the employee has finished his/her meeting with the Lead and finally have the offboarding date, the employee should wrap up his/her handover process and send back the work tools. 
-
-That includes working device, subscription account, office key or parking card.
-
-## Offboarding checklist
-### Project Offboarding
-
-- [ ]  Last day confirmation with client
-- [ ]  Project handoff done
-
-### Company Offboarding
-- [ ]  Exit talk with lead/ mentor
-- [ ]  Exit talk with HR/ Ops (Remind about Non-competitive Agreement & NDA)
-- [ ]  Return access card / equipments (laptop, phone) if have
-- [ ]  Remove email account
-- [ ]  Remove Git account
-- [ ]  Remove 1password account
-- [ ]  Remove Basecamp account
-- [ ]  Update Fortress profile
-- [ ]  Update Discord Role → Alumni + Remove Discord Access from channels
-- [ ]  Member Delete source code on their machine
-- [ ]  Last day & Final paycheck informed
-- [ ]  Update DF resource planning file
-- [ ]  Farewell message posted
-- [ ]  Update linkedin + endorse Dwarves
+## Objectives
+An off-boarding process must ensure three things:
+1. Your employee feels good.
+2. The departure causes minimal disruption.
+3. The termination process must be well-wrapped to make sure the company policy and procedures are all conformed.
+
+## Project Offboarding
+- [ ] Last day confirmation with client by email 
+- [ ] Resource replacement 
+- [ ] Project handoff completed 
+- [ ] Source code backup 
+
+## Company Offboarding
+### Exit Interviews and Final Communications
+- [ ] Exit interview with lead/manager 
+  - Gather feedback
+  - Invite to join alumni activities on discords/event
+- [ ] Exit talk with HR/Ops 
+  - Remind about important points in the Contractor Agreement
+- [ ] Last day & final paycheck informed 
+- [ ] Offboarding email - Remind on survival terms in Contractor Agreement 
+- [ ] Thank you & farewell letter to personal email 
+- [ ] Farewell message posted (Optional)
+- [ ] Update DF resource planning file
+- [ ] Update LinkedIn + endorse Dwarves  
+
+### Account and Access Management
+- [ ] Remove email account 
+- [ ] Remove Git account 
+- [ ] Remove 1password account 
+- [ ] Remove Basecamp account
+- [ ] Remove access to other work channels 
+- [ ] Remove database access
+- [ ] Update Fortress profile
+- [ ] Update Discord Role → Alumni + Remove Discord Access from work-related channels
+
+### Equipment and Resources
+- [ ] Office card / work device (laptop, phone) if applicable
+- [ ] Any other company-owned equipment
+- [ ] Remind member to delete source code from their machine
+
+## Post-Departure
+- [ ] Follow up on any outstanding items or handover tasks
+- [ ] Conduct a brief team meeting to address any gaps left by the departure
+- [ ] Update relevant documentation and contact lists
+
+### Handover Transfer
+- [ ] Conduct handover transfer sessions with team members
+- [ ] Document any unique scripts or tools created by the employee
+- [ ] Capture information about ongoing experiments or research
+
+Note: This aims for a smooth, positive offboarding that maintains good relations with the departing employee while protecting company interests. The checklist can be adapted to the specific role and company technology/processes.