Skip to content

Q3 2026 objectives for IRL Events team#18005

Merged
Zaltsman merged 3 commits into
masterfrom
posthog-code/irl-events-q3-2026-objectives
Jun 30, 2026
Merged

Q3 2026 objectives for IRL Events team#18005
Zaltsman merged 3 commits into
masterfrom
posthog-code/irl-events-q3-2026-objectives

Conversation

@Zaltsman

Copy link
Copy Markdown
Contributor

Changes

Replaces the IRL Events team's Q2 2026 objectives with their Q3 2026 goals on the team page. Three primary goals (signature self-driving event series, event-to-content flywheel, builder groups → curated collectives) plus sidequests for Discord, the student program, and Dreamforce. Uses the existing <details> styling and <TeamMember> linking conventions.

Why: New quarter — the team page should reflect what IRL Events is prioritizing in Q3.

Checklist

  • I've read the docs and/or content style guides.
  • Words are spelled using American English
  • Use relative URLs for internal links
  • I've checked the pages added or changed in the Vercel preview build
  • If I moved a page, I added a redirect in vercel.json

Created with PostHog from a Slack thread

Replace Q2 2026 objectives with Q3 2026 goals on the IRL Events team page.

Generated-By: PostHog Code
Task-Id: 63740115-0a12-4b2c-81bc-453a7485daab
@github-actions

github-actions Bot commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

Deploy preview

Status Details Updated (UTC)
🟢 Ready View preview Jun 30, 2026 03:13PM

@github-actions

github-actions Bot commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

Vale prose linter → found 0 errors, 5 warnings, 0 suggestions in your markdown

Full report → Copy the linter results into an LLM to batch-fix issues.

Linter being weird? Update the rules!

contents/teams/irl-events/objectives.mdx — 0 errors, 5 warnings, 0 suggestions
Line Severity Message Rule
51:3 warning 'Rebrand' is a possible misspelling. PostHogBase.Spelling
62:5 warning 'Sidequests' is a possible misspelling. PostHogBase.Spelling
64:1 warning 'Sidequests' is a possible misspelling. PostHogBase.Spelling
71:101 warning 'devs' is a possible misspelling. PostHogBase.Spelling
85:10 warning 'Dreamforce' is a possible misspelling. PostHogBase.Spelling

@github-actions

github-actions Bot commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

Bundle report

Total JS (gzip)

6.24 MiB (+23.2 KiB / +0.4%)

Largest changed named chunks
Chunk Gzip Δ vs master
component---src-pages-self-driving-index-tsx.js 9.3 KiB new
component---src-pages-terms-tsx.js 22.2 KiB +6.2 KiB / +39.2%
app.js 1977.3 KiB +3.0 KiB / +0.2%
component---src-pages-art-library-tsx.js 2.7 KiB new
component---src-pages-privacy-tsx.js 19.9 KiB +1.0 KiB / +5.5%

Eager graph (static-import closure per entrypoint)

