> maybe tech debt is not a concern there Design can definitely generate technical debt. If the designer specifies that some widget has to look and behave just

> maybe tech debt is not a concern there Design can definitely generate technical debt. If the designer specifies that some widget has to look and behave just so, then some developer has to code a widget that meets that requirement. IME a lot of design work is purely aesthetic, and a matter of taste. That is, it's not functional; you could have used a native browser widget instead, but designer says no. And in the last shop I worked in, the designer had the whip hand, partly because the boss couldn't code, and partly because designers cost more than grunt front-end developers. So you end up with a pile of unnecessary front-end code that becomes a breeding ground for bugs and regressions. Not quite the definition of tech debt; but unnecessary code quickly turns into tech debt.