We (my organization) are about to wrap up our first year in Tessitura. WOO! We've learned a lot about how we use the system for development purposes, and now that we have one year under us I'm MUCH more confident in making decisions about field usage, style, etc. And because we're still in the very early stages of our version's use, I have some time to make changes to how we use fields and functions to optimize our system with minimal intrusion. I'm about to start tackling the annual fiscal year "turnover" and I wanted to pose a question to the group...
What is something you wish you could change about the way your department uses Tessitura for fundraising that would make your work 100x easier/clearer? Maybe it has to do with how analytics pulls in data, maybe it has to do with using one functionality over another, maybe it's a personal data "pet peeve" that you can't solve because of data age/time in the system.
I'm all ears! I'd love to know what wisdom you all can impart as more experienced users while I still have the time and ability to make sweeping system-use changes for next year.
THANKS EVERYONE!! :)
I can tell you we've been on Tessitura for a long time and resolve every couple of years to get Memberships off the ground but still haven't quite done it. Initially, we didn't do it because that's not really the way we talk to our donors, but we're finding we wish we had it for internal analysis purposes. The issue is that setting it up either means doing a lot of retroactive work and/or setting it in practice and then waiting a year+ before you can do meaningful analysis. And that's a lot of labor to mobilize for not terribly immediate returns. But I do wish we had it running already!