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
  • Customer Obsession Meeting (aka "COM")
  • During meeting
  • After meeting
  • Staff enablement survey
  • CEO Listening Tours
  • GNN Updates
  • Monthly Business Review ("MBR")

Was this helpful?

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

Company cadence

This section details all of the different ways the company communicates and at what cadence

PreviousMLT metricsNextCompany policies

Last updated 1 year ago

Was this helpful?

We have a number of different ways we communicate. Use the right side bar to jump to a specific area:

  • Customer Obsession Meetings (COM)

  • Surveys

  • CEO Listening Tours

Customer Obsession Meeting (aka "COM")

This is a bi-weekly all-staff meeting focused on increasing alignment and awareness of how the company, departments, teams and individuals serve our customers.

is a key leadership principle and we emphasize its priority when we bring the company together. Colleagues who come from companies that aren't obsessed with customers have suggested we refer to this meeting as "All Hands" and not expect everything we announce - from to - to be framed in the context of serving customers. Such expectations are typical and common, and therefore we don't have "All Hands" meetings and instead have "Customer Obsession Meetings" to continually remind us that our focus on customers is atypical and uncommon.

Attendees:

  • All Mattermost Staff

  • Chair: Amy Nicol

  • Co-Chairs: Co-founders

Objectives:

  • Reach alignment on near and long term goals

  • Reinforce our obsession with making customers safer and more productive

  • Bring awareness through key company updates and news

  • Celebrate team achievements and patterns of success

Time:

  • Bi-weekly meeting on Wednesdays from 8:00am to 8:25am Palo Alto time and once per quarter at 6:00pm Palo Alto time to allow APAC team members to participate.

  1. Chair works 1-1 with presenters to prepare for them.

  2. Team members can share meeting agenda topics with Chair via direct message. Must be shared at least 24 hours prior to meeting start and be aligned with the meeting objectives above.

2 - T-8: Chair and Vice Chair meet to review agenda. Vice Chair works with approriate presenters of agenda topics to develope slides for presentation

3 - T-1: COM prep meeting held with Chair, Co-Chairs, and Vice Chair and review the following items:

  1. Meeting starts with thematic goal, including the theme statement, defining objectives, and actions the company is taking towards the goal.

  2. Introductions for each Week 2 Welcome are confirmed by PeopleOps.

    1. If new hire or manager is away, introduction is postponed to the following meeting.

    2. New team members are introduced on their second week by their manager, including name, role, what they're working on, timezone, additional info as appropriate (max 2 minutes).

    3. New hire can opt-in to introduce themselves if they choose (default is not to require public speaking).

  3. Material for each agenda item is reviewed, and contains a link for more information such as a post to a channel, documentation or a blog post.

    1. Each link shared in meeting notes should be publicly accessible to everyone in Mattermost.

  4. If computer sound is shared during the call, test it prior to the meeting and install libraries or tools as required.

During meeting

  1. (Chair & Vice Chair) Sign into their Zoom account to access recording and screenshare during the meeting.

  2. (Vice Chair) Start Zoom recording at 8:00am Palo Alto time.

  3. (Chair and Co-Chairs) Run through the agenda, which comprises one or more of the following items:

    • Introduction: One of the founders does an introduction to the meeting. Usually to align company on short and long term objectives, to reiterate larger vision for the company, or to emphasize leadership principles.

    • Good News: News or updates shared by team members.

    • Week 2 Welcomes: New team members introduced on their second week by their manager, or optionally by the new team member themselves.

    • Main Topics: Align and educate team around challenges faced by Enterprise customers and around department near-term goals. Examples include: FOSDEM event highlights and learnings; Enterprise customer's path from pilot to production; department VPMOM share; key updates, use cases or stories from customers.

      • Links to publicly shared documents or slides may be included in meeting notes.

    • Feedback: At end of meeting, conclude meeting with a reminder to share feedback via survey.

After meeting

  1. (Chair) Collect feedback from survey and add to next meeting's draft agenda for Chair and Co-Chairs to review.

Staff enablement survey

  • The enablement survey will be announced in COM one week before the survey goes live.

  • The survey link will be shared at the beginning of COM.

  • The link will be posted in the COM channel with "Thumbs Up" emoji reaction.

  • All staff are asked to complete the survey and signal completion by clicking on "Thumbs Up".

  • Ideally, the meeting will conclude after "Thumbs Up" count reaches attendee count but this is not a requirement.

  • An analysis of the results should be prepared and presented within the next 2 - 4 weeks in COM.

