The latest update in Journeys is the ability to execute Actions within multiple Steps at the same time. We call this Parallel Steps. 

Historically, all Steps had to be run in sequence where each Step would only begin after the Step before it was completed.

But what about when you have two teams or two work streams that need to be completed but are not dependent on each other in order to get started? This is where Parallel Steps come in.

You can now drag multiple steps into a Journey side-by-side so they can run at the same time. These Steps are placed into a Parallel Steps container so they all start at the same time and the Journey only progresses when all Steps within the container are complete. This allows teams to complete work faster while ensuring active work does not get ahead of any dependencies.

An example of Parallel Steps would be when you have two separate teams working to onboard a new customer, but in completely different capacities. For example, one team is helping the customer upload the menu for their restaurant while another team is helping to build a custom integration. This work can happen at the same time, but you can’t progress to the Go Live Stage until both of these work streams are complete and the customer has finished the software configuration.

What other capabilities would you like to see within the Journey Builder? We would love to hear your feedback.