Proper modelling of alternative user tasks

Hi, Flowable fans,
I am building a process where we are managing a onboarding wizard with Flowable process.
We represent each page of the wizard as UserTask and upon progressing, the wizard we complete the tasks.
The question ,that i have is what is the best way to represent alternative steps in the process. Meaning customer can complete either of them as alternatives.
One option is to fork 2 parallel user tasks and complete both upon completing either of them and join them. However i am not sure this is the best approach.
Does someone have recommendation ?

Best Regards, Chavdar