I've recently taken over running the sound cues for my resident SM position; it started as a situation in which we couldn't 100% trust the sound op to run mics and run QLab at the same time, so I took over QLab through necessity. Now it's a regular thing. I gotta say, I prefer running lights rather than sound (I can feel the timing of a light cue better but sound tends to be pretty steady in its timing). But with the number of FX deployed through the light board, it's more realistic if we use a separate light op for the Ion board and myself for QLab.
That being said, with my attention on QLab, I've found that writing my cues in my book in a way that suggests how it's pronounced really frees up my mind during the show. I now use LTS instead of LX or LQ, because I say "Lights # GO" and that's what it looks like on the page.
STBY ("Standby ___")
LTS 4 ("Lights 4, GO!")
SQ J (I don't have to call this so I write it as clearly/efficiently as possible)
FX [Name/#] ("FX Flash, GO!" or "Fog 1, GO!")
RL [Name/#] ("Rail 1, GO!" or "Main, GO!" depending on what my flymen prefer)
DK 3 ("Deck Shift 3, GO!" or "Shift 3, GO!" depending on what's preferred)
The last three (FX, RL, DK) are always preceded by a STBY with more detail, so everyone is on the same page. The GO cue should be clear and simple, as clutter-free as possible. The only way I deviate is in writing my cues as they're pronounced, so I don't have to translate as I'm calling.