Tessitura Governance

Hi everyone,

My organization is new to Tessitura - we are going live in July - and are working on our governance structure recommendation. I'd love to learn from you about what works well and what doesn't work well in your respective structures?

We are hoping to move toward a centralized structure with a department that oversees functional usage and data management but wonder if this structure discourages other internal business units from taking ownership of data? This unified hub would manage gift processing/acknowledgment, extractions, data maintenance and hygiene, manage Tessitura internal committee,  etc.

If your organization has a decentralized governance structure, what are the pros/cons? Who manages SOPs and data hygiene,, etc?

Thank you all for your feedback. Looking forward to learning from you! :)

  • Former Member
    Former Member $organization

    Hi Susie,

    We centralized in January in preparation for our May Tessitura go-live, bringing gift processing, program and group reservations, customer service, data management and call center into a single "Central Station."

    Our reporting and data pulls, however, go through IT. Loosely, Central Station manages system inputs and IT does configuration and outputs. A multi-departmental steering committee oversees the ongoing Tess implementation.

    We are by no means done evaluating our new structure and making tweaks. I can say though that as former stewards of the data who were now handing off control to a third party, many of our business units were, if anything, more invested in its integrity following the switch! :)

    In fact, we are moving towards more of a hybrid model in which areas that have very unique information sets (education, development) are being given limited abilities to add and modify their own data in order to better manage their business.

    Be happy to talk more offline if you'd like. Curious to see if you've made the switch, as well, and hear how it went.

    Chrissy