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 is this team important now?
  • How is this team measured?
  • How will work be allocated to this team?
  • Who owns long-term maintenance of solutions built by this team?
  • How does this role differ from TAMs (Technical Account Managers)?
  • Why does this role not report to Customer Success, like TAMs?
  • How does this role differ from Customer Reliability Engineers?
  • Why does this role not report to Customer Support, if they work on escalations?
  • Will this team be on call or part of SET rotation?
  • What is out of scope for Deployment Engineering?

Was this helpful?

Edit on Git
Export as PDF
  1. Operations
  2. Deployment Engineering

Frequently Asked Questions

PreviousWorkflowsNextPlaybook for MME Sev 1 Outages

Last updated 1 year ago

Was this helpful?

Why is this team important now?

Retention is the #1 priority, and underdeployment is the leading cause for contraction.

Deployment Engineering helps customer-facing teams (TAMs, CREs, CS) by leveraging engineering talent to accelerate customer success with deeper platform knowledge given their background in software design engineering, thus accelerating seat deploymets, thus reducing contraction, thus increasing renewal rates.

How is this team measured?

Primary measurement is Customer Seats Deployed - % of customers with >$50K ARR with at least 80% of seats deployed.

How will work be allocated to this team?

Deployment Engineering will work closely with other post-sales teams (CREs, customer success, TAMs) to determine the highest impact technical customer priorities for the team to work on.

For instance, when choosing between three options, work will always be prioritized based on the impact level, with effort taken into consideration (e.g. a medium impact low effort technical priority may supersede a high impact but very high effort priority).

Moreover, for any one-off customer solutions, a clear SOW or other such document will be created to set clear expectations with the customer of what is delivered, by whom, and in what timeframe, , signed off by the customer. This process is similar to what would be done with a partner. The sign-off is not necessarily a formal contractual agreement, but at minimum a verbal agreement to ensure expectations are set clearly before work begins.

Who owns long-term maintenance of solutions built by this team?

Most solutions should not require long-term maintenance, as they will be standalone scripts, plugins or other code that is not dependent on Mattermost server versions.

For solutions that require maintenance, we will discuss ownership between Deployment Engineering, TAMs, R&D and a vendor on a case-by-case basis.

How does this role differ from TAMs (Technical Account Managers)?

TAMs are responsible for ongoing relationship management with technical champions, and own pre-defined customer onboarding in standard deployment environments (ie. follow our gold standard deployments).

Thus, Deployment Engineering acts as an extension of R&D supporting post-sales and customer success on the most complex, technical problems, with expertise on how to run and deploy Mattermost and the platform as a whole.

Why does this role not report to Customer Success, like TAMs?

TAMs are responsible for ongoing relationship management, and are evaluated against renewal rates.

Deployment Engineering engages with customers on a short-term basis, in a technical capacity. Their evaluation is not based on renewal rates, and hence do not directly report to the revenue organization (Sales & Customer Success).

How does this role differ from Customer Reliability Engineers?

Customer Reliability Engineers provide first-line of support & troubleshooting, and may fix bugs & security issues, while Deployment Engineering is a point of contact for critical deployment escalations only for customers over $50k ARR (e.g. performance degradation).

Why does this role not report to Customer Support, if they work on escalations?

Support Engineers are evaluated against CSAT scores and SLA coverage. Deployment Engineering is evaluated against Customer Seats Deployed.

Will this team be on call or part of SET rotation?

No.

What is out of scope for Deployment Engineering?

The following is out of scope for Deployment Engineering

  • Regular customer support (tier 1, 2, 3, 4 support) owned by Customer Support as per our standard support terms: https://mattermost.com/support-terms/

  • Customer account management including expansion, renewals, or license management, owned by CSMs and TAMs.

  • Predefined onboarding journey including sales hand-off, standard deployments with standard data migrations, testing, training and end-user rollout, owned by TAMs unless specifically escalated to Deployment Engineering.

  • Identification of key integration opportunities for the Mattermost team to develop, owned by CSMs and TAMs

  • Development or maintenance of in-product features, integrations or other such product functionality, owned by R&D Engineering

    • Note: In-product feature development may be completed by Deployment Engineering as an exception, e.g. building a custom solution that we decide to integrate into the product. Such a development requires prior approval from Product Engineering, to ensure they can support the feature once developed for the customer.

On the other hand, Deployment Engineering supports non-standard deployments with complex technical problems, as well as work closely with customers on temporary one-off custom solutions & integrations based on .

outlined as a services request by the CSMs/TAMs
requirements outlined by the CSMs/TAMs