---
title: "Comment by Charlie from xSquads on \"A churn score nobody can explain is a churn score nobody acts on\" | Hashnode"
description: "The \"read the why lines before acting\" rule is the part most teams skip, so I'd make it mechanical. A few steps that have worked for me: Put the top factor and"
url: "https://hashnode.com/posts/a-churn-score-nobody-can-explain-is-a-churn-score-nobody-acts-on/6afb12a9882f0bab7c7c6d67/comment/6afbba82cce6bbea95ad2674"
---

[Discussion](https://hashnode.com/posts/a-churn-score-nobody-can-explain-is-a-churn-score-nobody-acts-on/6afb12a9882f0bab7c7c6d67)

Comment [A churn score nobody can explain is a churn score nobody acts on](https://hashnode.com/posts/a-churn-score-nobody-can-explain-is-a-churn-score-nobody-acts-on/6afb12a9882f0bab7c7c6d67)

[Charlie from xSquads](https://hashnode.com/@charlie-xsq)

[1d ago](https://hashnode.com/posts/a-churn-score-nobody-can-explain-is-a-churn-score-nobody-acts-on/6afb12a9882f0bab7c7c6d67/comment/6afbba82cce6bbea95ad2674)

The "read the why lines before acting" rule is the part most teams skip, so I'd make it mechanical. A few steps that have worked for me:

1.  Put the top factor and the save motion in the same row as the score, so the owner never has to open a second tab.
2.  Give each motion a named owner and a due date (CSM for exec check-in, support lead for the ticket backlog). A motion with no owner just doesn't happen.
3.  Log what was done and whether the account recovered 30 days later. After a quarter you can see which weights deserve more points.
4.  Review Watch accounts weekly, but flag any account whose score jumped 15+ points in one run, even if it's still below Critical.

That feedback loop is what turns a transparent heuristic into something a team trusts.
