> systemd requires time to understand in its entirety.
Sysvinit based init schemes take orders of magnitudes more time and they even work differently on different distros.
> Without having a good grasp on the startup process overall, one is unable to quickly troubleshoot issues. This causes a commercial risk of longer downtime, as sysadmins will take longer to bring the system up in case of a fault.
This is a short-term problem that is easily offset by systemd's relative simplicity in the long term.