Entrypoint Eager size Budget Modules
app 24.19 MiB (+13.9 KiB / +0.1%) report-only 5516
Largest modules in the app closure
Module Size
css ./node_modules/.pnpm/css-loader@5.2.7_webpack@5.101.3/node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[8].oneOf[1].use[1]!./node_modules/.pnpm/postcss-loader@4.3.0_postcss@8.5.6_webpack@5.101.3/node_modules/postcss-loader/dist/cjs.js??ruleSet[1].rules[8].oneOf[1].use[2]!./src/styles/global.css 713.6 KiB
./src/components/Stickers/Stickers.tsx 696.4 KiB
./.cache/caches/gatsby-plugin-mdx/mdx-scopes-dir/31a094f140f119e73085d847ae81b99b.js + 2 modules 556.7 KiB
./node_modules/.pnpm/@radix-ui+react-icons@1.3.2_react@18.3.1/node_modules/@radix-ui/react-icons/dist/react-icons.esm.js 481.4 KiB
./node_modules/.pnpm/@codemirror+view@6.38.2/node_modules/@codemirror/view/dist/index.js 458.1 KiB
./node_modules/.pnpm/rehype-raw@7.0.0/node_modules/rehype-raw/lib/index.js + 29 modules 395.1 KiB
./node_modules/.pnpm/@posthog+icons@0.36.6_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/@posthog/icons/dist/posthog-icons.cjs.js 364.8 KiB
./node_modules/.pnpm/@posthog+icons@0.36.6_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/@posthog/icons/dist/posthog-icons.es.js 354.8 KiB
./src/hooks/useCustomers.tsx + 54 modules 353.9 KiB
./node_modules/.pnpm/react-markdown@8.0.7_@types+react@16.14.66_react@18.3.1/node_modules/react-markdown/lib/react-markdown.js + 88 modules 351.4 KiB
./node_modules/.pnpm/cloudinary-core@2.14.0_lodash@4.17.21/node_modules/cloudinary-core/cloudinary-core.js 281.9 KiB
./src/components/ProductComparisonTable/index.tsx + 116 modules 267.6 KiB
./node_modules/.pnpm/@codesandbox+sandpack-react@2.20.0_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/@codesandbox/sandpack-react/dist/index.mjs 266.6 KiB
./node_modules/.pnpm/d3@7.9.0/node_modules/d3/src/index.js + 208 modules 247.4 KiB
./src/components/Pricing/PricingSlider/Slider.tsx + 87 modules 239.9 KiB

Eager-graph budgets are report-only until a baseline is established. Sizes are gzip of public/**/*.js; eager size is webpack module source bytes.

**Things we could do:**
- Test 3 formats
- Pitch our format to partners
- Curate ICP guest lists

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Is the intent there to build events around the personas?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Yes - around personas that fall into the ICP - the founders, the engineers, and non engineers all in ai-pilled cos

- Creator network
- Handhelds at hacker houses
- Footage-to-social pipeline
- Feed s*itposts

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think also just trying to get slides from each talk, and just turn each talk an engineer does into a draft blogpost may be a good idea

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

This has already started. Mine's recent blog posted started as a talk and Robbie's recent article is now a talk he's doing. So let's just make it more commonplace!

<details>
<summary>Explore live streaming</summary>
<details>
<summary>Student program</summary>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

<3

@kliment-slice kliment-slice left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

+1 on partnerships and co-hosting, refining for higher-profile organizers, more ICP data/measurement and students approach with gradual small steps

- City drop-in generates stronger local engagement than a standalone event in the same city
- Sales see positive impact from conferences
- Events are helping users learn about and try specific products
- One format clearly wins because of glowing response and partner interest

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

partner interest is keyword imo, adding also in L35 with "higher visibility"

- Lightweight moderation playbook and role system based on engagement level
**Things we could do:**
- Creator network
- Handhelds at hacker houses

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Love. A step below "backing" hacker houses since format is unclear.

**Things we could do:**
- Creator network
- Handhelds at hacker houses
- Footage-to-social pipeline

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Some involvement from @adletsmykov (e.g. twitchcon, known builders hosting etc) and @liamg-posthog here

- At least 25% of new members send 3 or more messages within their first two weeks
- We can point to at least one meaningful signal we couldn't have gotten elsewhere — a product insight, a super-user, a cross-user collaboration, or a partner co-event lead
- The team feels like it's worth continuing, not just maintaining
- Events ship content we drove and buzz from events climbs

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

As measured in 1) impressions and social tags, 2) geo signups, 3) geo long term usage.

@Zaltsman Zaltsman marked this pull request as ready for review June 30, 2026 23:15
@Zaltsman Zaltsman merged commit 315be77 into master Jun 30, 2026
23 checks passed
@Zaltsman Zaltsman deleted the posthog-code/irl-events-q3-2026-objectives branch June 30, 2026 23:16
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.

3 participants