My current title is "CRM Administrator." I'm our Tessitura DB, essentially. I have some SQL knowledge, but I'm not writing custom reports or stored procedures. But I do all FY and performance builds; I am responsible for TNEW content; I'm currently the only one building analytics dashboards; I do all training and onboarding; I maintain documentation of our system policies and procedures. My boss has never liked my title and thinks it should be Database Manager. I'm curious -- if your job sounds like mine, what is your title?
My role is very similar, except I do write custom reports and stored procedures, and I don't do performance builds (and I'm only responsible for some TNEW content). My current title is Shared Services CRM Director (Shared Services because we are a consortium and I do this work for the consortium orgs too). In previous iterations I've been Director of Data & Analytics, Data Services Manager, and (Shared Services) Database Specialist. I like the use of "Data Services" rather than "Database" because I think it reflects the broad nature of these types of roles a bit better; Database feels purely technical, but Data Services feels like it involves the technical and the reporting, training, and documentation aspects.
I also have a similar role, my title is Associate Director of Patron Data. I am responsible for training, troubleshooting, advanced reporting, process development and documentation, upgrade planning and managing our relationship with Tessitura.
My title is 'Analytics Manager'. I have very little SQL knowledge. I am currently working on delegating the perf/contribution builds for each year. I do most of the Analytics building, and most of the list pulls. I do some training, but most of that has moved elsewhere. I also manage all the Tessitura integrations (kiosks, dynamic pricing, website, etc.)
I like Data Services Manager! And that might actually go over better with upper management. We have other database managers and they've been arguing that our jobs are different, but maybe they would go for data services.
Thank you! That sounds a lot like what I do.
My role is very similar to yours. I am the one who builds out the majority of the Ticketing dashboards (thankfully Devo has a good handle on the Membership ones). I also train literally everyone (that's technically not in my written job description but I do it anyway because nobody else wants to), which includes all of our documentation. I am one of 3 Power Users within the organization, but most times the day-to-day responsibilities fall on me. I am also the one making all of the improvements (meaning implementing new ticketing strategies to make Tessitura run better).
Thankfully the only performances I have to build out are our GAs, unless our Education department is swamped, then I will help them with their performances as well. And TNEW is handled by our Marketing department.
The weird thing about my role is that I also handle all of the day-to-day techie stuff. Your printer is not working? Call Chelsea. You need a new email password? Call Chelsea. I'm also the liaison between the museum and our outside IT company. So I literally do all of the tech on top of managing the CRM.
My current title is Visitor Services Technology Lead, which I've been trying to get my boss and HR to change for 2 years now. They want to, but don't know what else to call it that would encompass everything I do.
Thanks, Nate! I manage all of the hardware we use for Tessitura as well -- tablets, ticket printers, scanners.
Thank you! We have desktop support staff for computer issues, but I'm the one that manages the surface tablets we use for tess, as well as the ticket printers and scanners.
My title is Database Administrator. I do all database admin tasks including backups, data hygiene of all kinds, data import/export, and SSRS reporting. I build our primary ticketing subscription seasons/productions/perfs via SQL, but don't usually do day by day perf setup. I am not our primary web site admin.
Anne my role is super similar and I'm the Database Supervisor which I strongly dislike. I'm going to be Data Services Manager very soon!