• Replies 4 replies
  • Subscribers 333 subscribers
  • Views 189 views
  • Users 0 members are here
Related

Seeking feedback on a possible new feature

Meaghan Metke
$organization

Hello all! My name is Meaghan and I'm a Business Analyst with the Tessitura Network.

We received a great suggestion to create some sample lists and output sets to include as standard features in Tessitura, similar to what we do with sample HTML templates. We believe this would help new or less experienced users get a feel for how to pull a list, as well as possibly saving time by pre-building some basic lists/output sets that are commonly used - for example, current subscribers/members/donors, un-renewed subscribers/members, ticket holders for tomorrow, subscriber/member info for renewals, membership/subscription info for general communication, membership/subscription info for welcome communication, etc. This also seems like a great way to make the output set recipe book more accessible, as we could build out those recipes as sample output sets, rather than making you all build them from scratch.

As we contemplate adding these sample lists and output sets, I'd love to get some feedback on the following questions:

  1. It seems to make sense to add these sample lists into a new "Sample" category, so they are easy to find. However, output sets don't have the concept of a category. Would it be helpful to add categories to output sets so they could be bundled or grouped similar to lists?

  2. If we move forward with this, what sample lists and/or output sets would you find most helpful? Don't forget that these could be lists referenced by reports, utilities, pricing rules, etc. or output sets used with an extraction (re-named to segmentations in v16).

  3. Do you think sample extractions/segmentations could be valuable as well? Because of all the data nuances that are so personal to each org, this begins to feel maybe one step too complicated to me...unless we do something like generic sample sets that include commonly used segments for import. For example, basic suppression segments, some of the lists I called out above, etc.
    1. If yes, what sample sets or segments would you find most helpful?

Thank you in advance for your feedback! It is incredibly helpful to us as we keep working to make Tessitura the best tool it can be.

Meaghan

Parents
  • $organization

    Hi Meaghan - 

    1) Yes to groupings.

    My brain goes in two directions to reach a Yes answer. First, I think if there are going to be Samples handy, it only makes sense for them to be called out as a folder of all of them to browse--basically, mirroring what we're getting used to as a learning tool in Analytics. Second, while I can't say that our org really uses categories like I think they're probably intended (can't say there's consistent technique), I personally find them very helpful as a way to help my eyes identify what I'm searching for by just having a little less in front of me--filtering, basically. In fact, I save all our email lists (aka data saved out of extractions, where you see the real work product) into a dedicated folder just as one way of getting them out of they way.

    2) Examples....Queries related to:

    - email/mail suppressions

    - contact point preferences etc and interests (ie show that you need to select both the interest and the status of checkbox etc)

    - some basics of using Ticket History

    - some basics of using contribution history

    - things related to pre-visit or post-visit messaging (dynamic and relative concepts); within this, some clear indications of what's standard and what's easy to custom build via recipe books; also, have the examples represent some of what can be funky, like <= and >= for Ticket History Perf Date.

    3) Yes. 

    Mostly a yes because I like the idea that it's standard that all the things you build in "regular" Tessitura (aka not wading into SQL and intense Tables) have a consistent section of Examples That You Can Run. But, I also agree that the slope gets slippery faster here, so starting small with the sample set sounds smart--maybe just one for email and one for mail or so on.

Reply
  • $organization

    Hi Meaghan - 

    1) Yes to groupings.

    My brain goes in two directions to reach a Yes answer. First, I think if there are going to be Samples handy, it only makes sense for them to be called out as a folder of all of them to browse--basically, mirroring what we're getting used to as a learning tool in Analytics. Second, while I can't say that our org really uses categories like I think they're probably intended (can't say there's consistent technique), I personally find them very helpful as a way to help my eyes identify what I'm searching for by just having a little less in front of me--filtering, basically. In fact, I save all our email lists (aka data saved out of extractions, where you see the real work product) into a dedicated folder just as one way of getting them out of they way.

    2) Examples....Queries related to:

    - email/mail suppressions

    - contact point preferences etc and interests (ie show that you need to select both the interest and the status of checkbox etc)

    - some basics of using Ticket History

    - some basics of using contribution history

    - things related to pre-visit or post-visit messaging (dynamic and relative concepts); within this, some clear indications of what's standard and what's easy to custom build via recipe books; also, have the examples represent some of what can be funky, like <= and >= for Ticket History Perf Date.

    3) Yes. 

    Mostly a yes because I like the idea that it's standard that all the things you build in "regular" Tessitura (aka not wading into SQL and intense Tables) have a consistent section of Examples That You Can Run. But, I also agree that the slope gets slippery faster here, so starting small with the sample set sounds smart--maybe just one for email and one for mail or so on.

Children
No Data