If you're training, PLEASE do this...
If you're doing any kind of software training, or you have outside trainers coming in to do training, I beg of you, please do the following:
When you start the training, provide the learners with a complete overview of what you're going to cover. Do not just say "Now we'll walk through the membership application," but " We're going to walk through the membership application, which will include the following four steps..."
When you jump right into training without providing context and a map of where you're going, learners will spend half the time trying to decipher what you're telling them and why you're telling them that. And if they're focused on that, they're not focused on, you know, actually learning!
As the best trainers know: Tell 'em what you're going teach, teach them, and tell them what you taught them.
Wes's Wednesday Wisdom Archives
Eyes wide open and affirmative decision-making
Eyes wide open and affirmative decision-making When I work with my clients on any type […]
Honoring an industry legend
Honoring an industry legend I’m taking a break from my usual data management tips to […]
Never burn a bridge
Never burn a bridge My children have reached the age where they have, or are, […]
You CAN compete with the big guys…
You CAN compete with the big guys… In my experience, associations often undersell their actual […]
Join (or start) your users group!
Join (or start) your users group! Today’s message is simple: If the AMS you’re using […]
They don’t care, until they care.
They don’t care, until they care. One of the more common questions I get from […]
Longfellow and data management
Longfellow and data management “We judge ourselves by what we feel capable of doing while […]
Do you really need all that historical data?
Do you really need all that historical data? A question I’ll often get from my […]
AI actually requires thinking
AI actually requires thinking “I don’t think AI introduces a new kind of thinking. It […]
It’s not the mistakes, but how you respond
It’s not the mistakes, but how you respond Recently a client was complaining about a bug that […]