I'm a dev and I understand the frustration of multiple resource load and the bandwidth burden it imposes but also as an entrepreneur and business owner, I see the need for metrics when making a sales pitch.
> Your job is to show why both parties’ incentives are actually aligned, not opposed.
This!
It's your job to do just that because of your vantage point i.e. you're able to see everything more broadly than anyone else. Understanding that all the stakeholders in your organization are doing something important that allows everyone to have a place to come to work to tomorrow is critical for you as the engineer.
> It's your job to do just that because of your vantage point i.e. you're able to see everything more broadly than anyone else.
It sounds very good on paper but it doesn't really work in practice because devs are generally not recognized as important decision makers in product design, despite said "broad vantage point".
From there, it's a rather thankless uphill battle of the "no good deed will go unpunished" variety. It's a very misaligned situation.
The need for metrics is another way of saying "I don't trust you", which may be understandable to a degree but stakeholders should also understand that not everything can be measured, and that measuring things in a manner that is both accurate and useful is very hard. I'm skeptical that metrics have more value than the word of a seasoned engineer on a project. We don't have very good results with measuring other vague things, why would software development be any different?
> I'm skeptical that metrics have more value than the word of a seasoned engineer on a project.
That's a rather odd statement to hear from a dev (or developer advocate) because I've always heard fellow engineers talk about how data is more important than opinion. Why is this an exception?
> Your job is to show why both parties’ incentives are actually aligned, not opposed.
This!
It's your job to do just that because of your vantage point i.e. you're able to see everything more broadly than anyone else. Understanding that all the stakeholders in your organization are doing something important that allows everyone to have a place to come to work to tomorrow is critical for you as the engineer.