Looking for our brand style guide? Look no further.
People
Mission
- Communicate to prospective customers the value we provide
- Educate customers to deploy, manage and use PostHog very easily
- Create a sense of brand (key themes: working in the open and community)
Responsibilities
- Own posthog.com
- Own the docs
Q4 2022 Goals
- Objective:
- Make posthog.com an exceptional experience for new and returning users
- Key Results:
- We enable the community to contribute feedback on what we're building
- We keep the docs updated with any new functionality
- Make apps easy to maintain - make sure they all work, get them into a monorepo, with a standard approach to tests.
- Rationale:
- posthog.com is now regularly referenced as a gold standard website, like Stripe (!). We should go from 'great' to 'exceptional' to get more word of mouth growth and to double down on brand.
- On apps, we want to improve their docs. However, we've realized getting them to work first is the priority - and the way to achieve that is to get them maintainable.
- In Q3, we wanted to check that conversion rates didn't fall as we did some large positioning changes. We should now monitor this as part of business as usual, but it's not as important as we don't anticipate large positioning changes this quarter.
Output metrics
- Primary: Quality signups
How we work
The Website & Docs board is used for enhancements to posthog.com (including handbook) and our docs. Artwork for blog is handled separately, and is explained below.
- [Design] Backlog - a mostly stack ranked list of tasks
- [Design] In progress
- Ready for development - completed designs that are awaiting implementation
- [Development] Backlog - mostly stack ranked
- [Development] In progress
- Done
Designs for website & docs typically start in Balsamiq wireframes, then progress into hi-fi designs in Figma. Read more about this process.
Blog artwork and marketing assets
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.
Providing feedback
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!)
Slack channels
- #team-website - general website betterment
- #team-design - more internal discussion about topics interesting to designers