Hello! does anyone have any guidance or scaffolding around SLAs for fulfilling advocacy requests. We're struggling right now with various teams throwing a ton of requests at us with tight timelines that they feel are ALL high priority. It's less of an issue from sales re reference calls etc and more so from marketing/PR/comms who seem to be juggling a ton of competing priorities and it's all rolling down hill, but would be helpful if anyone has set SLAs for various activity/advocate requests!
We're trying to set some documented boundaries and expectations about how much lead time they need to be giving us for some of these requests (speakers for webinars/panels, quotes, permission for media mentions from higher profile customers, etc.)
Hi , I'm working on my ChatGPT skills (plus my own knowledge).
Here's the chat I just made: https://chatgpt.com/share/670fe2e9-86b8-800c-a6a5-bfa0069f9ce4
Here's a slide from when she shared her reference program.
https://cma-weekly.pory.app/slides/record/recQo1Dx1RQnAiYUB?sId=IMGapecrufny
And, finally, here's a very loose SLA I put together for working with product when I was at Demandbase. https://docs.google.com/document/d/1O6UfVShvDsPM3nDTARnnUv7pj7no8QSqEk7oFPhCuTE/edit?usp=sharing
I also suggest making a place where they can track the requests as well. Such as in this template I share. https://docs.google.com/spreadsheets/d/1PTBCRdu5hxG6JqC5lOkeIeNPfn1fYiGNNZLTv7CflT4/edit?gid=1055194068#gid=1055194068
A little late to respond I suppose, and you’ve probably already arrived at this conclusion on your own, but I would suggest looking at a couple of examples of recent stories you’ve created and working backwards about how long it took you to get through the story development from start to finish and note the differences. For example, if someone is requesting a reference for a product that hasn’t even launched yet and there’s no beta (personal favorite 😏 ) vs a reference that squarely lines up with a popular use case/solution etc (bread & butter). Maybe create some tiering based on business segments, solutions, and types of requests.
Another idea is to ask requesters to show what the business impact is so you can help prioritize and have a sanity check. If your team is hyper focused on 3specific products or company goals, for example, creat SLAs for requests that are in line with them and an explanation for timeframes for requests outside of those.
I love working cross functionally - it’s one of the best parts about advocacy but it’s easy to get drained by the volume and urgency!
