I have always been worried about a system that is too chatty.
When I came to work for my current org? I found that the one largest learning system instance had a user enrolled notification was essentially set on full blast with all courses triggering notifications (that I eventually helped to shut down). To many it felt horrible, if you enrolled yourself, you got an email. If someone else enrolled you? You got an email. If the course was part of a learning plan?? A person got two or more emails. Working at places 10X the size of where I am currently at makes me know that larger organizations dont stand for it and will even cap system notifications if they seem like they are being spoofed.
IMHO - that's not the way to configure things. I truly believe in the mantra that “less is more”. It is more powerful when you deploy targeted notifications to campaigns and onboarding programs. This paired with protecting the function of a manager to have an option to deploy a notification to only their team about courses they enrolled their staff into.
IMHO - this is not a set and forget configuration. People do and will talk about your system implementation. They let others know. And having email after email go out about system activity related to it can be nearly scary.
But I also know that there can be two sides to the story. How do yawl do it? Set it and forget it? Configure it at the branch level????? Or it depends?
I ask to only gain perspective.
