[dpackard]

Definitions we use when rating savings opportunities are below.

Right now users can’t edit the difficulty but that’s helpful feedback if you think it’s something you’d use!

Would you want the ability to change difficulty to one of our fixed difficulty categories or the ability to add a custom difficulty unique to your org (e.g. custom difficulty based on internal approvals/processes at your company)?

Easy: zero downtime, zero performance risk

Medium: zero downtime, potential performance tradeoffs

Hard: downtime required, potential performance tradeoffs

[tobobo]

This seems like a fair way to split it up and would apply to a broad range of scenarios. I actually lean towards the tool being more opinionated about classifications like these- I’ve seen many tools that bog themselves down because people focus on making granular adjustments to the tool itself rather than using it to execute. A special purpose tool like this should be able to nudge me towards best practices without giving me too many opportunities for distraction!

[dpackard]

Thanks for the input. Definitely tough to balance being opinionated and guiding with best practices vs being flexible for unique company use cases and right now we're trying to "nudge" :)

We particularly wanted the "Easy" savings opportunities to be things a cloud cost owner (Head of Infrastructure or Cloud FinOps) could execute centrally without creating tickets for eng sprints. Quick wins.