draft expectations

[raquelmsmith]

Changes

This is very draft because I feel like it could be a little 🌶️

These are things I've ended up telling new hires multiple times, figured it might be worth writing down.

I'm not sure having this in its own doc, or having it at all, makes sense. I thought about putting it in the values or culture docs, but it didn't really seem to fit as it's fairly specific "dos and don'ts" style. I guess we could add some "dos and don'ts" to the culture page for every heading 🤔

Anyway, feedback on if this seems useful and what to change would be good.

[vercel]

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

Name	Status	Preview	Updated (UTC)
posthog	✅ Ready (Inspect)	Visit Preview	Dec 11, 2024 10:19pm

[corywatilo]

Love this!

[charlescook-ph]

Thoughts in no particular order:

• I'd rewrite combine this with the Culture page - that page is pretty out of date and kinda boring in parts. We could also remove the video.
• This seems very eng-focused, which is fine - an alternative could be to add this to the Engineering section of the Handbook instead.
• We generally refer to people in the Handbook as 'team members' not 'employees'.

[andyvan-ph]

+1 to Charles points. Ping me if you want help merging the two pages.

[raquelmsmith]

Okay we can combine with culture page. @andyvan-ph Happy to have you help with that since I'm not really sure the best way to put it together.

I think my examples are engineering specific because that's where I came from, but I think the principles are generic. Maybe Andy you can come up with some examples that aren't for engineering?