Product design process

Last updated:

"No design by default"

We encourage engineers to act like feature owners, carrying a project from ideation to completion. We maintain a design system in Storybook so engineers can build high-quality features independently, as much as possible.

Because engineers choose their sprint tasks near the beginning of a sprint (and product doesn't plan tasks for engineers in advance), our process doesn't allow for us to have a product manager and a designer to work closely together before a task gets selected by an engineer.

In our process of short, 2-week sprints with no pre-planning, design would become a blocker to an engineer quickly iterating on a feature. Thus, we've settled on the general rule of that engineers don't get support from product designers by default.

This doesn't mean product design should never be involved. But designers can weigh in on if their support would be useful for a given task, or if design is premature for a project.

Learn more about how we decide this in our guide to working with product designers, for engineers.

People

NameRoleTeam(s)
Lottie CoxonGraphic DesignerWebsite & Docs, Marketing
Cory Watilo (Team lead)Design LeadApp teams, Website & Docs

Design at PostHog:

  • Supports Small Teams (and contributors) in building better versions of PostHog
  • Enables customers to build better products (using PostHog)
  • Make it easy for third party developers to build apps on top of our Product OS
  • Exists to make the best damn SaaS website and docs in the world

Blog artwork and marketing assets

Because of the volume of content we publish, all requested artwork has its own dedicated Artwork project board managed by Lottie. Please add a small description/brief, level of importance and a hard deadline: this will allow Lottie to priortise which projects get done first around her own sprint tasks.

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.

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!)

Portfolio

You can find PostHog's design portfolio on Dribbble... or just have a look around!

Questions?

Was this page useful?

Next article

Designing posthog.com

The Website & Docs Team is responsible for everything you see on posthog.com. We treat our website & docs as a product, which means we're constantly iterating on it and improving it. Because our website has a well-defined aesthetic, we often skip the hifi design process and jump straight from wireframes into code. Having a designer who can code means we can reach the desired level of polish without always having to produce hifi designs, thus leading to huge time savings. Usually Eli will…

Read next article