You might want to take a step back and think about how you ended up where you are. I mean no offense by this, but it's worth asking yourself why you're in this

You might want to take a step back and think about how you ended up where you are. I mean no offense by this, but it's worth asking yourself why you're in this spot to begin with. The divide you're talking about? You've actually hit the nail on the head describing it. Let's face it: you're in a role that might seem a bit superficial, and yes, the pay is more than generous. Maybe it's time to own up to that reality. Let the developers do their magic; after all, that's what they're here for. There's this fascinating case about the EBT card system across different states in the US. They noticed something intriguing: a couple of states managed to roll out their systems smoothly, staying under budget and finishing early. So, naturally, everyone wanted to know their secret. Turns out, these successful states had one thing in common – they handed the reins over to the actual developers. No fuss, no frills, just straight-up development work, and it paid off big time. On the flip side, the states that ended up way over their budgets and deadlines? Those projects were bogged down by external consultants and layers of consultancy. It's a clear message: sometimes, keeping it simple and trusting the people directly doing the work is the best approach.