The ability to target different roles for child steps seems like such a trivial enhancement but it would remove a lot of unnecessary duplication.

I've a project that powers on a few dozen Azure VMs, checks their tentacle health and restores them to normal service. The problem with this is that, for any reasonable number of VMs, those that start early are waiting on the last ones to start before moving on to the health check and undrain steps; I’d like to use child steps to enable concurrency. When you’ve multiple environments and different types of target, running this concurrently becomes harder than it should be in Octopus; whilst I could achieve this with cloned parent steps, the optimal process would be one where I can set the targets within the child steps and not have Octopus enforce the scope of the parent step.

This is pretty much necessary in a load balanced environment where the farm servers do not have access or permission to add / remove themselves from rotation.