TL;DR I would leave him alone regarding his software components.
I just finished writing this comment and noticed it's your boss. I assumed you were the boss, bit maybe this comment still helps you.
Some people can't be convinced. (Even if they can, they can be too busy to learn new stuff.)
There's ideal and reality. I find this often discussed in software architecture books. As you've been doing, a good architect analyzes how the ideal proposal works in practice. In your case, your colleague is refusing the ideal either because he has a good understanding of the reality or it's outside of his comfort zone.
I've tried several times to convince this kind of person. They either couldn't act on what was told or intentionally ignored me. One guy even harassed me, which was his technique to get his way.
In any case, to work with this kind of person I learned to leave them alone. I let them create a blackbox and isolate my code / role from theirs as much as possible. I also try assigning a different but suitable role for them.
Regarding Google Docs... maybe assign a different person to do that for you.