I would start by only doing rebuilds - especially if you're on Enterprise Edition and that MAXDOP = 8 is helping you more than MAXDOP = 1 would. I agree with the other posters; reorganize is a waste. It has one benefit over rebuild - if you stop it partway through, some of its work remains.
An easy thing is that you can also try tuning the MAXDOP - is 8 too high? I'd guess that MAXDOP 3 or 4 would deliver nearly all of the performance at a much lower CPU cost. It's certainly at the upper limit of what I'd do. If you have dedicated, separated disks - or have databases on 100% flash storage - you can experiment with running two lower maxdop index maintenance jobs in parallel, and see if the aggregate result is superior. If you're on shared spinning disks, expect it to get worse instead.
Do make sure you're doing statistics maintenance, as Jeff said.
More importantly, while I don't agree with the "turn off index maint" part of Jeff's statement, I 100% agree with FILLFACTOR maintenance and care, to the point that years ago I started changing the DEFAULT fillfactor to less than 100%, on the premise that it's an exceptional case where 100 is ideal for most indexes across the board, not a normal case. Leave a little room for new/larger (VARCHAR) rows on each page, and you're likely a lot happier.
Monitor which indexes are getting rebuilt EVERY time; consider those for dropping fillfactor - they probably have rows added or enlarged "in the middle" regularly.
If you can, I also split my maintenance by size; tiny things get rebuilt and their statistics updated much more often than big ones that take time, since it's nearly free (a few minutes during a short nightly maintenance/slowness OK time) if you have some time nightly where performance degradation or brief blocking is ok. If you don't have that time, obviously don't do that!