Yes thank you, great point. I've definitely seen the organizational leadership push designers to be more imposing, and that's a big problem. I think that a lo

Yes thank you, great point. I've definitely seen the organizational leadership push designers to be more imposing, and that's a big problem. I think that a lot of VPs struggle to justify the cost (salary) of designers because it can be difficult to identify the contributions/value when you aren't intimately involved in the process. Because of this they want to see someone who they think will really take the reins and make the investment worth it. This is IMHO a big mistake, but it's the best explanation I can think of to explain what I've seen in the past. I think there's also sometimes an idea that engineers and designers are inherently in conflict and engineers will ruin things if not kept in check and dominated by a strongly opinionated designer. I think this largely stems from Apple and the Jobs/Ive era, but regardless, in most software I've been a part of this is a mistake. That sort of domination/conflict-based "teamwork" does not lead to the results they think it does.