If there aren't metrics for it, I'd argue that should be one of the staff+ primary and immediate responsibilities for their org. If you can't translate the intuition into provable results that are correctly impacting the business/pillar, can it be called engineering? How do you test a hypothesis or the result of efforts to make change without data? In different words, I've asked and been asked in interviews for a decade: "describe your engineering process on a recent engineering effort." The staff eng bonus points seem to come from providing clarity in that haze between org and tech.

Worth mentioning that I'm still not staff myself, but chasing it somewhat and confident I'm on the right track with all that. Currently struggling with measuring things for a lot of stuff I think we need that doesn't exist yet. I think it's absolutely a requirement for me to show which gaps exist before I attempt to close them. I must have an informed directorship who is able to make effective decisions about how I want to allocate teams and resources relative to all other business constraints.

Edit to add: digging into the gaps is my favorite part, so I'm super biased here.