Looking for our brand style guide? Look no further.
Designers are spread between Small Teams. Like sovereign states have ambassadors, our designers live on the ground in the places where we can tangibly offer support.
|Lottie Coxon||Graphic Designer||Marketing, Growth|
|Cory Watilo (Team lead)||Design Lead||Growth|
|Chris Clark||Product Designer||Core Experience, Core Analytics|
We’re here to:
- Support Small Teams (and contributors) in building better versions of PostHog
- Enable customers to build better products (using PostHog)
- Communicate to prospective customers the value we provide
- Initiate new projects to support the missions above
- Support Small Teams in completing their sprint tasks
- Iterate based on feedback from customers, in collaboration with other Small Teams
How we work
Design tasks are managed on GitHub project boards. See below:
Need product design help? Learn how to request assistance from a product designer.
Website & Docs (posthog.com)
The Website & Docs board is used for enhancements to posthog.com marketing pages, our Docs, and Handbook. (Artwork for blog is handled separately, and is explained below.)
Because design and website development are closely related, we share a project board.
- [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
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.
Note: Not all posts get custom artwork. We prioritize creating custom art for posts that are anticipated to receive high traffic, will likely end up on HackerNews, or will be promoted on social media or in promoted posts. However we do have a library of hedgehog-themed art and topic-based artwork that may be used or repurposed for posts that don't receive custom artwork.
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!)
Working on something and need help from design?
Tag issue or PR with relevant project board.
|Product design||Mention @clarkus and assign to relevant board||Core Experience, Core Analytics|
|Website & Docs||Assign to project board||Website & Docs|
|Blog artwork||Assign to project board||Artwork|