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
  • Why do we need a policy?
  • Escalation process
  • Sensitive topics
  • Non-sensitive topics
  • Response writing tips
  • Roles

Was this helpful?

Edit on Git
Export as PDF
  1. Operations
  2. Company operations
  3. Company policies

Community response policy

PreviousCompany policiesNextSecurity policy

Last updated 1 year ago

Was this helpful?

This page outlines the process for escalating sensitive topics within Mattermost.

Why do we need a policy?

There are several sensitive topics raised by the community that we want to address appropriately and consistently at all times.

However, currently the struggles we have as a team is the unclarity on where Mattermost stands on each of the sensitive topics listed below. This unclarity often results in inconsistent responses that lead to confusion for our users, or ingenuine responses that breaks the trust from our community. We want to stop both of these from happening.

This policy is put in place to compel us as a team to have a clear official point of view for each of the listed topics below, with standard responses that can be used by a broader team. Until a clear point of view is reached, a person or a group of people are assigned as the approved responders to avoid unnecessary confusion and broken trust with our users and our community.

Therefore, if you see a question on a sensitive topic, the ask is to follow the escalation process below, and escalate sensitive topics to the approved responders until an official point of view is clearly documented. Once documented, this process will be revisited.

This policy is intended to be an iterative process, and feedback is encouraged and welcome. If there are any questions about this policy, please reach out in the in Mattermost, or message @jason.blais directly.

Escalation process

Sensitive topics listed below are escalated to a in the Private Staff team, which includes all members of the Mattermost Leadership Team (MLT) plus any approved responders. This channel is public, so anyone in the company can escalate an issue.

When an issue relating to a sensitive topic is raised (for example, on GitHub issues, Twitter, or elsewhere), it should be posted in the Community Escalations channel with an @-mention to the list of approved responders related to that particular issue.

Raising an issue is the responsibility of whoever is managing community responses in a given forum. However, it is also open for anyone at the company to escalate an issue that they see. It is then the responsibility of the approved responders to review the issue and choose an owner for responding (if a response is appropriate). By default, ownership is delegated to the first person on the list of approved responders.

Sensitive topics

While anyone can escalate a sensitive topic, only approved responders listed below can engage. If you’d like to be an approved responder for one or more of the topics, we welcome the help! Reach out to @jason.blais on community.mattermost.com, and you will be added to the next training session.

  1. Non-regulatory Privacy/Telemetry where opinions are at play more than legal or regulatory issues:

    • Approved Responders: Dr. Program Management, Lead PM, CTO, CEO

    • Loop in: CEO, CRO

    • Template Response: To be added

  2. Product-related Regulations/GDPR, and other legal issues:

    • Approved Responders: Head of Security, VP Legal, VP Product, CRO, CEO

    • Loop in: VP Legal, Lead PM, CFO

    • Template Response: To be added

  3. Licensing, including open source and commercial license inquiries:

    • Approved Responders: Dr. Program Management, CRO, CEO

    • Template Response: To be added

  4. Packaging, including requests for making an Enterprise feature free:

    • Approved Responders: Lead PM, VP Product, CTO

    • Loop in: CEO, CRO

    • Template Response: To be added

  5. Workplace policies, including hiring locations:

    • Approved Responders: VP HR, VP Legal

    • Template Response: To be added

  6. Security vulnerabilities

    • Approved Responders: Head of Security, Security PM, CTO

    • Loop in: CEO, VP Product, CFO

    • Template Response: To be added

  7. Illicit use

    • Approved Responders: VP Legal, CFO

    • Loop in: VP Legal, CEO

    • Template Response: To be added

  8. Marketing-related Regulations/GDPR, and other legal issues:

    • Approved Responders: VP Legal, CFO, CEO

    • Loop in: VP Legal, CEO

    • Template Response: To be added

  9. Governmental data request, e.g. US government requesting user/customer data under US jurisdiction:

    • Approved Responders: VP Legal, CEO

    • Loop in: VP Legal

    • Template Response: To be added

Non-sensitive topics

Non-sensitive topics include feature requests, troubleshooting questions, bug reports, and other user feedback.

Response writing tips

  • Don't make false promises or assumptions

    • If you are unsure of the answer, ask someone for help. Do not reply with an assumption or incomplete understanding.

    • Don’t say "we’ll work on feature X" that sets expectations we cannot meet (e.g. after presenting to core team it turns out you can’t implement the feature).

  • Choose positivity over negativity

    • Avoid excuses like “we’re busy”, or “our team is small” and turn a missing feature into an invitation to share a feature idea to be upvoted.

  • Do your best to link documentation as answers

    • Allow answers to be easily updated dynamically, as documentation is updated.

    • Turn questions that are not answered in docs, but should be, into tickets to create that documentation (and include ticket link in your response).

  • Keep community end user information secure

    • If you come across a post that includes the person's IP address, domain name, or other information you think should not be disclosed publicly, edit the post to remove this information. Then click the hide revision button so that your edits won't be visible to others on the forum.

  • Be thankful

    • Communities really respond well to being praised and thanked for their work.

  • Do not focus on opinions

    • Turn product discussions into conversations of specific audiences and use cases that each product edition serves.

Roles

Below is the list of members mapped to each role mentioned as an approved responder:

  • CEO: Ian Tien

  • CTO: Corey Hulen

  • CFO: Kendra Neidziejko

  • VP Product: Chen-i Lim

  • VP HR: Natalie Jew

  • VP Legal: Nirosha Ruwan

  • Lead PM: Katie Wiersgalla

  • Head of Security: Daniel Schalla

  • Dr. Program Management: Jason Blais

  • Security PM: Katie Wiersgalla

Anyone in the company is welcome and encouraged to respond, regardless of the medium. If it is your first time responding to the community, please read for help on various inquiries.

Try to understand each person's and shift the conversation away from opinions.

For more guidelines on Mattermost forums and the public GitHub repositories, see the .

Community Escalations channel
Community Escalations channel
principles, tips, and sample responses
emotions, assumptions and priorities
Mattermost Community Playbook