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
  • Level 1: Product Designer I
  • Level 2: Product Designer I
  • Level 3: Product Designer II
  • Level 4: Product Designer II
  • Level 5: Senior Product Designer
  • Level 6: Senior Product Designer
  • Level 7: Staff Product Designer
  • Level 8: Principal Product Designer
  • Level 9: Distinguished Product Designer

Was this helpful?

Edit on Git
Export as PDF
  1. Operations
  2. Research and Development
  3. Product
  4. Product Design team handbook

Product Design levels

These levels serve to help Product Designers assess their opportunities for career growth in the Product Design function. The levels below follow a growth track in the art and craft of Product Design and not in a person management track.

Level 1: Product Designer I

Leadership Principle
Competencies
Level Expectations

Ownership

Scope: "What do I work on?" Scope is the domain over which you are expected to show ownership.

Executes on defined projects or tasks in their area of focus, directed by senior leaders.

High-Impact

Supervision: "How much do I rely on my Design?" Community: "How do others work with me?" The need to receive supervision is inversely related to the instinct to choose what is high-impact.

Receives detailed instruction on most projects or tasks. Asks questions, and knows when to stop and ask for help.

Earn Trust

Influence: "Who do I work with?" As more people and parts of the organization earn your trust, your influence grows.

Works effectively in teams to align priorities and manage execution on defined projects or tasks. Works directly under Senior-level designers.

Customer Obsession

Customer Impact: "How do I bring value?" Community spans both open-source and enterprise, but ultimately manifests in the same obsession for enabling customers to be successful.

Considers the customer's perspective when making decisions. Knows when to ask clarifying questions.

Self-Awareness

Interaction: "Who relies on me?" Iteration: "How do I improve myself and others?" Self-awareness yields an ability to seamlessly fit into any conversation or effort, interacting with a group to work towards the best possible outcome and always iterating towards the best possible outcome.

Regularly participates in team discussions for ongoing feature work. May lead discussions on smaller topics.

Level 2: Product Designer I

Leadership Principle
Competencies
Level Expectations

Ownership

Scope: "What do I work on?" Scope is the domain over which you are expected to show ownership.

Executes on defined projects or tasks in their area of focus, with limited direction.

High-Impact

Supervision: "How much do I rely on my Design?" Community: "How do others work with me?" The need to receive supervision is inversely related to the instinct to choose what is high-impact.

Receives general instruction on day-to-day work, and detailed instruction on new projects or tasks. Engages, and enables senior designers to deliver high quality work.

Earn Trust

Influence: "Who do I work with?" As more people and parts of the organization earn your trust, your influence grows.

Works effectively in teams to align priorities and manage execution on defined projects or tasks. Works directly under Senior-level designers.

Customer Obsession

Customer Impact: "How do I bring value?" Community spans both open-source and enterprise, but ultimately manifests in the same obsession for enabling customers to be successful.

nderstands and applies basic level best practices for customer impact within their daily work. Will ask for input on more complicated topics.

Self-Awareness

Interaction: "Who relies on me?" Iteration: "How do I improve myself and others?" Self-awareness yields an ability to seamlessly fit into any conversation or effort, interacting with a group to work towards the best possible outcome and always iterating towards the best possible outcome.

Regularly participates in team discussions for ongoing feature work. May lead discussions on smaller topics.

Level 3: Product Designer II

Leadership Principle
Competencies
Level Expectations

Ownership

Scope: "What do I work on?" Scope is the domain over which you are expected to show ownership.

Influences and executes defined projects or tasks and features across the product.

High-Impact

Supervision: "How much do I rely on my Design?" Community: "How do others work with me?" The need to receive supervision is inversely related to the instinct to choose what is high-impact.

Receives general instruction on new projects or tasks. Enables senior designers to deliver high quality work.

Earn Trust

Influence: "Who do I work with?" As more people and parts of the organization earn your trust, your influence grows.

Works directly with PM and ENG, providing input on the feature work to be done by the team, with product and engineering requirements.

Customer Obsession

Customer Impact: "How do I bring value?" Community spans both open-source and enterprise, but ultimately manifests in the same obsession for enabling customers to be successful.

Can navigate moderately complex decisions and thought process about how features and implemetations bring customer value, and can make decisions in these areas independently. Starts to understand and contribute to cross-feature and/or cross-team implications of customer impact.

Self-Awareness

Interaction: "Who relies on me?" Iteration: "How do I improve myself and others?" Self-awareness yields an ability to seamlessly fit into any conversation or effort, interacting with a group to work towards the best possible outcome and always iterating towards the best possible outcome.

Drops fluidly into feature team projects, ramps quickly and drives features to successful outcomes. Drives discussions on small and mid-size topics. Participates actively in discussions and efforts that cross teams. Actively seeks feedback and growth opportunities.

Level 4: Product Designer II

Leadership Principle
Competencies
Level Expectations

Ownership

Scope: "What do I work on?" Scope is the domain over which you are expected to show ownership.

Executes and delivers high impact features and design changes across the product.

