惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

aimingoo的专栏
aimingoo的专栏
WordPress大学
WordPress大学
阮一峰的网络日志
阮一峰的网络日志
博客园 - 司徒正美
月光博客
月光博客
宝玉的分享
宝玉的分享
Recent Announcements
Recent Announcements
小众软件
小众软件
H
Hackread – Cybersecurity News, Data Breaches, AI and More
美团技术团队
博客园 - 三生石上(FineUI控件)
A
About on SuperTechFans
J
Java Code Geeks
云风的 BLOG
云风的 BLOG
罗磊的独立博客
大猫的无限游戏
大猫的无限游戏
IT之家
IT之家
Vercel News
Vercel News
量子位
Martin Fowler
Martin Fowler
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
V
Visual Studio Blog
腾讯CDC
有赞技术团队
有赞技术团队

PostHog's RSS Feed

Training our own AI models - PostHog From 270GB RAM to 5GB: Moving local flag evaluation from Django to Rust The best analytics stack for vibe-coded apps The do's and don'ts of minimum viable product marketing - PostHog The best MCP servers for startups, by workflow 4,063 errors closed without a human opening PostHog – here's what we learned - PostHog PostHog Code and the self-driving product - PostHog Why attacking your competitors online is dumb - PostHog The best real-time analytics platforms for developers, compared DuckDB vs ClickHouse: Why we use both at PostHog - PostHog PostHog's next chapter - PostHog Making Claude Cowork actually useful - PostHog PostHog vs Matomo in-depth tool comparison You're doing lifecycle emails wrong Untangling Tokio and Rayon in production: From 2s latency spikes to 94ms flat The best HIPAA-compliant A/B testing tools - PostHog A beginner's guide to testing AI agents - PostHog I hate the standup bot (so I built an agent to do it for me) - PostHog The best CDPs for developers, compared The best error tracking tools for developers, compared The best feature flag software for developers, compared 7 best session replay tools for mobile apps 7 best free open source business intelligence tools right now 7 best free and open source LLM observability tools PostHog vs LogRocket in-depth tool comparison The most popular PostHog alternatives, compared Open source (and self-hosted) session replay tools - PostHog The 9 best GA4 alternatives for apps and websites - PostHog PostHog vs Google Analytics 4 in-depth tool comparison How we built automatic clustering for LLM traces - PostHog
How PostHog's new VP focused the company on nailing funne...
Marcus Hyett · 2021-07-01 · via PostHog's RSS Feed

Ramping up fast in any senior product role requires understanding as much context as possible across 3 axes (Market, Product and People). I’ll talk you through my process of going from zero understanding in these three areas, to landing a clear, ambitious long-term strategy across the company in just one week.

Phase 1: Understanding context

Market

Customer interviews

We have a wealth of documented in-depth interviews with existing customers and prospects around their experience with PostHog, and I was able to attend a few live interviews in my first week. I read the transcript of every single interview (some multiple times), pulling out key themes and looking beyond what they were asking for to try and work out why they were asking for it. This created a shortlist of critical needs we must solve for to make our customers successful.

Competitor research

When you’re new to a market with existing competitors it’s important to understand who they are and what’s unique about their products. I analyzed the marketing and documentation of a number of our competitors to understand our potential gaps and advantages. It’s key not to get hung up on features our competitors have which we don’t - we must focus on building the best solution to the problems our customers have, which might look different to what our competitors offer.

Analytics

PostHog is a product analytics tool, so I was able to get set-up and analyse the behavior of our users within a few hours. I focused on breaking down how our existing product is used across different dimensions to understand which of our capabilities are most valuable to our existing customers and have the biggest growth opportunities.

Product

Mission

PostHog's mission to "Increase the number of successful products in the world" was a big reason I joined the company, and that phrase provided context to building out a long-term direction.

Dogfooding

Every good product manager is one of the world’s top users of their product. I spent over 12 hours in my first week using the product inside and out, identifying bugs, drawbacks and opportunities for the product along the way.

Tasks and feature requests

To gather context on how the team prioritizes and what they’re currently working on, I spent a number of hours reading through open GitHub issues. This gave me insight into what our community is expecting and experiencing when they use PostHog.

People

Intro interviews and insights

I attempted to meet with every single person in the company in my first week - a few meetings spilled over into the second week. I introduced myself and got to learn about them, their history, and what they’re passionate about. I asked everyone the same three questions:

  • In your opinion, what's the long term direction of PostHog?
  • What do you think is the biggest blocker to our success?
  • What can I do to help you become more successful?

The answers to these questions were really enlightening. It was immediately clear that the company had been quite reactive and that a proactive strategy would be welcomed. I also got a great understanding of what the future of PostHog might look like and what I can do to help each individual succeed.

Insights

Based on these interviews, I aggregated the key themes as a collection of insights to share with the team. This also gave me the opportunity to identify and share a number of immediate actions I would be taking to help push the company forward.

Long-term direction & audience

The cornerstone of every strategy is having a long-term direction to point everything else towards. It was easy to build a long term vision for 2023 with insights from the intro interviews and leveraging PostHog’s existing mission. We identified a segment that resonated well with our existing successful customers and has a lot of growth potential.

First milestone

With a long term vision, clear focused audience, and a ton of context about our customers, their needs, the market and how our product is used today, we identified one thing we needed to get right before anything else: funnels.

Feedback & iteration

To get buy-in, it was crucial for me to share the draft with the entire company and get as much feedback as possible. The feedback was comprehensive and enabled me to quickly iterate on the first version. To make the strategy easy to remember and execute, we came up with a memorable two-word version of our top priority: “nail funnels”.

But you can't just assume everyone will buy into the strategy because you posted it somewhere and they gave it a thumbs up. You have to talk people through it 1:1 and communicate the message via different channels. We discussed the new strategy in all our small team standups, company all-hands, and uploaded it to our website.

Read more about our strategy in the strategy overview.

Subscribe to our newsletter

Product for Engineers

Read by 100,000+ founders and builders

We'll share your email with Substack