Institution-Wide Training Strategy

Hello All, 

I am interested in creating a formal training program for Tessitura users here at my organization to ensure that institutional standards are being clearly communicated across many departments that all use the system differently. 

I am envisioning a tiered strategy where all new users will need to attend a basic training introducing them to the system, consistuent records, and our data entry standards. Others may also need to attend a 'reporting' training, which covers reports, lists, output sets etc. Individual business areas will still be responsible for training their staff on their specific business processes. 

Does anyone else have a training strategy they'd be willing to share? Do you offer training based on functional areas (Ticketing, Development, etc.)? Do you lean on much of the Tessitura documentation, webinars, and T-Classes or are all of your materials created in-house? 

Curious to see what has worked for others! 

 

Thanks, 

RhondaLeigh

Parents
  • The NYCTUG held an event yesterday that focused on this. Once I get the four presentations and accompanying notes upload to the Tess website, I'll send an update on this thread.

    Jamie

      
      

    JAMIE O'BRIEN

    ASSISTANT DIRECTOR OF DIGITAL SERVICES

    THE NEW 42ND STREET
    229 W 42ND STREET, NEW YORK, NY 10036

    The New 42nd Street



    On Tue, Apr 18, 2017 at 3:25 PM, Melissa Scott <bounce-melissascott2313@tessituranetwork.com> wrote:

    RhondaLeigh,

    We do two types of training, individual and group. For new employees I set up an hour-long introductory one-on-one training. Prior to the training I ask them to watch Introduction to the Tessitura Software. I cover the basics that will get them started:

    • This is Tessitura/this is what it can do/this is how we use it
    • How to look up records/record structure
    • What's in a record and where to find it
    • How to add/edit information if it applies to them and data entry standards
    • Reports they will find helpful if it applies to them
    • Org specific items like how to enter a ticket, where to find the wiki, and how to submit a gift processing form
    • Fund/Campaign/Appeal/Source structure

    After that training I do another one-on-one for Development on Plans and how we use them. I don't train on how to enter contributions, other than where to find them, because our Data Team takes care of those. PSR training is handled by the Box Office manager, other ticket training is on a as needed basis.

    For group training, anyone who uses Tessitura is invited to attend the monthly brown-bag sessions. In these sessions we've covered

    • List (basic and advanced)
    • Extractions (basic and advanced)
    • Dashboards
    • Tessitura on the Go
    • T-Stats
    • Refreshers on data entry standards
    • Reports
    • Best Practices
    • T-Casts/webinars
    • New features training for new versions

    I encourage all users in our org to attend these trainings, even if they never use them because I want to break down the technical wall between the Data Team and everyone else. We have a pretty good turnout for these and I think that's because we do it over lunch and keep it to an hour.

    A lot of the materials for training I created in house because they are specific to our org. I just use Word and PowerPoint, nothing fancy. If Tessitura has something basic I can use for training, then I'll use that. It's a combination of both.

    I feel like I just wrote a book! If you have questions let me know, I'm happy to answer them. Training is like my personal mission because I want people to use Tessitura and see that it can meet their needs.

    Melissa

    From: Brian Parker <bounce-brianparker6265@tessituranetwork.com>
    Sent: 4/18/2017 2:30:56 PM

    RhondaLeigh,

    Not able to contribute answers yet, but I'm curious in joining the group-think here because our consortium (Tulsa Arts Management Consortium) is actually beginning the process of how to bring on new users and have them learn and be familiar with consortia-wide standards of data entry, reporting, setup, etc.

    As we develop documentation, I'm happy to share here.

    With our Tulsa Ballet employees, onboarding has typically begun with a recommendation to watch specific T-Classes based on the new user's primary area of interaction with the database. The problem with our holistic approach has been that, since our local arts organizations are part of a PAC that uses ProVenue instead of Tess for ticketing, we have multiple databases at play at the same time.

    Thank you,

    Brian




    You have received this message because you subscribed to email alerts of postings on the Tessitura Network Town Hall forum. You may modify your subscriptions on tessituranetwork.com.

  • Yes - thanks everyone!

     

    Pieces of what you've all said are right along the lines of what I've been considering so glad to hear what's been working for more seasoned licensees. 

    I've formed a small group of stakeholders from our primary business areas (Membership, Ticketing, & Development) to help inform the initial strategy and will be happy to update everyone as we further develop our plan. 

  • I'm working on this as well - we've been live for a year with Ticketing, Membership and Development, going to bring in Marketing and Education soon. I've been tasked with developing a formal training course for these departments and also for new Development staff as added.

    When we were in the conversion process, I did a lot of group sessions for Development and Membership and prepared a lot of quickie cheat sheets. I'm going to use the Tessitura guides Stacey links to above as backbones and then polish up the cheat sheets to address more org-specific processes and usage.

    Is everyone here going to the conference? This could be a Open Space - or we just do lunch together?

     

  • This would be a terrific Open Space! If you post it I will do my best to attend and join the discussion!

    See you in San Diego in August...

Reply Children
No Data