Last year I wrote about toolchains, and why you should consider the full toolchain when considering any new tool or component. (See Apples and oranges.)
If you're making changes, it also helps to consider toolchain families.
Every toolchain is different, but then again they often fall into familiar categories (or families). Each family exists because people were trying to solve a common problem, or to work in similar circumstances.
I like the idea of having a map of the toolchain family universe, because it gives me a view of all the options and why they exist.
If you're like me, you have favorites and you wouldn't choose to use certain toolchain families for documentation -- and yet, you've used most or all of them at some point.
More importantly, if you recognize that each toolchain family has been chosen for a reason, you won't make a misstep in choosing new tools -- because the tools that somebody chose for your organization's documentation before are clues about requirements that may still exist.
If you want to jettison a certain funky or seemingly old-fashioned tool, be sure that you understand why someone chose that tool in the first place and you will avoid a wrong turn in your tool usage.
Take a look the five most common toolchain families.