I'm going to make this question as general as possible, as I've encountered similar problems elsewhere, those curious about the specific conditions can read below the break.
In ~2 months time, I'll be leaving my current position. My manager is aware and asked me to "clean house" and optimize where I saw opportunities. I leapt at the chance to have some free time to implement a new procedure I have been attempting to improve for almost a year. The new procedure is radically different, though I'd argue easier. It is also ~6 times faster than the previous process and requires less 'work' (there are fewer and less complicated steps).
I ordered the supplies necessary for the change to take place, and wrote what I'd call excellent documentation for my coworker to look at and then attempt. The supplies arrived today, and my colleague emailed me to let me know and then ask if I could walk him through the very specific, baby-sized steps. I responded that I'm busy and working on other, more immediate projects. I told him that he should attempt the new process but that I could make myself available at the end of the week to walk him through, if he desired. I copied my manager on this exchange so he would be aware.
I understand my colleague's reticence, as there is some potential for him to undo some significant back-end work I'd done. I told him he should not worry about this, it would be extremely simple to recover from and he should give it a shot as soon as he has the time to do so. Now I've had radio silence, and my hunch is that he expects me to show up at the end of the week and do this with him. My current inclination is to not do so unless he asks me outright, and let my manager decide who needs to give on this one. Is this the best course of action? I'd like to see my new process in swing before I leave.
Specifics I'm a sysadmin at a small firm. We're something of a managed service provider for several clients, we build Linux laptops for them by purchasing what you could charitably call consumer-grade laptops and installing a standard Linux image (with some customized applications and windows-ish DE). Since I've joined, we've followed my predecessor's process which consists of installing a vanilla Ubuntu install from a network image via PXE boot, then we run some nasty config scripts, troubleshoot drivers, and pray (repeat ad nauseam). Not only does this take hours (1.5/laptop, more if we need to more than one at once as we begin to choke out the network), but we wind up with every laptop built slightly differently as things are run in different orders, or one built gets interrupted and we forget where we were.
My solution was to purchase a cheap hard drive cloner (this one), and two SSDs to build master images on. The new procedure is to clone a master drive, drop it in a laptop to be built out, and change the hostname and mailname, rather than the tedious config scripts and little hacks we used to run. My colleague is reluctant to clone the master image I built, after I assured him I had a backup and gave him the same link, which contains the instructions in very plain english in the product description.
Two days after I asked this question, my coworker emailed me to let me know that the new process went very smoothly, and the new laptops are out for testing with the users, so far no complaints.