It’s important that the team not get bogged down in trying to fine-tune the score too much. The score is to be used for relative prioritization and will not be perfect. A growth meeting can devolve quickly if team members squabble over a test’s impact score, for example. It’s better for the team to use the score as a valued guide, rather than the be-all and end-all for test prioritization.