Links to previous staff enablement surveys:

CEO Listening Tours

Listening to feedback is vital to iteration and to continually improve everything we do.

Feedback and listening is at the core of our self-awareness leadership principle. We have 1-1s with managers, regular pulse and engagement surveys, People team outreach and conversations, and annonymous feedback available in every weekly Customer Obsession/All-Hands Meeting. CEO Listening Tours are another way we listen.

CEO Listening Tours happen over Zoom in meetings around 25-30 minutes with different groups of 5-8 staff, typically within the same department or in a related function. Managers of the team members in the group are typically not included in the meeting.

Some notes about Listening Tours:

  • It's an opportunity to hear from staff about their likes and wishes, which could be about their team, their department, the company in general, or on any topic. These could be likes and wishes off the top of your head, or maybe something you've been thinking about for a while. This simulates an open feedback session at MatterCon where we would ask people to share their thoughts and feelings.

  • The priority of the meeting is listening. During these sessions the CEO takes notes and refrains from commentary, though may ask follow-up questions. Notes are "default open" to be shared with managers, executives, and anyone in the company.

  • At the end of the session the CEO reads back what they heard. The notes are shared with the management team/s of the group.

  • It's then up to managers to decide how to process and address the feedback at the team level. The CEO can also incorporate the information at the company level.

  • In the past, participants and managers of listening tours have found the meetings productive for uncovering blindspots at the company and within departments.

If you're not able to make a particular listening meeting, please ping @amy.nicol to add you to a different slot.

How to participate in Listening Tours:

  1. Join us: Attend the scheduled meeting, or if it's not convenient, ping @amy.nicol to join a different meeting slot.

  2. Share about yourself: Please introduce yourself with the group (even if we all know each other), with your name, your role, the city and country you're in, and what time it is there.

  3. Share a like and a wish: If you'd like to share feedback, in the form of a like and a wish, please share it when you feel appropriate. Your feedback can be about anything, something recent ("Wish Zoom was more stable") or something you've been thinking about or talking about for a while ("Really like the Social Coffee channel and meeting people across the company").

  4. Confirm you've been heard: As feedback is read back, share if what you had to say has been accurately captured to be shared with our leadership team, execs, and managers.

Listening tours are just another way we gather feedback so we can iterate and improve everything we do. Thank you for helping speed us on our journey of continual improvement.

GNN Updates

A GNN Update is a concise way to share out what's "Going Well", "Not Going Well", and "Next Actions" on a specific initiative or goal.

  • Going Well: What's going well, and what would we want to amplify or repeat?

  • Not Going Well: What's moving slower than expected? What's in our way?

  • Next Actions: Based on what's going well (things we want to amplify or repeat) and Not Going Well (problems we need to solve), what are the next actions we want to take in the next 1-2 weeks? Next actions should include who is responsible for them, a due date and what the expected outcomes and imapct of the next actions.

If a GNN has been shared previously, the Business owner should share the following in their next update:

  • Outcomes of previous Next Actions: Share what happened after the last set of Next Actions were shared out, good and bad. If the Next Action wasn't completed, explain why, and then what we'll do next time to complete the action.

  • Link to previous GNN Update: Add a link back to the previous GNN update as a reference.

Monthly Business Review ("MBR")

  • Each month we review our progress against our company-level standard operating metrics.

  • The GNN Updates are prepared by business owners with input from the data owners.

  • In the MBR we align on the most important opportunities to accelerate the company, and supporting the DRI with Next Actions across the company to bring a goal back to success.

(Vice Chair) At 7:58am Palo Alto time on the day meeting is held, post a reminder in Customer Obsession Meeting channel. .

(Team) Join the Zoom link in the header of the , and open the Meeting Notes link in the header to see the agenda.

(Chair) Share meeting recording (viewable only by signed-in users and non-downloadable) and link to feedback survey. . Note: Include the hashtag #com-recording somewhere in the post.

(Chair) Post a link to the meeting recording in the header of the and in the meeting notes.

(Presenter) Any presenter that introduces a new acronym needs to include this in the .

Every 6 months we'll be asking staff to spend around 3 minutes completing a , plus identifying their organizational leader.

See here for an example
Customer Obsession Meeting channel
See an example here
Customer Obsession Meeting channel
Mattermost Acronyms Focalboard
staff enablement survey of 12 engagement questions
March 2019 staff enablement survey
September 2019 staff enablement survey
March 2020 staff enablement survey
April 2021 staff enablement survey
spending company money
recruiting new talent
Customer Obsession