• Product
  • Pricing
  • Docs
  • Using PostHog
  • Community
  • Company
  • Login
  • Table of contents

  • Handbook
    • Start here
    • Meetings
    • Story
    • Team
    • Investors
    • Strategy overview
    • Business model
    • Objectives
    • Roadmap
    • Brand
    • Culture
    • Values
    • Small teams
    • Goal setting
    • Diversity and inclusion
    • Communication
    • Management
    • Offsites
    • Security
    • Brand assets
    • Team structure
    • Customer Success
    • Exec
    • Experimentation
    • Growth
    • Infrastructure
    • Marketing
    • People & Ops
    • Pipeline
    • Product Analytics
    • Session Recording
    • Website & Docs
    • Compensation
    • Share options
    • Benefits
    • Time off
    • Spending money
    • Progression
    • Training
    • Side gigs
    • Feedback
    • Onboarding
    • Offboarding
      • Product Manager ramp up
    • Merch store
      • Overview
      • How to interview
      • Engineering hiring
      • Marketing hiring
      • Operations hiring
      • Design hiring
      • Exec hiring
      • Developing locally
      • Tech stack
      • Project structure
      • How we review PRs
      • Frontend coding
      • Backend coding
      • Support hero
      • Feature ownership
      • Working with product design
      • Releasing a new version
      • Handling incidents
      • Bug prioritization
      • Event ingestion explained
      • Making schema changes safely
      • How to optimize queries
      • How to write an async migration
      • How to run migrations on PostHog Cloud
      • Working with ClickHouse materialized columns
      • Deployments support
      • Working with cloud providers
      • How-to access PostHog Cloud infra
      • Developing the website
      • MDX setup
      • Markdown
      • Jobs
      • Overview
      • Data storage or what is a MergeTree
      • Data replication
      • Data ingestion
      • Working with JSON
      • Query performance
      • Operations
        • Overview
        • sharded_events
        • app_metrics
        • person_distinct_id
    • Shipping things, step by step
    • Feature flags specification
    • Setting up SSL locally
    • Tech talks
    • Overview
    • Product metrics
    • User feedback
    • Paid features
    • Releasing as beta
    • Our philosophy
    • Product design process
    • Designing posthog.com
    • Overview
    • Personas
    • Testimonials
    • Value propositions
      • Content & SEO
      • Sponsorship
      • Paid ads
      • Email
      • Press
    • Growth strategy
    • Customer support
    • Inbound sales model
    • Sales operations
      • Managing our CRM
      • YC onboarding
      • Demos
      • Billing
      • Who we do business with
    • Growth reviews
  • Table of contents

  • Handbook
    • Start here
    • Meetings
    • Story
    • Team
    • Investors
    • Strategy overview
    • Business model
    • Objectives
    • Roadmap
    • Brand
    • Culture
    • Values
    • Small teams
    • Goal setting
    • Diversity and inclusion
    • Communication
    • Management
    • Offsites
    • Security
    • Brand assets
    • Team structure
    • Customer Success
    • Exec
    • Experimentation
    • Growth
    • Infrastructure
    • Marketing
    • People & Ops
    • Pipeline
    • Product Analytics
    • Session Recording
    • Website & Docs
    • Compensation
    • Share options
    • Benefits
    • Time off
    • Spending money
    • Progression
    • Training
    • Side gigs
    • Feedback
    • Onboarding
    • Offboarding
      • Product Manager ramp up
    • Merch store
      • Overview
      • How to interview
      • Engineering hiring
      • Marketing hiring
      • Operations hiring
      • Design hiring
      • Exec hiring
      • Developing locally
      • Tech stack
      • Project structure
      • How we review PRs
      • Frontend coding
      • Backend coding
      • Support hero
      • Feature ownership
      • Working with product design
      • Releasing a new version
      • Handling incidents
      • Bug prioritization
      • Event ingestion explained
      • Making schema changes safely
      • How to optimize queries
      • How to write an async migration
      • How to run migrations on PostHog Cloud
      • Working with ClickHouse materialized columns
      • Deployments support
      • Working with cloud providers
      • How-to access PostHog Cloud infra
      • Developing the website
      • MDX setup
      • Markdown
      • Jobs
      • Overview
      • Data storage or what is a MergeTree
      • Data replication
      • Data ingestion
      • Working with JSON
      • Query performance
      • Operations
        • Overview
        • sharded_events
        • app_metrics
        • person_distinct_id
    • Shipping things, step by step
    • Feature flags specification
    • Setting up SSL locally
    • Tech talks
    • Overview
    • Product metrics
    • User feedback
    • Paid features
    • Releasing as beta
    • Our philosophy
    • Product design process
    • Designing posthog.com
    • Overview
    • Personas
    • Testimonials
    • Value propositions
      • Content & SEO
      • Sponsorship
      • Paid ads
      • Email
      • Press
    • Growth strategy
    • Customer support
    • Inbound sales model
    • Sales operations
      • Managing our CRM
      • YC onboarding
      • Demos
      • Billing
      • Who we do business with
    • Growth reviews
  • Handbook
  • Strategy
  • Brand

