Recently I've signed with a new employer and am currently serving the notice period at my old employer. There's a rather long notice period where I live, given my parameters (13 weeks, Belgium). Currently we are bringing a customer up-to-date with regards to a software package I've done most of the analysis, design and development for. In fact, it is a product that exists by merit of me generalising common aspects of similar projects and has come to its current form over the course of many projects and years. Most of the knowledge for it, both technical and functional, lies with me. The code itself is well documented, but the way everything fits together, domain knowledge, installation and best practices in using it all needs much more documentation.
I'm working together with another developer on this update implementation and he's learning quite well. But with me doing part of the work, explaining things to him and having to decide what to delegate, there's simply no time to explain everything. Even if I did I can't expect him to remember everything or grasp it immediately. If I could use the remainder of my notice period creating thorough user and developer guides, it would leave him with solid reference material and any future developers and users as well.
Instead, this project needs to be completed ASAP because there's a much bigger customer for the same product waiting to get started on an implementation. It's clear that my boss is expecting me to get started on that as quickly as possible, bring the other developer up to speed and have him learn and document as we go. I know for a fact that this will lead to little more than very patchy knowledge and notes, lacking insight and missing much of the techniques I've had to learn by experience. Without full documentation those left at the company will have to waste huge amounts of time figuring out how to use the software, how to expand it and will not be able to avoid many mistakes I'be made and learned from. And finally, I've spent years of my life building this architecture up, tuning and improving it; it's my brainchild and I'd hate to leave it behind "helpless".
How do I convince my boss that the company, my colleagues and future projects are best served by me setting up the resources needed for its continued support rather than having to spend my last weeks here squeezing billable hours out of a customer and setting up scaffolding that no-one will really know how to build upon?