If you've never done it yourself, then the answer is right in front of you. Before you try to make pair programming happen with your developers, a move that is

If you've never done it yourself, then the answer is right in front of you. Before you try to make pair programming happen with your developers, a move that is fitting of the boss from Dilbert comics, I suggest you work on some of your own programming tasks and ask one of your developers to help you figure something out. Doesn't really matter if you aren't that skilled. Just find a harmless task you can do that isn't critical but can help you facilitate pairing as a culture. If it's clearly beneficial, then there's a decent chance your developers will simply start doing it amongst themselves. However, pairing doesn't magically create good code, better products, or more efficient developers. If your devs don't take on pair programming, then it's in your best interest to accept that it's not for them. Everyone has a different style of being productive, and for some that means deep focus and not playing backseat driver. In any case, definitely don't try to push pair programming on them without having experienced it yourself. At the very least, ask your developers what they think about pair programming and try to get as honest an opinion as you can. Chances are they actually have opinions on it.