How do I explain "out of scope" without sounding like I don't care?
The thing is, out of scope sounds cold when you say it like you're closing the door completely.
But try saying it like a tradeoff.
Bad version:
We're not fixing that in this project.
Better version:
You're right that this matters. For this release, we're fixing the checkout flow because keyboard users can't complete payment. We'll track the account settings issue for the next accessibility pass.
That does three things. It validates the problem. It explains the priority. And it names where the work goes next.
If you can, be specific. Instead of dismissing the account settings issue altogether, say something to this effect:
We're not going to fix account settings in this milestone because the current blocker is form submission. We'll add account settings to the settings reorganisation project.
It's a small difference, but you start to sound like someone who is managing the work.
People don't need every issue fixed today to believe you care. Often, they just need to see that their issues aren't disappearing.
So when you say out of scope, always pair it with three things: why, where it goes and when you'll look at it again.