Training thoughts
- Elizabeth Storrs
Ideas stolen from Matt Schieren, that feel reasonable:
Since we're a decentralized school who supports each of our divisions by deputizing super-users within that division we've structured our access and training to Slate as follows:
Anyone who needs access to Slate beyond just reading and reviewing applications must receive an hour-long 'Intro to Slate' training where we break down the system, give a brief overview of the major modules, and pick apart a Person and Application record. After the Intro training, we provide hour-long trainings on the following modules:
Queries
Deliver
Forms/Events/Scheduler
Decision Letters/Adding Decisions/Releasing Decisions
Reports
Configurable Joins
Inbox (half-hour)
Reader (half-Hour)
Our preferred method of training is Zoom, where we can record the session and then share it with our divisional super-user to hand out to anyone who may need access to that module in the future. We'll occasionally create documentation, and when we do, we always make sure to document it on our University wiki so that we can share it with anyone who needs access, it's centralized, and can be easily kept-up with.
We'll point to Technolutions documentation and Fundamentals Of videos every now and then, but due to our setup and permission structure, we usually stick with our own trainings/documentation.