Mattermost Handbook
Need help?How to spend company moneyHow to update the HandbookRelease overview
0.2.1
0.2.1
  • Mattermost Handbook
  • Company
    • About Mattermost
      • List of terms
      • Business model
      • Mindsets
    • "How to" guides for staff
      • How to set up a 1-1 channel
      • How to update the handbook
      • How to manage Handbook notifications
      • How to change mobile device
        • How to handle a lost mobile device
      • How to do a mini-retrospective
      • How to autolink keywords in Mattermost
  • Operations
    • Company operations
      • Areas of Responsibility
      • Mattermost Leadership Team (MLT)
        • MLT cadence
      • Company measures
        • Metrics definitions
        • FY23 goals board
        • MLT metrics
      • Company cadence
      • Company policies
        • Community response policy
        • Security policy
      • Company processes
        • Issue/solution process
        • Company agreements
        • Publishing
          • Public web properties
          • Publishing guidelines
            • Brand and visual design guidelines
            • Voice, tone, and writing style guidelines
              • Contribute to documentation
            • Confidentiality guidelines
          • Post-publication quality control process
      • Handbook processes and policies
        • Handbook onboarding
      • Fiscal year planning
    • Research and Development
      • Organization
        • Tech Writing
        • Data engineering
        • Delivery
        • Cloud Platform
        • Site Reliability Engineering
        • GRC
        • Product Security
        • Security Operations
      • Processes
        • Feature Labels
      • Product
        • Product planning
          • Product philosophy and principles
          • Prioritization process
          • Release planning process
          • Roadmap views
          • Release plan
          • Launch plan
          • Feature requests
        • Development process
          • Mobile feature guidelines
          • Deprecation policy
          • Mattermost software requirements process
          • Jira ticket lifecycle
          • Creating new Jira bug tickets
            • Priority levels for tickets
            • Jira fix versions
        • Release process
          • Release overview
          • Feature release process
          • Dot release process
          • Security release process
          • Mobile app release process
          • Desktop app release process
          • Release tips
          • Release scorecard definitions
        • How-to guides for Product
          • How to use productboard
          • How to record a roadmap video
          • How to update integrations directory
          • How to write a feature release announcement
        • Product Management team handbook
          • Product Management Areas of Ownership
          • Product Manager onboarding
          • Product Manager levels
          • Professional development
        • Product Design team handbook
          • Product Design levels
        • Technical Writing team handbook
          • Work with us
          • User interface text guidelines
          • Documentation style guide
          • Our terminology
          • Guidelines for PMs and developers
          • Guidelines for community contributions
          • Technical Writer levels
          • Docathon 2021
            • Getting started with contributing
        • Growth
          • A/B testing methodology
          • PQL definition
        • Analytics
          • Product Analyst Engineer levels
          • Looker
            • Dashboards
            • Explores
          • Telemetry
        • Developer relations
        • Product team hangouts
      • Engineering
        • Infrastructure engineering
          • Cloud infrastructure cost KPIs
          • Cloud data export process
          • Cloud churn process
          • Reliability Manifesto
          • Production Readiness Review
          • Infrastructure Library
        • Integrations team processes
        • Plugin release process
        • Data Engineering
        • Sustained Engineering
          • On call
        • How to go to a conference
        • Public speaking
        • Core contributor expanded access policy
      • Quality Assurance
        • QA workflow
        • QA testing tips and tools
        • Rainforest process
    • Messaging and Math
      • How-to guides for M&M
        • How to create release announcements
        • How to create screenshots and GIFs
        • How to write Mattermost case studies
        • How to write guest blog posts for Mattermost apps and services
        • How to write Mattermost recipes
        • How to compose tweets
        • How to create a split test for web page
        • How to run meetups
        • How to run executive dinners
      • Checklists for M&M
        • Blog post checklist
        • Bio checklist
      • Mattermost websites
      • Demand generation reporting
      • M&M Asana guidelines
      • Content marketing
        • How to use the editorial calendar
        • Content development and distribution
        • Video content guidelines
        • How to contribute content
    • Sales
      • Deal Desk
      • Partner programs
      • Lead management
    • Deployment Engineering
      • Overview
      • Workflows
      • Frequently Asked Questions
      • Playbook for MME Sev 1 Outages
      • Status Update Template
    • Program Management
    • Customer Success
      • Customer Support
    • Legal
      • Contracts
      • Ironclad Basics
        • Company-Wide Workflows
        • Sales Contracts and Workflows
        • Signing a Contract and Contract Repository
    • Finance
      • Budget
      • How to use Airbase
        • Access Airbase
        • Navigate Airbase
        • How to submit a purchase request
        • How to submit a reimbursement request
        • How to review a reimbursement request
        • Vendor portal guide
        • Frequently asked questions
      • Onboarding
        • Vendor onboarding
        • ROW staff onboarding
      • Staff member expenses
        • How to spend company money
        • How to spend company money: Internships
        • Corporate credit card policy
        • How to access Airbase
        • Gifting policy
        • How to book airfare and travel
        • How to reimburse the company
        • How to convert currencies
        • How to get paid
      • Arrange a Bounty Program
      • Naming files and agreements
      • Risk management
        • Mattermost U.S. consulting agreements
      • Operations playbook
    • Security
      • Policies
      • Privacy
        • Data deletion requests
        • Data subject access requests
      • Product Security
        • Product Vulnerability Process
        • Working on security-sensitive pull requests
        • Secure Software Development guide
      • Security Operations
        • User guides
    • Workplace
      • PeopleOps
        • HR cadences
        • HR systems
        • HR Processes
        • Working at Mattermost
          • Onboarding
            • Things everyone must know
            • Staff onboarding
            • Engineer onboarding timeline and expectations
            • Manager onboarding
            • Frequently asked questions
          • Learning and development
          • Mattermost communication best practices
          • Paid time off
            • Out of office email example
          • Travel
            • Business travel insurance
          • Leaves of absence
            • Pregnancy leave
            • Baby bonding parental leave
            • Jury duty
          • Workplace program
          • Relocation
          • Total rewards
        • Performance reviews
          • Formal review process
          • New staff performance review
          • Informal review process
        • Transfers and promotions
        • Offboarding instructions for managers
        • People compliance
      • People policies
      • Groups
        • Staff Resource Groups
      • Approvals and iteration
      • IT
        • IT helpdesk
        • Hardware and software purchases
        • Hardware buy back policy
        • Software systems
  • Contributors
    • Contributors
      • Equity, diversity, and inclusion
      • How to contribute to Mattermost
        • Community Content program
        • Documentation contributions
        • Help Wanted tickets
        • Localization
        • Contribution events
      • Mattermost community
      • Contributor kindness
      • Community systems
      • Guidelines and playbooks
        • Social engagement guidelines
        • Contribution guidelines and code of conduct
        • Mattermost Community playbook
        • How to run a Hackathon
        • Hacktoberfest event organizer guide for Mattermost
    • MatterCon
      • Staff information privacy management
      • Mattermost events code of conduct
      • MatterCon2021
    • Join us
      • Ice-breakers
      • Help Wanted tickets
      • Localization
      • Mattermost GitHub sponsorship
      • Things candidates should know
      • Staff recruiting
      • Recruiting cadences
        • Product Manager hiring process
      • Exec recruiting
        • EA logistics
  • Help and support
    • Contact us
