I'm a big fan of both aiming to deliver value (by having a value hypothesis for each new thing) and making sure we're delivering value. But actually quantifying it can be tricky. Do you mainly use value proxies here? E.g., X people are using the feature Y times per week?
I read "quantify" a little ambiguously, possibly because I'm projecting.
For me, it's enough to be able to explain the potential customer value. And this often happens after the fact. We actually try to get people here to listen to their gut and do small versions of work, _then_ tell the story of why it might matter.
I'd say it depends on how much effort it'll take to deliver the work. Want to spend a day clearing up a piece of technical debt? Guesstimate how much faster you'll end up adding new features after resolving it. But the bigger the piece of work the more effort you should put in quantifying it.
I'm a big fan of both aiming to deliver value (by having a value hypothesis for each new thing) and making sure we're delivering value. But actually quantifying it can be tricky. Do you mainly use value proxies here? E.g., X people are using the feature Y times per week?