Got an itch because our documentation is lacking? Wonderful, please help make it right.
To make changes to guidelines in https://axelerant.atlassian.net/wiki/spaces/AH/overview or https://axelerant.atlassian.net/wiki/spaces/OA, create a copy target page into /wiki/spaces/AH/pages/3034480778.
Rename the page with a DRAFT suffix in the page title, like Benefits DRAFT, and click Publish.
By publishing the draft after renaming the page title, you create version one that reflects the live page. Therefore, it becomes pretty easy to see what has changed since the copy. Otherwise, what’s changed is difficult to determine.
The draft version is to ensure that revisions are thought out and not perceived as rapid change.
Alternatively, edit the page in Google Docs, and then create a DRAFT for further review.
When you’re confident DRAFT pages are good enough, submit a request to People Operations for editorial and legal review plus publishing.
When it’s time to publish the revision unless it’s a new page that can be directly moved, a designated person will copy the content from the /wiki/spaces/AH/pages/3034480778 section page or Google Doc into the target page. We’ll not replace the page itself as to not break the page links.
Video https://www.loom.com/share/e659c78dd3014b18801863ba4c6b1bda
https://axelerant.atlassian.net/wiki/spaces/AH/overview edit notifications in #feed-axelerant-handbook.
Open Axelerant edit notifications in #feed-open-axelerant.
The pages below are not publicly accessible, yet shared here at a high level to let you know the things we’re attempting to clarify well. When they go live, they’ll be brought into https://axelerant.atlassian.net/wiki/spaces/OA.
The @admin-team of People Operations handles editorial and legal review of Axelerant guidelines, policies, and processes within the Axelerant Handbook and Open Axelerant documentation once a year, typically every January.
Dates of Latest Reviews & Updates.
Directly Responsible Individual’s (DRI) checklist for review/changing a process/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. Inviting all relevant team members/stakeholders to share their suggestions in channel.
When the guideline change is applicable to all, then all the team members can be invited to join the disc-conversation channel, and wait for at least 2 weeks for everyone to share inputs, before finalizing the draft
Collate all the suggestions, and consider the suggestion which can be implemented within the given time/budget in hand. Create a Draft of the proposed guideline/process.
Ensure the values of the organization are considered while drafting the guideline/processes. The verbiage used must be kind, inclusive, and respectful.
When a monetary impact is expected from the suggested change in guideline/benefit - get a clear go-ahead from Ankur or Michael plus Puneet for ensuring the sustainability of the proposal.
Share the draft with the Relevant stakeholders with clear expectations, and clear deadlines by when you choose to close/publish the final draft.
Relevant stakeholders might be your direct team members and other leaders
The DRAFT copy of the guidelines must be shared with the ops-organization channel, providing a couple of weeks to share feedback on revisions.
Mention the change effective date
Post the deadline, and publish the draft to Confluence.
Go-live, announce via #announcement or #general channel using @team-axelerant / @channel tags
Share a video recap (Loom / Slack recorded video) if there’s too complex stuff that needs a simpler explanation of the process.
Retrospect change
When live content is no longer valuable to Axelerant, prepend the title with zzz and Archive it.
When a draft page is no longer valuable to Axelerant, Delete it.