Powered by GitBook
On this page
  • Instructions for managers
  • Instructions for departing team members
  • Communicating departures
  • Plan for the transition

Was this helpful?

Edit on Git
Export as PDF
  1. Operations
  2. Workplace
  3. PeopleOps

Offboarding instructions for managers

PreviousTransfers and promotionsNextPeople compliance

Last updated 5 months ago

Was this helpful?

Instructions for managers

  1. Forward staff member's resignation letter/email to MLT member and HR hr@mattermost.com. The resignation letter/email will be stored in Rippling.

    Note: A resignation letter/email is required from departing staff. In most cases and depending upon the statutory requirements in the staff member’s country/region, a minimum of two weeks' notice is required for voluntary departures.

  2. Submit a which is used to indicate:

    • Systems that need to be deprovisioned.

    • Confirm whether emails need to be forwarded to a manager/selected team member for a period following staff member’s departure.

    • Confirm if there are any company-owned files in Google Drive that need to be transferred to you.

  3. If the departing team member is a for any vendors, systems, or contractors, communicate changes to Finance regarding:

    • Which vendors need to be transitioned (billing approvals, main point of contact).

    • Status confirmation on open procurement requests and transition procurement DRI via procurement@mattermost.com. Include: most recent email exchange and new vendor DRI.

    • Transfer ownership of any software accounts to Finance or a different team DRI. Notify of the change.

  4. Confirm with HR. Managers may also share:

    • Staff member’s termination details, including: date, final vacation balance ().

    • If needed, provide context on what led to the staff member’s resignation.

    • Confirm who will be taking over staff member’s responsibilities in the interim.

  5. Termination Retrospective with HR or Team MLT. This is not a formal , but is an opportunity to understand how to improve as a function, team, and company. HR may initiate this during Step 3, and will also request Manager feedback on:

  • Confirm rehire eligibility (if resignation was regrettable, not regrettable).

  1. Update the Handbook: If applicable, update your team list and any content that may include outdated contact information.

  2. Review and approve any outstanding expense reports.

