you've described a mess correctly, but misused the term/jargon. What you've described is poor quality implementation. There are many (infinite?) implementation

you've described a mess correctly, but misused the term/jargon. What you've described is poor quality implementation. There are many (infinite?) implementations that could satisfy the product manager, but each has it's nuances of correctness in non-tested cases (if you have tests), in runtime effects, race conditions (across processes), thread safety, ease of refactor, readability etc. All these are markers of software quality, but failing to do them is not "techdebt". Tech debt is a very specific thing as described in the video above