We're building a feature request board, and adding a "Work in progress" section to show what we're working on _right now!_
No updates yet. Engineers are currently hard at work, so check back soon!
Two things in life are true: Nobody ever reads the T&Cs, and nobody ever reads annoying updates about how those T&Cs have been updated either.
Still, we think it's important that you have an idea of our terms when you sign up to PostHog - so we redesigned them to be more fun to read, and easier to understand.
Objective: Make PostHog.com a destination for product engineers and PostHog customers
Objective: Make it easier to develop on PostHog.com, and make sure things still work under heavy traffic loads
Objective: Make it easier to find answers directly on PostHog.com (vs Google)
Make the website better
Get community to product-market fit
Continue to rove across product as we’re able
There are hundreds of Linear-style websites out there. We are intentionally not one of them. Becoming the inspiration never started by copying what already existed. It's better to be copied than to copy.
Plenty of services exist to make building websites easier, but they're limited by someone else's creativity. No off-the-shelf solution solves 100% of every problem. In order for us to execute our vision to 100%, we need complete control of the entire experience.
"Death by a thousand cuts, but a thousand tiny improvements add up"
Our website isn't a marketing site. It's our primary channel for sales, recruitment, and communicating our company culture and values. Since these are always evolving, we are constantly evolving how we communicate them.
Doing unique things that unexpectedly delight visitors will pay off dividends over adding more signup CTAs to a page. Building for the long-term pays dividends over optimizing for the short term boost in conversion rate.
Sometimes users (even internal users) don't typically think past the immediate challenge they're facing. Take the time to step back and decide if a bit more thought and effort can make things 10x better.
Our team works in weekly sprints. We run joint sprint planning sessions with the Marketing team, since we often have projects that overlap. You can find what we're working on in the company-internal repo (private).
Designs for website & docs typically start in Balsamiq wireframes, then progress into hi-fi designs in Figma. Read more about this process.
Because of the volume of content we publish, blog artwork has its own dedicated Artwork project board managed by Lottie.
When authoring a blog post, add the Artwork project board so we can create visuals and make sure the post is listed on our content calendar with a publish date. Learn more about our process.
When we share a design, we do our best to explain the type of feedback we're looking for. (Ex: Overall visual aesthetic, flow, if a design communicates to our developer-focused audience, etc.)
If a screenshot is posted directly to a Github issue, that's a great place for feedback. (If a comment already covers your feedback, we encourage the use of an emoji response over additional comments like "+1".)
Some of the design tools we use, like Balsamiq and Figma, both have built-in commenting, which is useful for prototypes with multiple pages. If we provide a link to a prototype in one of these tools, please leave a comment using the app's comment system. This helps us review and take action on comments later, and creates a single place for discussion around a particular topic.
Important: We prioritize feedback based on alignment with business goals. Everyone has feedback about design. (If feedback is more of a personal opinion than a business-related perspective, we’ll note it, but don't be offended if your feedback isn't specifically addressed!)
