Recommend Hogpatch or Hedge House for offsites and onboarding#16984
Conversation
Default team offsites and in-person onboarding to Hogpatch (SF) or the Hedge House (London) — both are set up for it, remove planning friction, and put teams in the same space as other PostHog teams for cross-team collaboration. Also trims a few bits of the small team offsites section that are now redundant (Kendal finding accommodation, the layover-minimising guideline, and the duplicate Hogpatch callout under the London Hedge House section). Generated-By: PostHog Code Task-Id: a2899ac5-1d6f-4b8c-baf6-3ce003539639
Deploy preview
|
|
Vale prose linter → found 63 errors, 72 warnings, 2 suggestions in your markdown Full report → Copy the linter results into an LLM to batch-fix issues. Linter being weird? Update the rules!
|
| Line | Severity | Message | Rule |
|---|---|---|---|
| 7:82 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 21:46 | warning | 'Mykonos' is a possible misspelling. | PostHogBase.Spelling |
| 23:178 | warning | Use the Oxford comma before 'and' or 'or' in a list of three or more items. | PostHogBase.OxfordComma |
| 23:293 | warning | Use the Oxford comma before 'and' or 'or' in a list of three or more items. | PostHogBase.OxfordComma |
| 39:180 | warning | Use American English. Use 'traveling' instead of 'travelling'. | PostHogBase.AmericanEnglish |
| 39:201 | warning | 'Hogpatch' is a possible misspelling. | PostHogBase.Spelling |
| 43:51 | warning | 'Hogpatch' is a possible misspelling. | PostHogBase.Spelling |
| 44:125 | warning | 'Hogpatch' is a possible misspelling. | PostHogBase.Spelling |
| 48:86 | warning | 'Kendal' is a possible misspelling. | PostHogBase.Spelling |
| 53:32 | warning | 'Kendal' is a possible misspelling. | PostHogBase.Spelling |
| 54:3 | warning | 'Kendal' is a possible misspelling. | PostHogBase.Spelling |
| 60:26 | warning | 'Kendal' is a possible misspelling. | PostHogBase.Spelling |
| 63:24 | warning | 'hoc' is a possible misspelling. | PostHogBase.Spelling |
| 63:39 | warning | 'Kendal' is a possible misspelling. | PostHogBase.Spelling |
| 63:83 | suggestion | Prefer 'proper nouns or they' over 'she'. | PostHogBase.Inclusivity |
| 69:117 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 70:230 | warning | Use American English. Use 'organizing' instead of 'organising'. | PostHogBase.AmericanEnglish |
| 71:58 | warning | 'Kendal' is a possible misspelling. | PostHogBase.Spelling |
| 73:285 | warning | 'Figjam' is a possible misspelling. | PostHogBase.Spelling |
| 84:64 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 85:3 | warning | 'Dogfooding' is a possible misspelling. | PostHogBase.Spelling |
| 86:11 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 87:56 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 89:167 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 93:103 | warning | Use American English. Use 'judgment' instead of 'judgement'. | PostHogBase.AmericanEnglish |
| 93:158 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 93:313 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 99:4 | warning | 'Hedge House' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 101:39 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 101:219 | warning | 'onboardings' is a possible misspelling. | PostHogBase.Spelling |
| 101:355 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 101:368 | warning | 'Hogpatch' is a possible misspelling. | PostHogBase.Spelling |
| 107:49 | warning | 'homebase' is a possible misspelling. | PostHogBase.Spelling |
| 107:66 | warning | 'Farringdon' is a possible misspelling. | PostHogBase.Spelling |
| 111:18 | warning | 'onboardings' is a possible misspelling. | PostHogBase.Spelling |
| 113:4 | warning | 'Marrable's' is a possible misspelling. | PostHogBase.Spelling |
| 113:15 | warning | 'Farringdon' is a possible misspelling. | PostHogBase.Spelling |
| 114:8 | warning | 'Zetter' is a possible misspelling. | PostHogBase.Spelling |
| 114:15 | warning | 'Clerkenwell' is a possible misspelling. | PostHogBase.Spelling |
| 115:17 | warning | 'Clerkenwell' is a possible misspelling. | PostHogBase.Spelling |
| 116:4 | warning | 'Yotel' is a possible misspelling. | PostHogBase.Spelling |
| 119:16 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 120:22 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 121:30 | warning | 'Clerkenwell' is a possible misspelling. | PostHogBase.Spelling |
| 125:178 | warning | Use American English. Use 'optimize' instead of 'optimise'. | PostHogBase.AmericanEnglish |
| 125:220 | warning | 'accom' is a possible misspelling. | PostHogBase.Spelling |
| 127:4 | warning | 'Border Control' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 131:136 | warning | 'colleauges' is a possible misspelling. | PostHogBase.Spelling |
| 131:190 | warning | 'colleauges' is a possible misspelling. | PostHogBase.Spelling |
| 131:992 | warning | Use American English. Use 'traveling' instead of 'travelling'. | PostHogBase.AmericanEnglish |
| 137:290 | warning | 'Embroker' is a possible misspelling. | PostHogBase.Spelling |
| 139:137 | warning | 'Kendal' is a possible misspelling. | PostHogBase.Spelling |
| 147:218 | warning | Use American English. Use 'maximize' instead of 'maximise'. | PostHogBase.AmericanEnglish |
| 149:36 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 151:116 | warning | 'repurpose' is a possible misspelling. | PostHogBase.Spelling |
| 151:445 | warning | Use American English. Use 'canceled' instead of 'cancelled'. | PostHogBase.AmericanEnglish |
| 179:128 | warning | Use American English. Use 'judgment' instead of 'judgement'. | PostHogBase.AmericanEnglish |
| 179:141 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 190:145 | suggestion | Prefer 'proper nouns or their/them' over 'her'. | PostHogBase.Inclusivity |
| 199:48 | warning | 'intracontinental' is a possible misspelling. | PostHogBase.Spelling |
| 218:72 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 238:131 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 240:37 | warning | Use American English. Use 'organize' instead of 'organise'. | PostHogBase.AmericanEnglish |
| 244:109 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
contents/handbook/people/onboarding.md — 46 errors, 27 warnings, 0 suggestions
| Line | Severity | Message | Rule |
|---|---|---|---|
| 11:141 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 33:308 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 33:332 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 38:67 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 46:368 | warning | 'Hogpatch' is a possible misspelling. | PostHogBase.Spelling |
| 46:629 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 54:36 | warning | 'onboardings' is a possible misspelling. | PostHogBase.Spelling |
| 58:177 | warning | 'onboardings' is a possible misspelling. | PostHogBase.Spelling |
| 61:32 | warning | 'onboardings' is a possible misspelling. | PostHogBase.Spelling |
| 63:65 | warning | Use American English. Use 'judgment' instead of 'judgement'. | PostHogBase.AmericanEnglish |
| 63:171 | warning | 'onboardings' is a possible misspelling. | PostHogBase.Spelling |
| 63:289 | warning | Use 'Brex' instead of 'brex'. | Vale.Terms |
| 65:447 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 65:465 | warning | Use American English. Use 'judgment' instead of 'judgement'. | PostHogBase.AmericanEnglish |
| 80:58 | error | 'Rules' is repeated! | Vale.Repetition |
| 107:32 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 107:55 | warning | Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. | PostHogBase.ProductNames |
| 125:39 | warning | Use American English. Use 'organize' instead of 'organise'. | PostHogBase.AmericanEnglish |
| 125:134 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 129:16 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 130:10 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 130:19 | warning | 'comms' is a possible misspelling. | PostHogBase.Spelling |
| 131:9 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 132:39 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 133:11 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 134:17 | warning | 'Deel' is a possible misspelling. | PostHogBase.Spelling |
| 134:33 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 135:13 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 136:5 | warning | 'Deel' is a possible misspelling. | PostHogBase.Spelling |
| 136:8 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 149:5 | warning | 'Ops, People & CS' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 151:14 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 152:11 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 153:10 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 153:24 | warning | Use American English. Use 'modeling' instead of 'modelling'. | PostHogBase.AmericanEnglish |
| 154:5 | warning | 'Carta' is a possible misspelling. | PostHogBase.Spelling |
| 154:9 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 155:5 | warning | 'Fondo' is a possible misspelling. | PostHogBase.Spelling |
| 155:9 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 156:5 | warning | 'Deel' is a possible misspelling. | PostHogBase.Spelling |
| 156:8 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 157:5 | warning | 'Ashby' is a possible misspelling. | PostHogBase.Spelling |
| 157:9 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 158:5 | warning | 'Micromerch' is a possible misspelling. | PostHogBase.Spelling |
| 158:14 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 162:1 | warning | Use the Oxford comma before 'and' or 'or' in a list of three or more items. | PostHogBase.OxfordComma |
| 166:59 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 168:52 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 169:46 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 170:46 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 174:252 | warning | Use 'PostHog' instead of 'Posthog'. | Vale.Terms |
| 174:300 | warning | Use the Oxford comma before 'and' or 'or' in a list of three or more items. | PostHogBase.OxfordComma |
| 178:50 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 179:58 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 180:68 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 181:68 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 185:136 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 185:171 | warning | Use American English. Use 'organizing' instead of 'organising'. | PostHogBase.AmericanEnglish |
| 187:83 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 189:61 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 189:155 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 205:15 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 214:460 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 214:533 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 218:12 | warning | 'checkin' is a possible misspelling. | PostHogBase.Spelling |
| 219:62 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 230:160 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 238:78 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 240:101 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 242:4 | warning | 'Slack Channels' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 248:15 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 249:26 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 258:17 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
rafaeelaudibert
left a comment
There was a problem hiding this comment.
I must disagree with "the least amount of money wasted" lol. I'm going to SF next week and hotels are just insane. We were planning an offsite in Central America, and I'm sure the whole week for the 3 of us would cost the same as my trip. Flights to SF are also insanely expensive; the city is literally on the edge of the Western world.
I do like the concept though :). My onboarding is London was amazing because there was just so many people to meet - all of dev, salespeople, marketing, execs, etc. - and the one where I was onboarding Fernando in Sao Paulo was not as productive.
Another thing to consider: South/Central American/African folk will have problems with the US - at least for younger people who don't really have a lot of "presence" in their home country -, but I guess London is there to solve this problem. Also, it's not really the markets where we hire the most in anyway
My actual request: can we clarify what characterizes as an exception? If we don't know what an exception is, we'll either apply it to everything or nothing, and none of those options is good
Co-authored-by: timgl <tim@posthog.com>
There was a problem hiding this comment.
One thing to consider with this change is that it turns work travel from a perk/benefit to more of a downside. People often get tired of going to the same places all the time.
I do see the benefits of defaulting to the two places where other posthoggers are.
Did something inspire this update? Have you noticed wasted travel recently?
There was a problem hiding this comment.
+1; IMO this turns something that I felt was a perk and a cool feature of working at PostHog into more of a chore.
I’m coming from a company that similarly limited Phoenix and SF as the 2 offsite locations and can confirm everyone was so over it and after a while people just ended up looking for excuses not to go (after my 6th time in Phoenix you truly can't pay me to go back there nowadays)
This makes a lot of sense for onboardings and I assumed this was already the case, but for small team offsites this feels like a downgrade/it's a shame.
I think with this change it would be worth clarifying what's the expectation in terms of what people should be getting out of their small team offsites;
I thought the whole point was more dedicated work time with your team and adjacent teams, not broad in-person collaboration. The value I got from the content/marketing/website one last year was precisely the fact we had isolated, focused, alone time to deep dive into the themes that matter to us and we barely had time to cover that over the week + hang out with each other — I don’t think trying to weave in extra face time with other people and other teams would make these necessarily more valuable or more productive in terms of moving forward our specific agendas, but maybe that's not the point/I misunderstood what these are meant to accomplish
There was a problem hiding this comment.
[In fairness I have a personal bias against this decision because for visa and general state of the world reasons I have no interest in going to the States anytime soon, and the thought of having to keep going back to SF for my offsites (which is the location that logistically would make sense for my team out of these 2 options) makes me dread them more than look forward to them lol]
There was a problem hiding this comment.
This came partly from our all-company offsite, partly from other conversations I've had. In person high bandwidth hanging out is just so good. I love being a remote company, but I think we're missing an opportunity by having onboardings or small teams go to random places with no other posthog people. The more we can get people in the same room, the more crazy ambitious ideas we'll come up with.
On offsites being 'a perk'... I get that attitude but it's also a little bit short sighted. Yes offsites should be fun, but ultimately they are a business trip, not a holiday. SF and London are cool places, and we've invested a lot in having spaces there that are nice and you want to spend time in. I think hanging out with other PostHog people makes it worth it?
There was a problem hiding this comment.
two more thoughts:
- SF in particular is just somewhere I believe everyone at PostHog should spend more time. It's the centre of one of the biggest revolutions in tech in our lifetime. hogpatch literally is in the same neighorhood as openai, and hogpatch is full of YC founders and users. The more time people spend here, the more they soak up the atmosphere, the better we'll do
- the offsite you talked about is probably one of the bigger non-all company offsite, so I get your feeling of there being a lot on. most small team offsites aren't like that and would benefit more from hanging out with others, though I believe even in a big offsite like that having other perspectives would be super valuable
There was a problem hiding this comment.
In person high bandwidth hanging out is just so good.
Oh trust me I agree, I'm all for spending more in person time with coworkers whenever possible, so much so that I'm headed to Toronto next week to work with PostHog people, and headed to London in June to work from HedgeHouse for 2 weeks, all of this on my own dime, just because of how much I believe in and enjoy/crave being in the same room with others in the company regardless of team, and do think it's worth it.
So I'm personally a huge believer in spending intentional time ad-hoc with other coworkers (and act accordingly), that's not what I'm arguing against.
My criticism is specifically on forcing the small team offsites to happen in either SF or London every single time, regardless on whether that's convenient or cost-effective for team members, which feels very weirdly rigid & I'm struggling to fully grasp the upsides; maybe if it was like "switch around, 1 year do in one of the offices, other year pick a location", but this feels like a super narrow directive for reasons I'm still struggling to comprehend
Then again I think this policy change would benefit from being appended with the new vision/goal behind small team offsites
Curious what that would mean for example for a team that is already based in one of the origin cities (i.e. London), are their offsite options to either stay in London or to fly 12 hours to SF?
Yes offsites should be fun, but ultimately they are a business trip, not a holiday.
FWIW I don't see it as a holiday either since there's zero to no free time, but before it was a business trip with something different/exciting to look forward to (for example, getting to see Lisbon through the eyes of PostHog locals was really special to me), now it's just... a corporate business trip. Which is fine, these are still cool cities and seeing people will always be nice, but it is undeniably shift towards the corporate norm and a lot less special/weird/fun in the way I've gotten to know PostHog
There was a problem hiding this comment.
I fundamentally agree with the directive here - I think it makes sense for us all to gather where most of the PostHog team is. I am probably a bit old school - I think this is work travel/this is a work place, so have no qualms with being tied down to specific locations.
BUT, I think there are real world conditions that would play a big role that may be overlooked here. I know @timgl you already added an exception for visa issues. But I also massively +1 @natalia-amorim 's point here
[In fairness I have a personal bias against this decision because for visa and general state of the world reasons I have no interest in going to the States anytime soon, and the thought of having to keep going back to SF for my offsites (which is the location that logistically would make sense for my team out of these 2 options) makes me dread them more than look forward to them lol]
I know at PostHog we don't take a stand - and that's fine. But the visa exception doesn't cover the broader 'don't want to travel to the US right now' situation a lot of people are in - I am in that boat, I just don't feel safe travelling to the US right now.
But my team's composition is going to directly collide with this directive (as I'm sure will be the case for many). Everyone in Finance except me, is now going to be based in the US - which makes me dread the travel setup. Feels like I'll have to somehow just be ok with not feeling safe and travel to the US for work (which has not been my experience at/doesn't sound like PostHog at all in my experience), or have everyone in North America fly down to London (more $$). As opposed to maybe compromising and meeting in Toronto, for instance.
When folks met up in Feb in Toronto, a whole bunch of folks showed up there - Engineering, Ops, Marketing - from Toronto/GTA/Montreal/Ottawa/the US as well. The WeWork conference room was full. +1 to @brandonleung 's point here - I think as we hire more across geographies, we have specific hubs being created with a decent chunk of folks. I think this directive can have flexibility built into it to let teams make the best decision for themselves.
Fair, and i've changed this. It's not about saving money, I think the extra expense is worth it.
I think this is a bit of a special case and def falls under the exception, partly for visa reasons and partly because of the vast distances, esp if the whole team is there. but for the majority of the team SF and London are a direct flight and no visa issues so should work
will do |
|
|
||
| We want to try to encourage small teams to get together once each year. These are more focused on work and on creating strong bonds within teams. Ideally they are spaced appropriately through the year in relation to the all-company offsite. | ||
|
|
||
| With very few exceptions, team offsites should happen at [Hogpatch](/handbook/people/hogpatch-operations) in San Francisco or the [Hedge House](#hedge-house) in London. Both are designed for it, remove most of the planning friction, and you'll always overlap with other PostHog teams — which is way more fun, and means you'll meet more people. |
There was a problem hiding this comment.
| With very few exceptions, team offsites should happen at [Hogpatch](/handbook/people/hogpatch-operations) in San Francisco or the [Hedge House](#hedge-house) in London. Both are designed for it, remove most of the planning friction, and you'll always overlap with other PostHog teams — which is way more fun, and means you'll meet more people. | |
| With very few exceptions, team offsites should happen at [Hogpatch](/handbook/people/hogpatch-operations) in San Francisco or the [Hedge House](#hedge-house) in London. Both are designed for it, remove most of the planning friction, and you'll always overlap with other PostHog teams — which is way more fun, and means you'll meet more people. | |
| If that's not practical because of visas or excessive travel time, feel free to pick another location that makes more sense. |
|
|
||
| We want to try to encourage small teams to get together once each year. These are more focused on work and on creating strong bonds within teams. Ideally they are spaced appropriately through the year in relation to the all-company offsite. | ||
|
|
||
| With very few exceptions, team offsites should happen at [Hogpatch](/handbook/people/hogpatch-operations) in San Francisco or the [Hedge House](#hedge-house) in London. Both are designed for it, remove most of the planning friction, and you'll always overlap with other PostHog teams — which is way more fun, and means you'll meet more people. |
There was a problem hiding this comment.
I like the idea of this being the default place for work travel, saves the back and forth of figuring out where we should go and allows folks to hang out with each other more often. Also, it makes sense that it's the place for onboarding.
For team offsites this is a bit annoying, as it's nice to make those something special to spend time with your team, and it being in London / SF where we'll have been 3 times already that year won't feel like that anymore.
It being expressed as a kind of mandatory with very few exceptions thing feels a bit corporate and definitely makes work travel feel like it's not a benefit as Raquel said 🤷♂️
There was a problem hiding this comment.
I do agree this feels more control than context driven initiative.
However, the net benefit from doing offsites in these places are much better, reliable working environment, cross-pollination, usually better travel links.
I do still think there is space for wider teams to do offsites in unique locations:-
- The GTM offsite
- The Marketing
- AI teams
- Data Stack
Where there is a large enough group and actually those teams needing their own space and needs etc.
However where it is a handful of people, defaulting to our hubs makes a million times more sense.
This would then make it kind of look like in a normal year of working at PostHog:-
- 1 company offsite in unique location
- 1 wider team offsite in unique location
- 1 small team offsite in SF or London or Cambridge
- other ad-hoc meetups in SF or London or Cambridge
Also the title of this PR is "Recommend" but the wording is not a recommendation, it's a directive.
Summary
why?
Test plan
#hedge-houseresolves correctly on the rendered offsites page