'something that solves enough users problems it's worth it to implement it' rather, and I think it is often difficult to judge how much engineering time to spen

'something that solves enough users problems it's worth it to implement it' rather, and I think it is often difficult to judge how much engineering time to spend on user issues. I'm currently working in an internal team, so I value cost savings estimation, but even before prioritising was also a bottleneck (although a small one compared to architecture and design)