mirror of
https://github.com/BillyOutlast/posthog.com.git
synced 2026-02-04 03:11:21 +01:00
Update community incubator, events page and add handbook links (#12445)
Co-authored-by: Ian Vanagas <34755028+ivanagas@users.noreply.github.com>
This commit is contained in:
Daniel Z
@@ -24,11 +24,11 @@ import CloudinaryImage from 'components/CloudinaryImage'
|
||||
|
||||
|
||||
<p className="text-lg lg:text-xl mt-4 mb-4">
|
||||
Want to start a co-working community of builders in your city? We're launching a pilot program in emerging tech hubs across the UK, EU, and North America and are looking for builders who want to be the first chapters we invest in.
|
||||
Want to start a co-working community of builders in your city? We're looking for builders who want to build a community we'll invest in. We've already successfully kicked off in <Link to="https://github.com/PostHog/meta/issues/327#issuecomment-3067453536">Austin</Link>, <Link to="https://github.com/PostHog/meta/issues/331#issuecomment-3119258647">Barcelona</Link>, and <Link to="https://github.com/PostHog/meta/issues/336#issuecomment-3097106340">NYC</Link>.
|
||||
</p>
|
||||
|
||||
<a href="#apply" className="inline-block mb-10">
|
||||
<CallToAction to="#apply" type="primary">Apply to lead a chapter</CallToAction>
|
||||
<CallToAction to="#apply" type="primary">Apply to start a chapter</CallToAction>
|
||||
</a>
|
||||
|
||||
</div>
|
||||
@@ -42,19 +42,19 @@ import CloudinaryImage from 'components/CloudinaryImage'
|
||||
<li className="bg-accent dark:bg-accent-dark relative md:max-w-md py-4 md:py-8 pl-4 pr-2 md:px-12 lg:px-8 rounded-2xl shadow-sm transition-colors duration-300">
|
||||
<h5 className="text-xl font-extrabold !m-0 pb-1 pr-4 text-black dark:text-white">$800 cash grant</h5>
|
||||
<p className="m-0 text-[15px] text-gray-800 dark:text-gray-300">
|
||||
Meant to get you going and to be used at organizer's discretion. It's main purpose is to encourage you to get started. We'll also send merch.
|
||||
This will get you going and is to be used at the organizer's discretion. You can use it for food, coffees, or an activity. We'll also send merch.
|
||||
</p>
|
||||
</li>
|
||||
<li className="bg-accent dark:bg-accent-dark relative md:max-w-md py-4 md:py-8 pl-4 pr-2 md:px-12 lg:px-8 rounded-2xl shadow-sm transition-colors duration-300">
|
||||
<h5 className="text-xl font-extrabold !m-0 pb-1 pr-4 text-black dark:text-white">Help attracting attendees</h5>
|
||||
<p className="m-0 text-[15px] text-gray-800 dark:text-gray-300">
|
||||
The people you gather are the sparks of your community. We'll help you find the builders we'd work alongside any day.
|
||||
The people you gather are the sparks of your community. We'll help you find the builders we'd be glad to work alongside on any day.
|
||||
</p>
|
||||
</li>
|
||||
<li className="bg-accent dark:bg-accent-dark relative md:max-w-md py-4 md:py-8 pl-4 pr-2 md:px-12 lg:px-8 rounded-2xl shadow-sm transition-colors duration-300">
|
||||
<h5 className="text-xl font-extrabold !m-0 pb-1 pr-4 text-black dark:text-white">Help finding a venue</h5>
|
||||
<p className="m-0 text-[15px] text-gray-800 dark:text-gray-300">
|
||||
We've been remote working in coffee shops and co-working spaces for four years. We can help you find a great spot for your team.
|
||||
We've been remote working in coffee shops and co-working spaces for four years. We can help you find a space for your group.
|
||||
</p>
|
||||
</li>
|
||||
</ul>
|
||||
@@ -63,9 +63,9 @@ import CloudinaryImage from 'components/CloudinaryImage'
|
||||
|
||||
<div className="grid md:grid-cols-2 gap-8 items-start mt-6">
|
||||
<div>
|
||||
<h2 className="text-3xl lg:text-4xl mb-6">What we're asking from you, pilot participants</h2>
|
||||
<h2 className="text-3xl lg:text-4xl mb-6">What we're asking from incubator organizers</h2>
|
||||
<p>
|
||||
Bring together a group of at least 6 people to co-work and build for 4 straight weeks. The goal is to give you the initial push but let you carry forward afterwards. If the group continues and grows, we're going to highlight it in our community.
|
||||
Bring together a group of at least 6 people to co-work and build for 4 sessions. The goal is to give you the initial push but let you carry forward afterwards. If the group continues and grows, we're going to highlight it in our community.
|
||||
</p>
|
||||
<p>
|
||||
Create a consistent time and structure that works for your group. For times, do evenings or weekends. For format, we suggest two ingredients: building and demo-ing.
|
||||
@@ -76,7 +76,7 @@ import CloudinaryImage from 'components/CloudinaryImage'
|
||||
</div>
|
||||
<div className="relative">
|
||||
<div className="border-8 border-white shadow-xl rounded relative rotate-1">
|
||||
<CloudinaryImage
|
||||
<img
|
||||
src="https://res.cloudinary.com/dmukukwp6/image/upload/cambridge_9a4e27f42e"
|
||||
alt="Builder community in action"
|
||||
className="w-full"
|
||||
@@ -88,6 +88,58 @@ import CloudinaryImage from 'components/CloudinaryImage'
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div className="mt-6">
|
||||
<div className="text-center max-w-4xl mx-auto mb-12">
|
||||
<h2 className="text-3xl lg:text-4xl mb-6">It all starts with you, the (visionary) organizer</h2>
|
||||
<div className="space-y-4 text-lg">
|
||||
<p>
|
||||
One thing that's clear from the community incubators already in motion is that the organizer sets the tone. They come from different backgrounds (founders, engineering, product) but all have a clear vision for and desire to make an impact locally.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div className="grid grid-cols-1 md:grid-cols-3 gap-6 max-w-6xl mx-auto">
|
||||
<div className="relative">
|
||||
<div className="border-8 border-white shadow-xl rounded relative rotate-1">
|
||||
<img
|
||||
src="https://res.cloudinary.com/dmukukwp6/image/upload/Austin_community_incubator_photo_1049a2853e.png"
|
||||
alt="Austin community incubator"
|
||||
className="w-full"
|
||||
/>
|
||||
<div className="absolute bottom-0 left-0 w-full text-white bg-gradient-to-b from-black/0 to-black/50 p-2 pt-8 text-sm">
|
||||
<Link to="https://www.linkedin.com/in/kliment-minchev-a1847160/">Kliment</Link> leading community incubator, Austin
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div className="relative">
|
||||
<div className="border-8 border-white shadow-xl rounded relative -rotate-1">
|
||||
<img
|
||||
src="https://res.cloudinary.com/dmukukwp6/image/upload/NYC_community_incubator_photo_57f844e7c4.jpeg"
|
||||
alt="NYC community incubator"
|
||||
className="w-full"
|
||||
/>
|
||||
<div className="absolute bottom-0 left-0 w-full text-white bg-gradient-to-b from-black/0 to-black/50 p-2 pt-8 text-sm">
|
||||
<Link to="https://www.linkedin.com/in/garrettawolfe/">Garrett</Link> and <Link to="https://linkedin.com/in/mitchbregs/">Mitch</Link> with community incubator, NYC
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div className="relative">
|
||||
<div className="border-8 border-white shadow-xl rounded relative rotate-1">
|
||||
<img
|
||||
src="https://res.cloudinary.com/dmukukwp6/image/upload/Barcelona_community_incubator_photo_bc90b36bbe.png"
|
||||
alt="Barcelona community incubator"
|
||||
className="w-full"
|
||||
/>
|
||||
<div className="absolute bottom-0 left-0 w-full text-white bg-gradient-to-b from-black/0 to-black/50 p-2 pt-8 text-sm">
|
||||
Barcelona community incubator by <Link to="https://www.linkedin.com/in/guillem-tarraga/">Guillem</Link> and <Link to="https://www.linkedin.com/in/jesauraoller/">Jose</Link>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<section id="apply" className="pt-6 md:pt-12">
|
||||
<div className="max-w-screen-md mx-auto">
|
||||
<h2 className="text-3xl lg:text-4xl text-center mb-8">Apply to lead a chapter</h2>
|
||||
@@ -106,27 +158,27 @@ import CloudinaryImage from 'components/CloudinaryImage'
|
||||
|
||||
<details>
|
||||
<summary>Who is eligible to attend?</summary>
|
||||
<p>Individuals or small teams who want to build products.</p>
|
||||
<p>Individuals or small teams who are already or want to build products.</p>
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>What if more than one person applies from the same city?</summary>
|
||||
<p>For the pilot program we'll only select one based on your application and past experience. We'll connect you with other applicants from the same city.</p>
|
||||
<p>If it's a major city (population of 1 million or more), that's not a problem. If it's a smaller city, we'll connect you with other applicants from the same city.</p>
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>What happens after 4 weeks?</summary>
|
||||
<p>You've now bootstrapped a community, keep it going. If you didn't get the traction required to keep it going, we'll mourn then move on.</p>
|
||||
<summary>What happens after 4 sessions?</summary>
|
||||
<p>You've now bootstrapped a community, keep it going. If you didn't get the traction required to keep it going, let's learn about what happened and iterate for the next one.</p>
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>What level of support do I get?</summary>
|
||||
<p>We're looking for organizers who can drive this builder community with limited support from us. Still, we'll be here to help along the way.</p>
|
||||
<p>We're looking for organizers who can drive this builder community with limited support from us. Venue? Participants? Promotion? This is up to you. Still, we'll be here to help along the way. We also have existing community organizers who can serve as inspiration.</p>
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>What's in it for us?</summary>
|
||||
<p>We are excited about helping to bootstrap communities of builders around the world. That's what we're in it for. No one needs to use PostHog as part of this.</p>
|
||||
<p>We are excited about helping to bootstrap communities of builders around the world. That's what we're in it for. No one needs to use PostHog as part of this initiative.</p>
|
||||
</details>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -3,21 +3,27 @@ title: Events
|
||||
sidebar: Handbook
|
||||
showTitle: true
|
||||
---
|
||||
> If you want to build a local network of builders, go to [Community incubator](#community-incubator). If you’re planning an event and want support or promotion from the PostHog team, go to [Community events](#community-events)
|
||||
> If you want to build a local group of builders, go to [Community incubator](#community-incubator). If you’re planning an event and want PostHog to be involved, go to [Community events](#community-events)
|
||||
|
||||
We’re [100% remote](handbook/company/culture) and set up to work asynchronously–but there's a real benefit in getting together in real life (and our best ideas come from [working together](handbook/company/offsites)).
|
||||
We’re [100% remote](/handbook/company/culture) and set up to work asynchronously–but there's a real benefit in getting together in real life. Still, we’re figuring out how to do events "the PostHog way."
|
||||
|
||||
Still, we’re figuring out how to do events "the PostHog way." We prefer not to be a small fish in a big pond, so we pass on big conferences. We [prefer pull](handbook/growth/marketing#2-pull-dont-push) over push, so we avoid formats like webinars, dinners, and lunch & learns.
|
||||
For us to be involved the event has to be relevant to our [ICP](/handbook/who-we-are-building-for). We prefer not to be a small fish in a big pond, so we pass on big conferences. We [prefer pull](/handbook/growth/marketing#2-pull-dont-push) over push, so we avoid booths, badge-scanning, buying attendee lists, paying to speak, webinars, and dinners.
|
||||
|
||||
To get us to perk up with curiosity, at least one of these desired event criteria gets met:
|
||||
The event formats we get involved in (and organize ourselves) fall into one of these:
|
||||
|
||||
- Hands-on gatherings that help our customers build faster and better for their customers
|
||||
- Experiences that allow engineers and founders to flex their product muscles
|
||||
- When [product engineers](blog/what-is-a-product-engineer) get together to identify problems and build solutions for users
|
||||
- Experiences that allow engineers and founders to flex and grow their skillset
|
||||
- Getting [product engineers](/blog/what-is-a-product-engineer) together to identify problems and build solutions for users
|
||||
- AFK time such as a fun activity, some sightseeing, or just spending time together
|
||||
|
||||
## Community incubator
|
||||
|
||||
Our effort to activate and connect builders around the world by helping them incubate micro-communities that gather for weekly co-working sessions. As we know from our own sprints, offsites, and hackathons, we can build a whole lot when we gather in person. We believe this format can make a higher impact to communities of builders because of the velocity built over weeks of communal work and collaboration.
|
||||
Where we connect builders around the world by helping them incubate micro-communities that gather for weekly co-working sessions. As we know from our own sprints, offsites, and hackathons, we can build a whole lot when we gather in person.
|
||||
|
||||
We have already seen how this format makes a higher impact on communities of builders because of the velocity built over weeks of communal work, collaboration, and creativity.
|
||||
|
||||
|
||||
<Caption>Kliment leading community incubator, Austin</Caption>
|
||||
|
||||
### Geographies
|
||||
|
||||
@@ -25,9 +31,9 @@ The [pilot program](/community-incubator) is starting in tech hubs in North Amer
|
||||
|
||||
### Co-working structure
|
||||
|
||||
The focus is on recurring weekly gatherings with small groups of 10-20 people.
|
||||
The focus is on recurring weekly gatherings with small groups of ~10 people.
|
||||
|
||||
Gatherings can take place during weekday evenings or weekends and go for about 3 hours. A suggested format is to have at least 2-2.5 hours for working and 0.5-1 hours for welcomes and demos. Outside co-working, the group is encouraged to take part in an activity such as a walk, a bike ride, a hike, or a trip to the climbing gym. Preferably, this is outdoors.
|
||||
Gatherings can take place during weekday evenings or weekends and go for about 3 hours. A suggested format is to have time for intros, at least 2-2.5 hours for working, and demos to close. Outside co-working, the group is encouraged to get together for an AFK activity such as a walk, bike ride, hike, or local sightseeing.
|
||||
|
||||
### Venues
|
||||
|
||||
@@ -35,21 +41,21 @@ The [pilot program](/community-incubator) is starting in tech hubs in North Amer
|
||||
|
||||
## Community events
|
||||
|
||||
People often underestimate the power and potential within their teams and ecosystems. Community events are in real life (IRL) manifestations of [our mission](handbook/why-does-posthog-exist#our-mission) organized by enthusiastic customers. They take place when someone has identified a gap or opportunity where an event helps people move [faster](newsletter/this-is-why-youre-not-shipping), smarter, and more together.
|
||||
Community events are in real life (IRL) manifestations of [our mission](/handbook/why-does-posthog-exist#our-mission) organized by enthusiastic partners and customers. They usually originate when someone has identified an interesting topic for an event to help people move [faster](/newsletter/this-is-why-youre-not-shipping), smarter, and more together.
|
||||
|
||||
We avoid limiting event potential, so we don’t have a template to follow. With that said, some considerations:
|
||||
If you have a topic or gap you've identified but are unsure of format, here are some ideas:
|
||||
|
||||
- **Structure:** participatory > nonparticipatory, bottoms-up > top down. unconference > conference.
|
||||
- **Curation:** Get the right mix of people to the event. Prioritise this alongside the content. This extends to speakers, co-hosts, and attendees.
|
||||
- **Atmosphere** foster a [welcoming environment](handbook/company/grown-ups#things-we-do-to-create-a-welcoming-environment) where everyone can succeed.
|
||||
- **Structure:** participatory > nonparticipatory, bottoms-up > top down, unconference > conference, demos > pitches.
|
||||
- **Curation:** Get fewer people but the right people to the event. Prioritise this alongside the content. This extends to speakers, co-hosts, and attendees.
|
||||
- **Atmosphere** foster a [welcoming environment](/handbook/company/grown-ups#things-we-do-to-create-a-welcoming-environment) where everyone can succeed.
|
||||
|
||||
In our high trust environment, we expect organizers who initiate events to fully own them.
|
||||
|
||||
What community events are **not** for:
|
||||
|
||||
- Forcing PostHog or any other product into conversations with people
|
||||
- Watching or planning things rather than doing them (Workshops > Fireside Chats)
|
||||
- Networking
|
||||
- Watching or planning things rather than doing them
|
||||
- Just networking for the sake of chit chat
|
||||
|
||||
### Formulating a purpose and structure
|
||||
|
||||
@@ -57,31 +63,23 @@ An impactful event follows the principles of user-driven development which stems
|
||||
|
||||
> We use GitHub for everything at PostHog. When you’re ready to organize an event, create a GitHub issue [using this template](https://github.com/PostHog/meta/issues/new?template=event-plan.md) and assign it to Daniel Zaltsman. Prioritize progress (on which you can build) over perfection.
|
||||
|
||||
Put real effort into this first step. Defining the "what, why and how" of an event beforehand will pay off on event day. Let our [shared values](handbook/values) guide you. Don’t submit until your answer to “Would I attend this?” is a clear “yes.”
|
||||
|
||||
For an event to meet the high bar of quality for our work, we’ve provided considerations for ways to make it achieve its purpose within the GitHub issue template.
|
||||
Put real effort into this first step. Defining the "what, why and how" of an event beforehand will pay off on event day. Let our [shared values](/handbook/values) guide you. Don’t submit until your answer to “Would I attend this?” is a clear “yes.”
|
||||
|
||||
### Getting support
|
||||
|
||||
We support community events led by proactive organizers with a bias for action.
|
||||
We support community events in a handful of ways.
|
||||
|
||||
**Speakers:** We don’t review speaker lists—that’s up to organizers. We suggest avoiding:
|
||||
**Speakers:** Want a speaker in our ecosystem (team PostHog, customers, partners)? We’ll try our best. When considering speakers, avoid:
|
||||
|
||||
- Loudest person pretending to who know more than they do
|
||||
- Corporate speak aficionados spewing tedious enterprise marketing nonsense
|
||||
- People LARPing (live action role-playing) as executives
|
||||
- Loudest person pretending to know more than they do
|
||||
|
||||
Want a speaker in our ecosystem (team PostHog, customers, partners)? We’ll try our best.
|
||||
**Content:** If your speaker(s) are unsure of what to talk about, consider going back to the purpose of the event. Otherwise, [we](founders) [have](founders/product-market-fit-game) [plenty](handbook) [of](about) [material](https://newsletter.posthog.com/) [for](https://www.youtube.com/channel/UCn4mJ4kK5KVSvozJre645LA) [your](questions) [inspiration](docs).
|
||||
|
||||
**Content:** If your speaker(s) are unsure of what to talk about consider going back to the formulating purpose step. Otherwise, [we](founders) [have](founders/product-market-fit-game) [plenty](handbook) [of](about) [material](https://newsletter.posthog.com/) [for](https://www.youtube.com/channel/UCn4mJ4kK5KVSvozJre645LA) [your](questions) [inspiration](docs).
|
||||
**Merch:** We use the [store merch processes](/handbook/company/merch-store) to handle distribution of PostHog-branded merch. We tend to be generous with merch for community events. Outline what you had in mind in the issue.
|
||||
|
||||
**Merch:** We use the [store](merch) [processes](handbook/company/merch-store) to handle distribution of PostHog-branded merch. We may be generous with merch for community events. Outline what you had in mind in the issue.
|
||||
|
||||
**Co-promotion:** Most of the time the help requested is in the form of promotion. As a general rule, we don't promote events we aren't supporting or co-hosting ourselves. We decide when to repost community events on our social media channels on a case by case basis. To boost your chances of co-promotion:
|
||||
|
||||
- Words are spelled (correctly) using American English and you’ve tagged PostHog
|
||||
- It includes a link to the event page, which includes an agenda and relevant information
|
||||
- There is some form of multimedia: meta image, image, gif, or video
|
||||
**Co-promotion:** Most of the time the help requested is in the form of promotion. As a general rule, we don't promote events we aren't supporting or co-hosting ourselves. We decide when to repost community events on our social media channels and email on a case by case basis.
|
||||
|
||||
**Venue and catering:** Identify the vendors and costs and include them in the GitHub issue. If the event will not be possible without monetary support, make that clear. We may support the cost of venue, food, or beverages but require the paper napkin math.
|
||||
|
||||
@@ -89,20 +87,21 @@ Want a speaker in our ecosystem (team PostHog, customers, partners)? We’ll try
|
||||
|
||||
### Branding it
|
||||
|
||||
Our brand is a reflection of us and [how we’re experienced by others](blog/brand), including events.
|
||||
Our brand is a reflection of us and [how we’re experienced by others](/blog/brand), including events.
|
||||
|
||||
**Words:** For our customers to have a clear sense of our involvement in community events, avoid including PostHog in the title. The same goes for referring to it as a “PostHog Event/Meetup/Gathering” with or without the word "Official." Accepted alternatives are "PostHog-supported," “with support from the PostHog team,” or “with PostHog’s support.”
|
||||
**Words:** Naming products is hard. Same goes for naming events. As a prerequisite, read our primer on [writing for developers](/founders/writing-for-developers). Try your best to come up with event names that communicate the 'what?' and will attract the 'who?' And again, ask yourself if you would be interested in this event based on the title.
|
||||
|
||||
**Pictures:** Every event is improved with a flyer or poster that showcases the essence of the experience. We keep a comprehensive list of brand assets and guidelines for their use on the dedicated [brand assets page](handbook/company/brand-assets). Share your assets and we’ll give feedback. Depending on the scale and timing of the event, our team may be able to help with branding as well.
|
||||
**Pictures:** Every event is improved with a flyer or poster that showcases the essence of the experience. We keep a comprehensive list of brand assets and guidelines on the [brand assets page](/handbook/company/brand-assets). Share your assets and we’ll give feedback. Depending on the scale and timing of the event, our team may be able to help with branding as well.
|
||||
|
||||
### Follow-ups
|
||||
|
||||
Community events are better when organizers share what happened and any follow-up actions.
|
||||
|
||||
[We value feedback](handbook/people/feedback) and expect the same from event organizers. A great event will speak for itself but sometimes an event will miss the mark, too. Either way, we want to hear how it went and value organizers who learn from the experience.
|
||||
|
||||
In addition to what you learned and feedback from attendees, we will share any photos, videos, quotes, data points with our team.
|
||||
Community events are better when organizers share what happened, what you learned, and any follow-up actions. [We value feedback](/handbook/people/feedback) and expect the same from event organizers. In addition to what you learned and feedback from attendees, we will share any photos, videos, quotes, data points with our team.
|
||||
|
||||
## Sponsoring external events
|
||||
|
||||
We sometimes get asked by other companies or people if we are interested in sponsoring their events - these can range from small to extremely large. We don't do these at the moment because they are a poor return on investment, though we always encourage team members to speak at these if there is an opportunity to, and we can support you with budget, social posts, merch etc. Ask in the #team-brand-and-vibes channel.
|
||||
We sometimes get asked by other companies or people if we are interested in sponsoring their events - these can range from small to extremely large. We don't do these at the moment because they are a poor return on investment, though we always encourage team members to speak at these if there is an opportunity to, and we can support you with budget, social posts, merch etc. Ask in the [#team-brand-vibes](https://posthog.slack.com/archives/C01V9AT7DK4) channel.
|
||||
|
||||
## Sponsoring student organizations
|
||||
|
||||
Sometimes students at varying universities ask us if we are interested in sponsoring their career fairs, hackathons, or other student-led initiatives. We don't currently participate in these. Although we don't use specific years of experience as a qualifier for hiring, we rarely hire students straight out of school. If there is a custom partnership you have in mind or it involves an existing employee's alma-mater, ask in the [#team-brand-vibes](https://posthog.slack.com/archives/C01V9AT7DK4) channel.
|
||||
|
||||
|
||||
@@ -376,7 +376,7 @@ You can often refer to the source of existing pages for more examples, but if in
|
||||
|
||||
#### Images/GIFs
|
||||
|
||||
If you need to upload images, you can upload them to Cloudinary
|
||||
If you need to upload images, you can [upload them to Cloudinary](/handbook/engineering/posthog-com/assets)
|
||||
|
||||
To include an image in a markdown file, you can use Cloudinary URLs, like so:
|
||||
|
||||
|
||||
@@ -23,7 +23,7 @@ template: team
|
||||
### Build a community of superfans (Daniel)
|
||||
- **Rationale:** More fans = More word of mouth
|
||||
- **Things we could do:** Encourage community chapters. Events for startups. Engineers at conferences.
|
||||
- **Planning issue:** Coming soon?
|
||||
- **Planning issue:** [Here!](https://github.com/PostHog/meta/issues/345)
|
||||
- **We'll know we're successful when:** We’ve got good community chapters and 100+ superfans.
|
||||
|
||||
### Nail the new positioning (Joe)
|
||||
|
||||
Reference in New Issue
Block a user