What's better: Making one workflow that uses many actions with conditions, or many workflows with conditions and less actions with no conditions?

I want to be efficient when creating workflows and make them perform as best as possible, and I don’t know the answer to that question.

For example, say I have a save button on a pop up form. Depending on the option of a drop down list, it can vary how the data should be stored on the form and the actions that should happen.

One way of working this is by creating 1 workflow, and within the workflow, use conditions that check that dropdown’s value to do the action.

Another option would be to make several workflows that use conditions that match each value of that dropdown, and put the actions with no conditions on them.

The second option would be easier to read and more organized, but you will likely repeat yourself in several steps (reset inputs, hide pop up, show an alert, etc.). The first option will be a bit messier, but no repetition.

What would we consider as best practices in this situation? Which option would perform better speed wise? Is there another option I haven’t consider better than both of these?

More workflows less conditionals/actions allows for less processing, faster heavy actions at scale & lower WU usage as well as allowing your app to expand easier when furthering development.

When doing conditionals based off a single drop down It’s not near as severe but when searches, filters, counts etc get brought into the mix it’s much more imperative to structure correctly.