High-Impact

Supervision: "How much do I rely on my Design?" Community: "How do others work with me?" The need to receive supervision is inversely related to the instinct to choose what is high-impact.

Receives minimal instruction. Engages and enables senior designers to deliver high quality work. Enages in the open source community to contribute design efforts in building new features and contributions to Compass, the Mattermost Design System.

Earn Trust

Influence: "Who do I work with?" As more people and parts of the organization earn your trust, your influence grows.

Works directly with PM and ENG, helping define the feature work to be done by the team, with product and engineering requirements.

Customer Obsession

Customer Impact: "How do I bring value?" Community spans both open-source and enterprise, but ultimately manifests in the same obsession for enabling customers to be successful.

Can navigate moderately complex decisions and thought process about how features and implemetations bring customer value, and can make decisions in these areas independently. Starts to understand and contribute to cross-feature and/or cross-team implications of customer impact.

Self-Awareness

Interaction: "Who relies on me?" Iteration: "How do I improve myself and others?" Self-awareness yields an ability to seamlessly fit into any conversation or effort, interacting with a group to work towards the best possible outcome and always iterating towards the best possible outcome.

Drops fluidly into feature team projects, ramps quickly and drives features to successful outcomes. Drives discussions on small and mid-size topics. Participates actively in discussions and efforts that cross teams. Actively seeks feedback and growth opportunities.

Level 5: Senior Product Designer

Leadership Principle
Competencies
Level Expectations

Ownership

Scope: "What do I work on?" Scope is the domain over which you are expected to show ownership.

Influences product vision for high impact features and design changes across the product.

High-Impact

Supervision: "How much do I rely on my Design?" Community: "How do others work with me?" The need to receive supervision is inversely related to the instinct to choose what is high-impact.

Defines new feature assignments for themselves, usually without requiring help. Enages and inspires other designers to engage in the open source community to contribute design efforts in building new features and contributions to Compass, the Mattermost Design System.

Earn Trust

Influence: "Who do I work with?" As more people and parts of the organization earn your trust, your influence grows.

Recognized by colleagues and community as a design authority, passively influencing discussions and behavior, and working in sync with PM, ENG, and customer teams. Frequently sought out by product and engineering leads for opinion on both product and design directions.

Customer Obsession

Customer Impact: "How do I bring value?" Community spans both open-source and enterprise, but ultimately manifests in the same obsession for enabling customers to be successful.

Can indepently make decisions affecting customer value/impact for complex topics within a product/feature-set. Leads cross-product, cross-feature, and cross-team discussions related to customer value/impact, and can bring the stakeholders to a decision point.

Self-Awareness

Interaction: "Who relies on me?" Iteration: "How do I improve myself and others?" Self-awareness yields an ability to seamlessly fit into any conversation or effort, interacting with a group to work towards the best possible outcome and always iterating towards the best possible outcome.

Frequently called upon to comment on product, customer and community discussions. Is very comfortable in customer and community discussions, aligns efforts, and develops superior solutions through discussion and analysis. Participates deeply in cross-team efforts. Begins to lead discussions on topics that reach outside of design.

Level 6: Senior Product Designer

Leadership Principle
Competencies
Level Expectations

Ownership

Scope: "What do I work on?" Scope is the domain over which you are expected to show ownership.

Influences product vision for high impact features and design changes across the product.

High-Impact

Supervision: "How much do I rely on my Design?" Community: "How do others work with me?" The need to receive supervision is inversely related to the instinct to choose what is high-impact.

Defines new feature assignments for other members of the team, usually without requiring help. Leads the coordination and management of campaigns when creating new features and products.

Earn Trust

Influence: "Who do I work with?" As more people and parts of the organization earn your trust, your influence grows.

Highly respected by colleagues and community as a design authority, actively influencing discussions and behavior with input and suggestions, and working in sync with PM, ENG, and customer teams. Engages with people in the broader design community (outside of Mattermost) to identify and and implement best practices within Mattermost.

Customer Obsession

Customer Impact: "How do I bring value?" Community spans both open-source and enterprise, but ultimately manifests in the same obsession for enabling customers to be successful.

Can indepently make decisions affecting customer value/impact for complex topics within a product/feature-set. Leads cross-product, cross-feature, and cross-team discussions related to customer value/impact, and can bring the stakeholders to a decision point.

Self-Awareness

Interaction: "Who relies on me?" Iteration: "How do I improve myself and others?" Self-awareness yields an ability to seamlessly fit into any conversation or effort, interacting with a group to work towards the best possible outcome and always iterating towards the best possible outcome.

Frequently called upon to comment on product, customer and community discussions. Is very comfortable in customer and community discussions, aligns efforts, and develops superior solutions through discussion and analysis. Participates deeply in cross-team efforts. Begins to lead discussions on topics that reach outside of design.

Level 7: Staff Product Designer

Leadership Principle
Competencies
Level Expectations

Ownership

Scope: "What do I work on?" Scope is the domain over which you are expected to show ownership.

