The problem with the phrase "outcomes over outputs" is that people internalize it as "outcomes, not outputs" i.e. it gets misinterpreted in the same way that the Principles of the Agile Manifesto get misinterpreted. e.g. Responding to change over following a plan.

I use a different version of this that I've found helps people overcome that bias.

Skills-->Actions-->Outputs-->Outcomes

You need them all, and there's a clear dependency from right to left. Outputs and Outcomes are end results, but you can't get good end results without the right Actions and those don't happen without the right Skills.