Case study: Juicebox

[Lior539]

Changes

Case study for Juicebox. I was planning on merging it into @joethreepwood's PR for the AI product product, but it's not how that's going to proceed yet.

Article checklist

• I've checked the preview build of the article
• The date on the article is today's date

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
posthog	✅ Ready (Inspect)	Visit Preview	May 24, 2024 8:05am

[joethreepwood]

Reads fine. I'd like to ideally take it a step deeper and get an actionable story out of this, as that always demonstrates value the best. Can we maybe follow up with them on how they identified and solved a specific latency issue, or else tallk about a specific UX change they made as a result of the replay sessions (and the impact the change had)?

[Lior539]

Reads fine. I'd like to ideally take it a step deeper and get an actionable story out of this, as that always demonstrates value the best. Can we maybe follow up with them on how they identified and solved a specific latency issue, or else tallk about a specific UX change they made as a result of the replay sessions (and the impact the change had)?

Rereading this case study again after the offsite, I agree that it's missing a actionable insight. I rewatched the recording and its missing depth on this (this is my bad). Im not super well connected to David, so would prefer not to bother him again. I'll ship as is and keep this in mind for following case studies