#7-case-studies-stories

I usually start by looking at the age of the case study. Anything over two years old is a good candidate for review, or at least worth checking to see whether it could be refreshed.

I also consider whether the person featured in the case study is still with the organization, if they’ve moved on, it can be a good opportunity to revisit and update the use case with a new contact.

Another key factor is product accuracy. If the features highlighted in the case study have evolved significantly or been sunset, that’s a strong signal that the content may no longer reflect the current experience and could be a good candidate to refresh.

In the past when I have followed those buckets, it helped me build a solid list of case studies that need attention. From there, you can line it up with your current priorities and content gaps to figure out what to prioritize.

<@U08MBG24LRM> Makes sense, thanks! What's your criteria to remove a case study from your web? What would make you take down a case study?

Perfect answer from Paola 🙂 Good times to remove a case study: When a customer has churned (obvious but should be noted); if the solution they're talking about is really outdated and product names have changed so drastically the story is no longer relevant; if a customer asks you to remove the story due to a satisfaction issue, etc. That's my 2 cents. I've definitely made cases to keep stories older than 2 years because the story is still relevant and we don't have a newer one that is able to properly replace the older one. But an annual audit is a great way to identify opportunities for refreshing stories or what your story gaps are. I'll also note, even when a customers who was quoted in a story has moved onto a new company, I've reached out to other contacts to ask if they'd like to either provide us with an updated quote from someone else or simply re-attribute the quote to another person. Hope that helps!

@Sarah McCoy Thank you! It definitely helps and I'm glad you mentioned churn should be an obvious reason to pull a case study but I've gotten some unexpected pushback on that recently so wanted to see if I needed a reality check lol

Agree with all of the responses above. I generally try to perform a review cadence at least 2-3 times a year. Mostly to spot check if customers featured in case studies are still active and if older case studies just don't pass the eye test (older / sunset products, date case studies were originally published exceeds 3 years). If Case Studies are older than 3 years, sometimes I'll just shoot a note to the customer's account team to see if there's an evolution story that we can tell to update the case study and keep it fresh so that we can keep the case study up as opposed to taking it down.

Our process is basically identical to <@U09NPSSPHST>'s.