Hi Connie,

This setup looks good to me, but best practice is to use a gateway. As you've mentioned, this will work like your user wants by kicking off two paths immediately. In this use case, this'll be fine since it's basically like a parallel gateway split, and there's no merge back in the paths. 

It's also possible to set conditions on branches coming out of a task without using a gateway (i.e. exclusive gateways aren't always strictly necessary), but usually I'll recommend gateways because they confer additional logic onto the process (e.g., inclusive gateway behavior and prioritization of which outflow to follow) and they add some level of notation onto the process diagram itself. By using gateways, other users can pop in and easily see the intention behind the design without clicking into every path.

Of course, merging the paths requires specific gateways as well if those paths were to come back together, but in this case where all the process needs to kick off on the second path is a confirmation task, we don't need to worry about that.

(Edited to say that usage of gateways is definitely a best practice like you mentioned, but it'll certainly work the way it's configured!)