Challenging requirements may be the biggest lever to pull. Rarely do people take the time to understand if they can be removed or altered, only to realize they are of low value to the customer's needs.
Candost Dagdeviren wrote a great post, including many tips and ideas you can try out with your team: "You need to be resilient, relentless, and focused. Moreover, you have to have the people who want to put the work together with you. If you have a team of missionaries who just implement the code and don’t care about the rest, then you won’t get any results. Also, you have to have the right organization—not every organization is the best candidate to implement the whole system. However, if your organization develops its own product, then you can probably apply a few things from here to your team, if not the whole system."
"The next time someone asks why code coverage or deployment frequency matters to the business, you’ll have the answer — and a framework to back it up!" Mapping out KPIs to show how engineering can impact the business on multiple dimensions is a great way to explore our understanding. Iccha Sethi helps you to see the correlations.
I love each and every opinion by Tal Raviv, but maybe this one above all: "Smart people are good at painting incredible narratives from way too little data — and quickly. This is the fast lane to losing respect of your teammates and stakeholders — or worse, building crap no one wants. Instead of being intelligent, do your homework. Doing your homework is the ultimate influence card. Doing your homework transcends rank and seniority and politics."
As you progress in your career, both on the IC and management paths, you'll need to align with executives and ensure you drive your agenda while it fits the company's goals and the executives' agendas.