When is there not? 😂 With processes and data rules needing to adapt due to external factors, there are times when various team members get “lost in the weeds,” so to speak. Many times, this drives them to start adding layers of complexity to solutions which aren’t really necessary, because the problem isn’t as complex as they are imagining. This is the point where having the power to cut through the nonsense, strip the problem down to its most basic structure, and steer the team back towards the least complex measure that will solve the problem, is key.
One example I always think of is "when we needed to standardize a naming convention for bundled products (where a customer can reference one SKU to order this product model bundled with these specific other models and/or accessories.) A Product Director of a major class of products proposed there be a certain letter added into the bundle SKU, at the 8th position for some products, but at the 7th position for these others, but with exceptions for…
And that’s when I said no. Nope. No way. People will always be guessing if that’s a bundle SKU, plus it’s harder to manage from a data standpoint. Instead, we’re going to add a simple suffix to the end. The same suffix will go on all bundle SKUs, regardless of the product type.
I had no actual authority to mandate this. I’m not anyone’s manager, and even though we both report to VPs, this director is two levels above me in the corporate pecking order. These would be the SKUs that all customers of our $1B+ company see. But as it turned out, the power to connect this director to the more elegant and easier to use solution was more important than any corporate authority I could wield!