Hello hivemind!
I am working on creating a formal power user certification program at my organization, and wanted to see what everyone else's power user definition was. My goal is to create a test of sorts that people have to pass to be considered a power user, and, as a result, have higher levels of access in Tess. Ideally I'd like 1-2 per department. We already have a really solid Tessitura admin team, but we want to empower our users a bit more. The idea behind the test is to make the skills quantifiable so that nothing can be misconstrued as personal if the status of power user is denied.
Does anyone else have a formal training/cert program for power users?
What knowledge do you consider essential (especially for fundraising/customer service/marketing departments)?
What would you consider a deal-breaker for someone for someone being considered for that title (attitude, skills, seniority, etc.)?
If you were creating a skills test for power users, what would you have included?
I'm open to any input and suggestions!
Happy Tuesday
I am interested too. It is a perpetual question for me, and my thoughts have shifted over the years. I agree with Eric that data standards are essential and think another area that is important is troubleshooting and being a resource for others in the department. I'd suggest some questions about getting new users installed/logged in (we are self-hosted, so people have to run a script to install Tess on their desktops), about putting open batches on hold, about how to report a technical error properly, about your org's duplicate management process, what to do when a constituent in a household dies, or when a household divorces, etc.
As to crucial qualities power users need, I'd say ownership of the role and initiative are key. Good luck with your plans! Catherine
Thanks Catherine! These are all great ideas! I've been trying to figure out how to quantify initiative and using their resources. I think one major quality that I've found in power users is their ability to locate and utilize proper documentation.