Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Culture handbook updates #10241

Open
wants to merge 12 commits into
base: master
Choose a base branch
from
Open

Culture handbook updates #10241

wants to merge 12 commits into from

Conversation

andyvan-ph
Copy link
Contributor

@andyvan-ph andyvan-ph commented Jan 2, 2025

Changes

  • Integrates @raquelmsmith's suggestions from draft expectations #10115 around employee expectations into 'How you can help' page
  • Creates dedicated Lore page (previously on "how you an help" page)
  • Some light updates to the Culture page to bring it up to date

Additional: The values page still references 'Bias for impact' instead of action. I made an attempt at updating this, but abandoned it as wasn't sure what the correct wording should be. Feel free to have stab at that and add to this PR.

Copy link

vercel bot commented Jan 2, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
posthog ✅ Ready (Inspect) Visit Preview Jan 6, 2025 11:37am

@andyvan-ph andyvan-ph mentioned this pull request Jan 2, 2025
Copy link
Collaborator

@corywatilo corywatilo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lore.md is capitalized, so it 404s on the server. (It works locally because the filesystem is casing-agnostic, but it does matter on the server.) To get it to rename (and for Git) to pick up on the changes, you'll need to change it in two commits (because Mac OS won't see the casing rename as an actual change):

  1. Rename Lore.md to something like lore-temp.md, then commit
  2. Rename lore-temp.md to lore.md, then commit

I also saw the lore content was left in /handbook/help. Was it meant to be duplicated so it lives there and the dedicated page? Otherwise I might reference it in the help page, but then link it to the full page you created for it.

* It makes results clearer, which helps us hold people to account for outcomes rather than hours spent in the office.
* It encourages thoughtful, and intentional, written communication
* It creates space for lots of uninterrupted work.
* We judge performance based on real outcomes, not hours spend in the office.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"in the office" → "in front of your computer"?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could change to "hours spent in an office". I think the point is begin remote eliminates presenteeism, which is specifically associated with being in an office.

contents/handbook/company/culture.md Outdated Show resolved Hide resolved
contents/handbook/help.md Outdated Show resolved Hide resolved
src/navs/index.js Show resolved Hide resolved
contents/handbook/help.md Outdated Show resolved Hide resolved
contents/handbook/help.md Outdated Show resolved Hide resolved
@andyvan-ph
Copy link
Contributor Author

I also saw the lore content was left in /handbook/help. Was it meant to be duplicated so it lives there and the dedicated page? Otherwise I might reference it in the help page, but then link it to the full page you created for it.

I just forgot to save the page. Should be gone now.

contents/handbook/company/culture.md Outdated Show resolved Hide resolved
contents/handbook/company/culture.md Outdated Show resolved Hide resolved
contents/handbook/help.md Outdated Show resolved Hide resolved
andyvan-ph and others added 2 commits January 3, 2025 09:46
Co-authored-by: Ian Vanagas <34755028+ivanagas@users.noreply.github.com>
contents/handbook/help.md Show resolved Hide resolved
contents/handbook/company/culture.md Outdated Show resolved Hide resolved
@@ -48,13 +46,13 @@ To accomplish this, we use [asynchronous communication](/handbook/company/commun

Putting things in writing helps us clarify our own ideas, as well as allow others to provide better feedback. It has been key to our development and growth.

## Don't let others fail
## We don't let others fail
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel like this is somewhat at odds with our performance expectations and the fact that we do let people go if they aren't able to perform.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I see your point. This has been in here for a while. The actual words on this don't really match the heading anyway. When you read it, it's more about pushing people to do better all the time, rather than being satisfied with "good enough". At least, that's how I read it.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I feel like this heading has nothing to do with the content. Maybe "We give direct feedback early and often" and link to the blog post about this?


### Start from the start
### 2. Useful at every stage
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this something that was discussed somewhere / agreed to change? I think this framing of "start from the start" is useful strategically, whereas "useful at every stage" is less specific and generic and not very helpful.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, just my suggestion. "Start from the start" is just confusing to me! It think this used by "Get in first", which made more sense to me. Anyway, I don't feel strongly, so can remove this.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree, I like the prior wording to "get in first" better


## All remote
[Our team](/people) is 100% remote, and distributed across more than 15 countries.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@smallbrownbike we should automate this number

Copy link
Member

@rafaeelaudibert rafaeelaudibert Jan 5, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's a hardcoded country number reference in contents/handbook/company/grown-ups.md as well

contents/handbook/help.md Outdated Show resolved Hide resolved
contents/handbook/help.md Outdated Show resolved Hide resolved
contents/handbook/help.md Outdated Show resolved Hide resolved
contents/handbook/help.md Outdated Show resolved Hide resolved
Co-authored-by: Raquel Smith <raquelmsmith@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants