• 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
      • Breaking glass to debug PostHog Cloud
      • Developing the website
      • MDX setup
      • Markdown
      • Jobs
    • 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
      • Breaking glass to debug PostHog Cloud
      • Developing the website
      • MDX setup
      • Markdown
      • Jobs
    • 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

Joe Martin's README

Last updated: Oct 31, 2022

On this page

  • Bio
  • How I can help you
  • How to work with me
  • Areas of focus - Q4 2022
  • Feedback

Bio

This is my fifth start-up.

Before I took up Product Marketing I was a Content Marketer, a Copywriter and a Journalist. Before that I was a clown, a chainsaw salesman and a cleaner in a morgue. It's been a strange life.

I live just outside of London. I'm passionate about punk music, videogame preservation and garlic. I can't ride a bike.

How I can help you

  • I can help you figure out the right way to communicate anything, to anyone.
  • I can help you with a broad range of marketing tasks, including sales enablement.
  • I can help you understand our customers, our competitors or the press.
  • I can help with literally anything involving writing, editing or proof-reading.
  • I enjoy helping others. You can ask me anything. There are no stupid questions.
  • I help engineering with marketing stuff. Need content for a new feature? I'm your man.

How to work with me

  • I can be over-communicative and need to be challenged on this. Want the short version? Ask.
  • I have a very hands-on attitude and will never say 'That's not my job'.
  • I may parrot ('It sounds like...') to ensure I understand. If I'm wrong, tell me.
  • I'm really uncomfortable with being in the limelight. I prefer private thank yous.
  • I value compassion and inclusivity above everything else. I try to put people first.
  • Ad-hoc meetings are fine, but weekends are sacred. I generally work 9-6 GMT.

Areas of focus - Q4 2022

Last quarter I focused on collaborating with the growth and product teams to directly contribute to product improvements (such as tutorials and activation flows), growing external communities and partnerships, and becoming more autonomous/skilled technically so that I could contribute directly to the product. These were all successful.

This quarter I'm focusing on...

  • Onboarding: Previously I've provided content and research to inform v1 of our onboarding flows. This quarter, I'm going to take greater ownership of onboarding by delivering improvements to our emails, as well as continuing to work with Growth on improving in-product activation.
  • Announcements: We have some specific things we want to announce, such as EU Cloud. We also have regular announcements, such as Array. In addition to taking ownership of the former, I'll also find ways to directly improve the latter. A static page for Array? In-app announcements for new features? Better emails? Whatever is needed.
  • Word of mouth growth: We're starting to get a more detailed view of where our WOM growth comes from. I'll spend time scaling this growth with the marketing team. This could involve a referral program, influencers or levelling up and/our case studies. Maybe all of the above.
  • Product design: This is a personal goal. I'm switching from just-in-case to just-in-time technical learning and focusing on improving my knowledge of product design instead. The goal is to become more effective when providing feedback and when planning in-product proposals. Good thing we have a generous book budget.

This list is not exhaustive and is meant to guide the sort of work I do at a high level. If something more important comes up where I'll have more impact? Pivoting is fine.

Feedback

In our last 360 feedback session, I received feedback on the following points.

  • I am seen as an effective and flexible executor, planner, writer and storyteller.
  • I am seen as empathetic and extremely supportive of others, especially new colleagues or those with less experience than me.
  • I am seen as brave when giving feedback and stepping on toes. Others recognize that I default to transparency.
  • Work I do, such as case studies, is seen as valuable and showing a lot of insight.
  • I am seen as over-cautious and too detail-orientated when planning new work.
  • I am seen as over-communicative in social discussions. I talk a lot about diversity, but fail on follow-through.
  • I am seen as biased to my past experiences. This limits my potential impact.

A few months later, I had my career chat with Marcus and gathered additional feedback. PostHog team members can read notes from this conversation and summary of the feedback for more info.

I'm always open to more feedback, from anyone. Got some? Send it to me!

Questions?

Was this page useful?

Authors

  • justinjones
    justinjones
  • Joe Martin
    Joe Martin

Share

Jump to:

  • How I can help you
  • How to work with me
  • Areas of focus - Q4 2022
  • Feedback
  • 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?
  • 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