COMPANY PLAYBOOK

PostHog

PostHog shortens decision distance through transparency and small autonomous teams, consciously accepting some integration debt for speed.

Operating system

System principles

Team autonomy creates speed but may produce product inconsistency and shared-platform debt.
Radical openness speeds feedback but can feel harsh without psychological safety.

PRACTICES

Team structure

Teams own goals, roadmaps, metrics and user conversations.

How it works: Teams of six or fewer own goals, roadmap, metrics and user conversations together.
Why it is used: Keeps decisions close to information and users.
Trade-off: Risks duplicated solutions and product inconsistency.
Best fit: Organizations with modular product surfaces and strong individual ownership.

Ownership

The driver is the explicit owner of decisions and progress.

How it works: Each meaningful piece of work has an explicit driver accountable for progress and decisions.
Why it is used: Reduces committee decisions and ambiguous ownership.
Trade-off: Decision quality can fall if the driver does not gather enough context.
Best fit: Work with many contributors but a single final decision owner.

Hiring

Candidates do paid real work to generate hiring signal.

How it works: Candidates are observed by the team doing paid, work-like tasks.
Why it is used: Produces work signal instead of interview-performance signal.
Trade-off: Costs candidate time and a short sample cannot fully predict long-term performance.
Best fit: Knowledge work where output can be observed in a bounded sample.

Product

Some product inconsistency is accepted in exchange for small-team speed.

How it works: Some integration and consistency debt is accepted to preserve local team speed.
Why it is used: Prevents central coordination from slowing every delivery.
Trade-off: Customer experience can fragment and later require platform investment.
Best fit: During discovery, with clear team boundaries and reversible decisions.