Create file neuroinclusion-in-practice.md

Why is this change being made?

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

Please add the details saying why, not just what in this section. Example: We have discussed the topic in Slack - (copy of Slack conversation). The current process is not efficient, this MR makes the description of X more clear, and helps move Y forward.

DIB is launching the NeuroInclusion in Practice training programme as part of our commitment to building a culture where everyone belongs and everyone can contribute. This 12-module programme spans three Courses (all employees, managers, and HR/senior leaders)

Current State: While the training content is being developed and will be hosted on LevelUp and our internal Loop site, team members need a central Handbook page that:

Explains what neuroinclusion means at GitLab Connects them to the training programme Points them to the Loop site for materials and resources Provides clear pathways to accommodations and support Links to relevant TMRGs and community spaces

Current State: While the training content is being developed and will be hosted on our internal Loop site, team members need a central Handbook page that:

Explains what neuroinclusion means at GitLab Connects them to the training programme Points them to the Loop site for materials and resources Provides clear pathways to accommodations and support Links to relevant TMRGs and community spaces

Why This Change: This MR adds a new Handbook page: /handbook/people-group/learning-and-development/neuroinclusion-in-practice/ (or appropriate location as determined by L&D/DIB team placement). The page serves as:

Wayfinding — Helping team members navigate to the right resources Programme overview — Explaining the learning path and audience Connection point — Linking to TMRGs, accommodations processes, and support Official documentation — Establishing neuroinclusion as part of our CREDIT values in practice

Design Decisions:

Kept the Handbook page concise and scannable (estimated 5-7 minute read) Detailed resources, templates, guides, and training materials will live on the Loop site (which can be updated without MR process) Focused on universal principles that work across GitLab's global locations Language carefully reviewed to avoid country-specific legal claims about diagnosis/accommodations while still being supportive Key principles reflect the social model of disability (barriers exist in systems, not people)

Alignment:

Supports DIB mission and CREDIT values Aligns with existing Accessibility & Accommodations Handbook pages Complements existing Neurodiversity Resources page Works alongside TMRG structure

Next Steps After Merge:

Announcement in #diversity_inclusion_and_belonging Link added to DIB main page Reference added to onboarding materials (future iteration) Loop site content population continues in parallel

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
• Assign reviewers for this MR to the correct
  • The when to get approval handbook section explains when DRI approval is required
  • The who can approve handbook section explains how to identify the DRI
  • If the MR does not require DRI approval, consider asking someone on your team, such as your manager.
  • The approver may merge the MR. If they approve but don't merge, you can merge.
• For transparency, share this MR with the audience that will be impacted.
  • Team: For changes that affect your direct team, share in your group Slack channel
  • Department: If the update affects your department, share the MR in your department Slack channel
  • Division: If the update affects your division, share the MR in your division Slack channel
  • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
    • For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter

Commits

• Update file neuroinclusion-in-practice.md

---