Okay, and does your UI screen have some quiet bug that won't come up for a year? Does it introduce some unnecessary tech debt? Did the engineer implementing it notice some accessibility or consistency issue that wasn't caught by the product team? Does it account for some weird edge case? Is it performant? Does it handle IE6 or whatever? Did it incorporate some package with a security vulnerability?

And why Feb 1? Who decides what the reasonable timeline is? How sure are you that they aren't playing political games? How do you measure their performance? Did the engineer abandon some on-call thing to get it done? Did they pull a more senior person off of their job to help? Did the manager who gets blamed for all this choose who to hire?

Management isn't binary in this way, and when managers try to make it binary, a lot of people (rightly) complain. And I'd bet that many of the people who complain about that are exactly the same people who are here arguing for remote work (not least because I am in both groups).

Quantifying work to such an extent that you can detect any slacking or poor-quality work is one of the fastest ways to make it horrible for employees. Unscrupulous employees abuse Goodhart's Law to hell and back, scrupulous ones get punished for doing important work that didn't make it onto the quantified metrics, and work becomes more about covering your ass than it is about getting stuff done.