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?
This thread has been really interesting to read! As a follow up question for those have responded, I'm curious to know what your team structures look like. Are you a team of one, handling basically all Tessitura management/administration on your own (maybe you have specific tasks that get handled by your Ticketing or Fundraising teams)? Do you have someone who reports to/supports you, or do you report to another Tessitura administrator? And similarly, what department are you (and your hypothetical team) housed under? I'm under our IT umbrella, and I always find it fascinating to hear where different orgs put their "Tessitura person/people."
At HMNS, our structure goes:Senior Vice President, HR & Building Operations (whose depts include VS, Security, IT, Building, and HR)Director of IT -> Director, Tessitura CRM (me!) -> Systems AnalystDirector of IT (same guy, different staff) -> Systems Manager and Support Technician
Mark B, the Director of IT, handles what John's referring to as "true IT." Microsoft, vendors, hardware. He also coordinates with the web developers who work for Marketing. He knows what seems like all the programming languages. And he's who we bring our weirdest weird to for guidance. There's no way I can list all the things he does.
Then there's me. It may be confusing to have a Director under a Director, but I was Director of Membership before I accepted this role so they had me keep the level of title. My job is entirely Tess-focused and includes things like: implementing and testing upgrades and new features; creating sources/pricing rules/benefits/promo codes; troubleshooting for the staff; creating and collecting documentation and helping other depts make decisions that match how we've decided to use Tess as an org; using third-party solutions like Donate2 (who we love btw); and leading our weekly Tessitura meetings, which include the team who worked on our onboarding process. I'm currently learning SQL. I also handle our Support & Extended Services interactions, which are still pretty numerous since we just went live in August '23.
With me is Sara, our Systems Analyst. She's amazing at SQL and has been teaching me as she writes new tools for our internal-facing employee Tessitura site. She also heads our Prospect2 use, including creating and maintaining all our lists. She's fantastic at making custom output elements and ferreting out bits in the database to use to answer staff questions. She helps me with testing too.
Under Mark, but truly direct reports for him, are Mark M the Systems Manager and Miguel the Support Technician. They do a lot of the day to day tasks in and out of Tess - creating and editing perfs, making changes to the schedule for our Education department, creating and deactivating accounts, making email accounts, helping with password and login issues for all products, wiring things, fixing hardware, and handling the scanners. They do a fantastic job. Thanks to them, we have time to work on the other stuff.
Web & Graphics are elsewhere in the org.