Instructions for departing team members

  1. Forward your resignation letter/email to MLT member and HR hr@mattermost.com. The resignation letter/email will be stored in Rippling.

    Note: A resignation letter/email is required from departing staff. In most cases and depending upon the statutory requirements in the staff member’s country/region, a minimum of two weeks' notice is required for voluntary departures.

    • Exit Survey: All departing staff will receive an Exit Survey feedback request through Lattice. The survey link will be sent via email after the termination date is recorded in Rippling.

    • Exit interview with HR: Staff who leave on a voluntary basis will be invited to share feedback on their Mattermost experience in an exit interview with HR. The results of the exit interview will be shared with the departing team member’s manager and MLT. You may keep all or parts of your feedback confidential - as long as it does not involve matters that legally require additional action by the HR team. While exit interviews are not mandatory, we greatly appreciate your feedback about what is going well and what can be improved to continue making Mattermost a great place to work.

  2. Note: You do not need to, and you will not be asked to, return home office equipment, such as: desk, chair, laptop stand, etc.

  3. Sign the Role Completion Form. All departing staff will receive a Role Completion Form via DocuSign.

Communicating departures

Work with the departing staff member on the messaging around their departure. Confirm timeline of messaging and request that the staff member refrain from sharing info ahead of the planned timeline.

Communicate the agreed-upon messaging around the departure with the relevant team, department, and any other appropriate groups as soon as possible. This is important to reinforce asynchronous communication. Silence and/or lack of communication can lead to confusion, misalignment, conjecture, gossip, and insecurity. Include the departing staff member in the announcement if they are comfortable participating in the discussion.

Plan for the transition

Managers should ensure that a knowledge transfer plan is in place with the departing staff member. This may include:

  • Overview of current projects and stakeholders in those projects.

  • Overview of priority and recurring projects/tasks.

  • Overview of files and systems used regularly. Request transfer of files.

  • What files does their successor need access to?

  • Regular Mattermost contacts (and contacts outside the organization if applicable) that need to be informed of the transition.

For issues related to performance development and performance management, reach out to HR.

Confirm whether a backfill is required. If yes, follow instructions to .

Thank the departing staff member for their contributions and wish them the best for the future. Every person that joins Mattermost is part of the team and welcome to join our and stay in touch in whatever capacity feels most comfortable.

HR will reach out to the departing staff member to communicate last day instructions and details and to schedule an .

Work with your Manager to develop a transition plan, , and . We encourage team members to and encourage departing team members to say goodbye to peers, or optionally post in the . We just ask to align with your Manager on timeline of messaging so that direct teammates or working groups can be informed with an adequate plan ahead of departure.

Share feedback (optional). Input is highly encouraged and helps the People team understand as they relate to your experience at Mattermost and helps identify opportunities to improve.

Equipment. Staff members have the option to buy back their existing hardware when they are offboarding. Refer to the for more details. If staff members opt not to keep or purchase their existing hardware, they will need to return the equipment to Mattermost.

Stay in touch. Thank you for your time at Mattermost. Every person that joins Mattermost is part of the team and welcome to join our and stay in touch in whatever capacity feels most comfortable.

To avoid “@ all” departure emails/Mattermost messages, invite the departing staff member to draft a message to be shared in the . This message should be reviewed by the departing staff member's manager and HR.

General IT offboarding ticket
CAO
Systems channel
Communication Plan
if located in Canada, UK, or Germany
retrospective
open a new role
Community
exit interview
Communication Plan
Communication Timeline
make meaningful connections
Stand-up Channel
likes and wishes
Hardware Buy Back Policy
Community
Stand-Up Channel