-
Notifications
You must be signed in to change notification settings - Fork 474
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
Team Comms - Q4 Goals #9459
Merged
Merged
Team Comms - Q4 Goals #9459
Changes from 4 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
7f52e8a
Q4 plans
joethreepwood ec529bf
Update contents/teams/customer-comms/objectives.mdx
joethreepwood 9fd0bcd
Update contents/teams/customer-comms/objectives.mdx
joethreepwood 312afcd
Update contents/teams/customer-comms/objectives.mdx
joethreepwood 8888b51
Update contents/teams/customer-comms/objectives.mdx
joethreepwood File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,31 +1,34 @@ | ||
Make sure customers have the information they need to be successful with PostHog and deliver it in a way which sparks joy. | ||
|
||
### Hit our expanded SLAs while keeping CSAT stable (Marcus + Steven) | ||
- **Rationale:** Reliable support = Good support. | ||
- **What we'll ship:** Grow the team, train other teams. | ||
- **We'll know we're successful when:** 80% SLA achievement or above for _all_ Normal and High priority tickets. CSAT average does not fall below 4.1 (4.6 at start of Q3). | ||
|
||
### Level up our processes and automations (Steven) | ||
- **Rationale:** Good processes = Fewer tickets, happier users. | ||
- **What we'll ship:** Zendesk improvements ([domain problem](https://github.com/PostHog/meta/issues/201), [bounced emails](https://github.com/PostHog/company-internal/issues/1324) etc.), MaxAI v2, handbook definitions (incl. definitions of what we don't support), team tracking. | ||
- **We'll know we're successful when:** MaxAI v2 feels worth keeping and incoming tickets aren't getting out of control. | ||
|
||
### Make sure we have successful launches for new products (Joe) | ||
### Improve our SLA achievement without causing a CSAT catastrophe (Ben & Ben) | ||
- **Rationale:** Business as usual = A good start | ||
- **What we'll ship:** Issue coming soon | ||
- **We'll know we're successful when:** We're regularly hitting 90% SLA achievement for Normal+ prio tickets. CSAT doesn't fall below 80%. | ||
|
||
### Make everyone a subject matter expert as part of their onboarding (Abigail) | ||
- **Rationale:** More experts = fewer escalations | ||
- **What we'll ship:** Issue coming soon | ||
- **We'll know we're successful when:** Everyone is an expert in something and we have a playbook for learning when we hire next. | ||
|
||
### Support users outside of Zendesk (Steven) | ||
- **Rationale:** Other communities = good word of mouth | ||
- **What we'll ship:** Issue coming soon | ||
- **We'll know we're successful when:** We know if a community focus is worth it and we more regularly see users helping each other. | ||
|
||
### Centralize and improve all email comms (Joe) | ||
- **Rationale:** Better processes = Easier messaging beta | ||
- **What we'll ship:** [See issue.](https://github.com/PostHog/meta/issues/243) | ||
- **We'll know we're successful when:** We have all emails coming from C.io, campaign metrics generally improve, messaging beta goes well. | ||
|
||
### Make sure our upcoming betas and product launches are successful (Joe) | ||
- **Rationale:** More products = More revenue. | ||
- **What we'll ship:** [See issue](https://github.com/PostHog/meta/issues/215). | ||
- **We'll know we're successful when:** We're successfully completing all launch plans. | ||
|
||
### Continue supporting CS & Sales (Joe) | ||
- **Rationale:** There's a lot of things still left to do. | ||
- **What we'll ship:** [See issue](https://github.com/PostHog/meta/issues/215). | ||
- **We'll know we're successful when:** We're effectively processing deals of all sizes and up/cross-selling users into new features. | ||
|
||
### Onboard community manager (Joe) | ||
- **Rationale:** More WOM = More growth | ||
- **What we'll ship:** [See issue](https://github.com/PostHog/meta/issues/215). | ||
- **We'll know we're successful when:** They've found two influencers we can work with successfully. | ||
- **What we'll ship:** [See issue.](https://github.com/PostHog/meta/issues/243) | ||
- **We'll know we're successful when:** We're successfully completing all launch plans and are getting enough users in each beta. | ||
|
||
## Side quests | ||
- Run another YC S24 campaign, but with less direct work (Joe) | ||
- Run another YC F24 campaign, but with _even_ less direct work (Joe) | ||
- Continue supporting CS & Sales with everything they need to sell (Joe) | ||
joethreepwood marked this conversation as resolved.
Show resolved
Hide resolved
|
||
- Onboard a new product marketing manager to increase bandwidth (Joe) | ||
- Ship Max AI and track reduction in the overall ticket volume (Steven) | ||
|
||
|
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is worth doing but I don't think needs to be a specific goal unless you have particular tasks/projects in mind?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For F24, I at least want to do the Supergroup stuff.
For CS, mainly it'll be case studies -- Cam has been asking for non-technical ones, so I'm at least going to look at that.
No strong feelings on having them on here or not. It'll go on my Q4 planning issue regardless.