-
Notifications
You must be signed in to change notification settings - Fork 4
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
Q4 2024: Comms team goals: SMEs for everyone!! #252
Comments
My only major discussion point, is with Product Analytics dwarfing the other areas, should we potentially be putting two people in to the SME role for this first? Data Warehouse has 1/7 of the tickets Product Analytics has, is it as important to have an SME here short-term versus two people on Product Analytics? |
This good stuff, @abigailbramble. Nice work! 🙌 Thoughts:
|
I love anti-goals! I think by the sounds of it we're expecting engineers to self-drive the SME stuff themselves though (which is fine) but we should clarify that.
Agree. And I'm ambivalent over the idea of having 2x people cover analytics.
I think we should also request Team Leads for prospective teams to help with this by organizing a brown bag which the SME (and others) can attend. It'll help everyone, disseminate some knowledge. I'd also strongly suggest that SMEs join Sprints, if only from a rapport POV.
I'm a little wary of this. It feels like it may slow us down and that some tickets will clearly need to go directly to an engineer on the team -- especially because there are more engineers than SMEs. If @slshults is SME for analytics, for example, than an EU escalation to him means waiting for him to come online when it could go directly to an engineer in EU (and Steven may need to escalate to an engineer anyway). One of the goals for an SME is also to spread knowledge, which I think won't happen as quickly if they become a silo for knowledge. Up to you all, but it could be that the recommended process is requesting an SME look at a ticket and make a recommendation for it. This helps the non-SME learn and if it doesn't resolve the problem then we can escalate when the SME is blocked. We definitely can escalate to an SME, but making that the go-to process at this stage feels slow - I think we'd be better off leaving this vague and encouraging each other to escalate as we think is needed.
Just a note that I agree 100% here, but long-term that won't be an issue as we grow the team, refine processes etc. I think as long as we're setting good expectations for free tickets, this is fine for now.
One thing that we should aim to have a feel for by the end of the quarter is what we next need SMEs for. We can then factor that into hiring and consider if we need a specialist or something (like you or Ben L) with explicit background in an area. |
What are we doing?
Making everyone in the team an SME!
What are we not doing?
What are the areas for SMEs?
Ares to consider:
I think we should possibly group together things that make sense.
I think that number of support tickets/area should influence our decision for where to have SMEs first. Having a look at the support tickets raised over the last 30 days:
I know that we could group product analytics and web analytics together, but I think that product analytics is already a massive area for an SME and I don't want to overload individuals.
Current areas to provide SME coverage for:
Where is all the knowledge?
What is an SME responsible for?
Immediate : gain the knowledge
Mid term : give time back to engineering
Long term : help everyone else
Consider Zendesk changes for this
How will we know we're successful?
Risks
What about future goals off the back of this?
TODO lists
(now) Abigail
(eventual) TODOs for SMEs
Please review! and helpful things for me
The text was updated successfully, but these errors were encountered: