/
Handbook Reviews

Handbook Reviews

The People Operations @admin-team handles editorial and legal review of Axelerant guidelines, policies, and processes within the Axelerant Handbook and Open Axelerant documentation every January.

Dates of Latest Reviews & Updatesarchived.

Admin Team DRAFT Review & Publishing Process

  • Directly Responsible Individual’s (DRI) checklist for reviewing/changing a process or guideline:

    • Demonstrate the reason for the change in the existing or new guideline process

    • Read and research relevant best practices

    • Document suggestions/concern points using the #disc- Conversation Creator to help collect feedback and invite all relevant team members/stakeholders to share their advice in the channel.

    • When the guideline change affects the broader team, all team members should be invited to the discussion and given at least two weeks to provide feedback before the draft is finalized.

    • Collate all the suggestions, and consider the ones that can be implemented within the given time/budget. Create a Draft of the proposed guideline/process.

  • Ensure the organization's values are reflected throughout the draft. The language used must be inclusive of all genders, abilities, and backgrounds, and respectful of diverse identities.

  • When a monetary impact is expected from the suggested change in guideline/benefit - get a clear go-ahead from Ankur and Puneet to ensure the sustainability of the proposal.

  • Share the draft with relevant stakeholders, including the team and leadership involved, with a clear deadline and expectations for feedback before publication.

    • Relevant stakeholders might be your direct team members and other leaders

  • The DRAFT copy of the guidelines must be shared with relevant stakeholders, providing a couple of weeks to share feedback on revisions.

  • Mention the effective date of the proposed change in the draft.

  • After the feedback deadline has passed, finalize and publish the guideline/process to Confluence.

  • Announce the update via #announcement or #general using @team-axelerant or @channel.

  • Record and share a video (Loom or Slack video) if the update includes complex changes that need additional explanation.

  • Retrospect change.