Consults on product vision and strategy for product area, roadmap, and innovations across teams.

High-Impact

Supervision: "How much do I rely on my Design?" Community: "How do others work with me?" The need to receive supervision is inversely related to the instinct to choose what is high-impact.

Defines new feature assignments for members of other teams, usually without requiring help. Mentors and trains new team members and community designers while leading the coordination and management of design campaigns to create new features and products.

Earn Trust

Influence: "Who do I work with?" As more people and parts of the organization earn your trust, your influence grows.

Frequently sought out by product and engineering leads for opinion on product directions and technical discussions.

Customer Obsession

Customer Impact: "How do I bring value?" Community spans both open-source and enterprise, but ultimately manifests in the same obsession for enabling customers to be successful.

Has ownership for cross-product customer impact topics. Can anticipate complex issues early in the product development process (generally focused within Product). Starts to anticipate and resolve cross functional topics and issues.

Self-Awareness

Interaction: "Who relies on me?" Iteration: "How do I improve myself and others?" Self-awareness yields an ability to seamlessly fit into any conversation or effort, interacting with a group to work towards the best possible outcome and always iterating towards the best possible outcome.

Primary product design lead for projects, providing thought leadership in selecting and guiding these efforts. Works regularly with stakeholders outside of product. Is often the intial resource to drive design efforts for a new product or major feature.

Level 8: Principal Product Designer

Leadership Principle
Competencies
Level Expectations

Ownership

Scope: "What do I work on?" Scope is the domain over which you are expected to show ownership.

Defines product desgin and direction for entire product suites or product divisions.

High-Impact

Supervision: "How much do I rely on my Design?" Community: "How do others work with me?" The need to receive supervision is inversely related to the instinct to choose what is high-impact.

Independently defines new feature assignments across teams working on the same product or system. Influences, shapes and can redirect customer and community product developement discussions, rapidly understanding disparate viewpoints and leading discussions that align thinking and efforts to influence the product direction of large scale projects.

Earn Trust

Influence: "Who do I work with?" As more people and parts of the organization earn your trust, your influence grows.

Seen as the expert on product area of ownership. Engages with peers in customer and partner organizations to shape joint product development plans.

Customer Obsession

Customer Impact: "How do I bring value?" Community spans both open-source and enterprise, but ultimately manifests in the same obsession for enabling customers to be successful.

Works consistently with PM, ENG, and sales leadership to set goals and deliverables for customer value. Represents product design in discussions with non-design functions. Engages heavily with customers and community to share our design philosopy and principles. Applies our philosophy and principles to bring value to customer from work done all across the company.

Self-Awareness

Interaction: "Who relies on me?" Iteration: "How do I improve myself and others?" Self-awareness yields an ability to seamlessly fit into any conversation or effort, interacting with a group to work towards the best possible outcome and always iterating towards the best possible outcome.

Works consistently with PM, ENG, and Mattermost leadership to set organizational objectives and direction. Translates these objectives to clear and actionable projects for prduct design.

Level 9: Distinguished Product Designer

Leadership Principle
Competencies
Level Expectations

Ownership

Scope: "What do I work on?" Scope is the domain over which you are expected to show ownership.

Uses past experience and input from stakeholders to shape and define product design and new features and products for Mattermost. Translates learnings from the broader product design world to bring value to Mattermost's customers and community.

High-Impact

Supervision: "How much do I rely on my Design?" Community: "How do others work with me?" The need to receive supervision is inversely related to the instinct to choose what is high-impact.

Conceives, designs, explains, and oversees product design direction for nearly any feature or product with no outside direciton. Independently executes on cross-team (within prodcut) and cross-function (within Mattermost) effort with little or no supervision. Considered an expert in many design domains. Works across a broad set of product, design, and even technical and non-technical efforts.

Earn Trust

Influence: "Who do I work with?" As more people and parts of the organization earn your trust, your influence grows.

Highly respected by colleagues and community as a design authority, actively influencing discussions and behavior with input and suggestions, and working in sync with PM, ENG, and customer teams. Engages with people in the broader design community (outside of Mattermost) to identify and and implement best practices within Mattermost.

Customer Obsession

Customer Impact: "How do I bring value?" Community spans both open-source and enterprise, but ultimately manifests in the same obsession for enabling customers to be successful.

Works consistently with PM, ENG, and sales leadership to set goals and deliverables for customer value. Represents product design in discussions with non-design functions. Engages heavily with customers and community to share our design philosopy and principles. Applies our philosophy and principles to bring value to customer from work done all across the company.

Self-Awareness

Interaction: "Who relies on me?" Iteration: "How do I improve myself and others?" Self-awareness yields an ability to seamlessly fit into any conversation or effort, interacting with a group to work towards the best possible outcome and always iterating towards the best possible outcome.

Works consistently with PM, ENG, and Mattermost leadership to set organizational objectives and direction. Translates these objectives to clear and actionable projects for prduct design.

PreviousProduct Design team handbookNextTechnical Writing team handbook

Last updated 3 years ago

Was this helpful?