Name the lane, not the screen
Screen-based event names feel natural during a sprint. They age poorly when the same step becomes a scheduled job or a messaging bot.
Prefer lane names that describe the business step: invoice_reminded, sync_reconciled, onboarding_nudge_sent. Attach screen or channel as a property, not as the event identity.
This small taxonomy choice is the difference between an automation insight map that survives a redesign and a board pack that needs rewriting every quarter.