Skip to content

Commit

Permalink
Suggestions
Browse files Browse the repository at this point in the history
Co-authored-by: James Hawkins <[email protected]>
  • Loading branch information
andyvan-ph and jamesefhawkins authored Jan 10, 2025
1 parent 954388b commit 47ea267
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion contents/handbook/company/culture.md
Original file line number Diff line number Diff line change
Expand Up @@ -73,7 +73,7 @@ On Tuesdays and Thursdays, we don't have internal meetings at all. Occasionally

Hiring high-performing and self-sufficient team members means we don't need the typical corporate processes that are designed to slow teams down. Instead, we're organized into [small teams](/handbook/team-structure), which prioritize speed by delegating decision-making autonomy as much as possible.

Our [management approach](/handbook/company/management) is super simple - James Hawkins, Tim, and the team leaders are the only managers, and everyone else reports to one of them. We don't want to create a fancy hierarchy of titles, as we believe this can lead, consciously or not, to people feeling less empowered to make changes and step on toes, especially if they are not in a 'senior' role.
Our [management approach](/handbook/company/management) is super simple - small teams report to their team leader, and each of the team leaders reports to one of our four execs. We don't want to create a fancy hierarchy of titles, as we believe this can lead, consciously or not, to people feeling less empowered to make changes and step on toes, especially if they are not in a 'senior' role.

It's up to you how to get things done. If you want to make a change, feel free to just create the pull request. If you want to discuss something more widely for a bigger piece of work, it might make sense to [use an RFC](/handbook/company/communication#requests-for-comment-rfcs) for a change inside your team.

Expand Down
2 changes: 1 addition & 1 deletion contents/handbook/why-does-posthog-exist.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ Equip every developer to build successful products

Building a successful product is hard; doing so when you don't understand your customers is even harder.

PostHog includes every the tool you need to understand how people use your product, who they are, and how to make them happy.
We aim to offer every tool software teams need to find, sell to, get users, understand who they are, support them and improve their product experience.

### 2. Start from the start

Expand Down

0 comments on commit 47ea267

Please sign in to comment.