If you use the Songs and Setlists layout you will have an even easier time with performance.
Understood. I actually pursued that route early on but had a feeling of duplication of effort with all the list-making and (re)arranging.
By way of explanation, this is a close-covers act so presets are rather exacting - and rather plentiful. I'd say 20 presets for 40 songs with a few presets used 3-4 times, the rest just once.
And, as singers are wont to do, ours shuffles the setlist with every gig and changes out about 10% of the material.
So...I'm not only juggling presets, I'm occasionally creating them from scratch based on new material that week.
My strategy, such as it is, is to keep a master list (alpha sorted) in one block of the memory bank (eg presets 150-200) and keep the current setlist in another block (50-100) by copying in presets from the master. Having some empty space also allows 'bulk movement' as I have occasionally been flummoxed by 'hey you haven't got enough room to paste this here.' This allows me to have a block/preset for every song in the setlist, in order, even if there are duplicates that are a few doors down from each others. Footswitches are configured to hold, then tap for next preset (right switch) or previous (left) although I occasionally simply reach down and move with the knob.
And...you might say (again) this is what the setlist function is meant to do and I fully understand (again) but from a minimize-variables keep-sane perspective this is the method I've arrived at - even if this method may go out the window with the FM9. Last but not least, we occasionally/frequently will start doing songs out of setlist order, playing requests etc. so quickly finding the appropriate preset in the 'setlist block' or the 'master block' is necessary and relatively easy.