Pair programming is not a silver bullet. It's a tool that's appropriate sometimes and not others. Rigid adherence to pair programming as a practice lacks appreciable agility...if you get my drift. If the act of pair programming produces worse results, then not being able to pair program is not limiting their potential. Trying to pair program is.

I worry that framing the relationship from the outset in terms of "I've got" suggests a particular mindset in regard to the distribution of power. Ideally leaders work for their team rather than owning it. The developer isn't the necessarily the place to "start fixing things."

Good luck.