Finding the right balance for the Impact Score

Question

I'm trying to find the right formula for the Impact Score.

I'm considering Business Value, Customer value and Strategic fit as positive factors. I want to include Effort as a negative, but I'm finding it has too much impact on the result.

It's not easy to determine the impact on the formula of the negative factor, but I understand that there are 4 criteria, 3 positive and one negative. The negative one is affecting 1/4th of the weight.

I'd like to soften the negative impact of the Effort, and doing some research, I found some options like the square root of the effort multiplied by 7, but they are not allowed as it just allows me to add a negative factor with 100% value.

I've tested adding another negative factor such as Technical complexity to soften the negative impact of the Effort, but the results penalise the positive factors even more.

What can I do to lower the impact of the Effort as a  negative factor?

Thanks for the help

Hermance NDounga · Answer

Hello Andres,

sqrt isn't a function supported by Jira Product Discovery as per Formula documentation

I'm not sure how you mesure the effort today (which field type you're using). But technically you can simply create options and weight them.  
. 
The square root won't be perfect because it doesn't support commas, but you'll have a functionning formula.

Best Regards,
Hermance
Product Manager @ Jira Product Discovery

James Conway_bjz829 · Answer

i had a similar challenge, and got around it by squaring my important term.

For prioritising assumptions, I have

({Importance}*{Importance})/({Evidence}*{Effort})

So perhaps you could multiple Business Value, Customer Value and Strategic Fit and then Divide by Effort?

Or you follow Sean Ellis guidance on ICE (Impact Confidence Ease) prioritisation where he models effort from 10 easy to 1 hard (rather than effort high hard, low easy)

Bill Sheboy · Answer

Thank you for that information.  Without that function in the custom formulas, I believe an automation rule is the only workaround.