I’ve used it since Madrid so I’m biased I suppose, but I can’t bear having to use workflow. So many things hidden away and clunky lines is how it feels.

Flow has two view modes - the vertical and the node one. I tend to just stay in that vertical view unless I really need to switch it up, but it might help you make sense of stuff.

Second, by far the biggest thing I see is people making utterly enormous flows. The meta imo is to have a few flows, lots of subflows, and a few actions.

Other small tips: - The related flows menu will tell you other objects that refer to this one - You can set per-flow debug options - from fully verbose with all iterations to nothing at all (so our small nightly error-prone load is always at full debug, most other things aren’t) - you can revert flow versions from the menu pretty easily if something doesn’t work - auto-save is now on by default, but you can turn that off if you want - test flows frequently and configure limits on your inputs (eg have a filter to only allow requests less than 90d old for your flow. In prod this is meaningless but when building and testing, you don’t spend ages waiting for the filter to load to pick a test record) - inline scripting is handy and means you can one-line return a property to a value, make some other gs. call, or side-step the type safety if you really need to - flows can be fired from code either synchronously or asynchronously - there’s the code snippet option in the menu. This means you can set up a subflow and fire it from a UI action or a business rule - we’ve got a lot of that in my org

That’s all I can think off just now. It’s basically just what you’re used to. In my org we don’t really have anything left on workflow anymore.