Brand

Last updated: Oct 04, 2022

On this page

  • 20 year roadmap
  • Top 3 values
  • Top 3 audiences
  • Personality sliders
  • Competitive landscape
  • Brand assets

This page is a very simple guide to the PostHog brand. The purpose of these diagrams is to provide a concrete representation of PostHog's brand, so that we have a common reference point when we are working on new design, product, marketing and strategy initiatives. Should our website design be more serious or playful? Are we writing articles in a tone of voice that makes sense? These questions should be easier to answer with this guide.

A brand guide also helps our team (especially newcomers) and customers understand what we stand for.

This guide is dynamic, not fixed - we fully expect it to change over time, especially as we learn more about our users and market.

We used a template from GV to run the 3-hour brand sprint that generated the outputs below.

20 year roadmap

This is highly speculative from 10 years onwards - we only really think about our strategy in detail over the next 5 years. Nobody should expect us to stick to this - the point is to push us to think about the really long term. We want PostHog to last into the 2040s, and further...

Screenshot 2021-12-03 at 11 12 29

Top 3 values

We have already spent a lot of time creating and refining our values. The objective here was to select the top 3 most important, and then the top 1. To borrow from Jake Knapp: "knowing your most important value makes decisions easier, clarifies your message, and sets you apart from the competition."

In 20 years' time, we believe that if we have adhered to this value above all others, we'll be in a good place.

Screenshot 2021-12-03 at 11 17 24

Top 3 audiences

The intention here is to go broader than pure job titles (which is what we do when we develop personas). Here we're asking 'who are the most important people whose opinions we care about?'. We believe that, if we build products that the below 3 audiences love, we will build a successful business.

Screenshot 2021-12-03 at 11 22 39

Personality sliders

There are several different axes that we can plot the PostHog brand against. This exercise helped us align on how we want to position ourselves externally, and was particularly revealing as different team members perceived the brand quite differently in some cases. For example, on the 'Friend' vs. 'Authority' axis, we realized that being seen as credible thought leaders meant we couldn't go too far to the 'Friend' extreme.

Screenshot 2021-12-03 at 11 24 39

Competitive landscape

The graph that brand teams at our competitors will hate. It's important to remember that this graph doesn't mean one place is 'good' and another is 'bad' (with the exception of 'ignorance' probably). Instead, this graph is a helpful reminder of how we want to position our brand relative to other brands. For example, if we decide to make our visual imagery more reserved, we should question whether this will help or hurt our ability to stand out in the market.

Screenshot 2021-12-03 at 11 26 30

Brand assets

We keep a comprehensive list of brand assets and guidelines for their use on the dedicated brand assets page.

Questions?

Was this page useful?

Next article

Culture

So, what's it like working at PostHog? All remote Our team is 100% remote, and distributed across over 10 countries. As well as the equipment you'll need, we provide a budget to help you find coworking space or to cover the costs of coffees for those who prefer not to work at home. All remote has a bunch of advantages: We can hire amazing people from a global talent pool. Being remote encourages a deeper level of personal thought and writing things down. It allows for uninterrupted work…

Read next article

Authors

  • James Hawkins
    James Hawkins
  • Cory Watilo
    Cory Watilo
  • Charles Cook
    Charles Cook

Share

Jump to:

  • 20 year roadmap
  • Top 3 values
  • Top 3 audiences
  • Personality sliders
  • Competitive landscape
  • Brand assets
  • Questions?
  • Edit this page
  • Raise an issue
  • Toggle content width
  • Toggle dark mode
  • Product

  • Overview
  • Pricing
  • Product analytics
  • Session recording
  • A/B testing
  • Feature flags
  • Apps
  • Customer stories
  • PostHog vs...
  • Docs

  • Quickstart guide
  • Self-hosting
  • Installing PostHog
  • Building an app
  • API
  • Webhooks
  • How PostHog works
  • Data privacy
  • Using PostHog

  • Product manual
  • Apps manuals
  • Tutorials
  • Community

  • Questions?
  • Product roadmap
  • Contributors
  • Partners
  • Newsletter
  • Merch
  • PostHog FM
  • PostHog on GitHub
  • Handbook

  • Getting started
  • Company
  • Strategy
  • How we work
  • Small teams
  • People & Ops
  • Engineering
  • Product
  • Design
  • Marketing
  • Customer success
  • Company

  • About
  • Team
  • Investors
  • Press
  • Blog
  • FAQ
  • Support
  • Careers
© 2022 PostHog, Inc.
  • Code of conduct
  • Privacy policy
  • Terms