Features Wishlist
Requirements Wishlist
The table below cross-references the requirements imagined in the first exercise of our community design session - the wishlist - with the last exercise of the session - the 1.0 requirements ranking. When the requirements from the wishlist in the morning were translated into the sheets for the ranking, notes of the actual discussion which took place were used. As a result, not all of the requirements from the posted sheets in the morning match up with those used in the afternoon for the ranking. We have included both sets of requirements for completeness because we are using both to inform the actual business requirements for the system.
During the morning "wishlist" session, participants shouted out features they desired. These were written on big post-it notes and put up on the wall. During the afternoon "ranking" session, participants used colored dots to rank these requirements.
Participants assigned green, yellow and red dots to each requirement. They were given 12 of each color dot and told they could assign as many dots as they liked to each requirement. A Green dot meant that the participant thought the feature should be present in v1.0. A Yelow dot meant that the participant thought the feature had merit but should probably not be in v1.0. A Red dot meant that the participant thought the feature should not be in the system. Note that there was some confusion regarding the Red dots. Some participants believed they were meant to signify that the feature should not be present in v1.0 and some participants believed that signified that the feature should not be present at all.
Reading this Chart
"Wishlist" Requirement: Requirements as they appeared in the morning "wishlist" session.
"Ranked" Requirement: Requirements as they appeared in the afternoon "ranking" session.
Green: Feature should be present in v1.0.
Yellow: Feature has merit, but is not a requirement for v1.0.
Red: Feature should not be present in v1.0 OR feature should not exist at all.
Wishlist Cross-Referenced with Ranking
| "Wishlist" Requirement | "Ranked" Requirement | Green | Yellow | Red |
| Ability to Guarantee Payment (for house seats) | Ability to guarantee payment (eg, actor prepays for friend, etc.) | 2 | 11 | |
| Ability to Hide / Show Fees | Ability to show or hide fees in ticket price | 1 | 6 | 12 |
| Accounting Interface | Ease of interface with accounting | 2 | 3 | |
| Accuracy - Information - Names / Dates | Info accuracy - names, dates, no. of tix | 5 | ||
| Address verification | Auto address verification to help keep database clean | 4 | 1 | |
| Affiliate Program - Crowdsourced Sales | Affiliate program (crowd-sourcing, reseller API) | 2 | ||
| Affordability | Affordability | 5 | ||
| Analytics | Analytics | 2 | 2 | |
| Auditing | Audit functions | 2 | 1 | |
| Automated Marketing | Send emails automatically depending on user's purchases | 7 | ||
| Automated Subscription-based Reports | Ability to auto-send certain info reports | 3 | ||
| Barcodes: print-at-home and mobile | Ability to print at home / bar-codes | 5 | 1 | |
| Box office sales | Work well with on-site purchases | 5 | 1 | |
| Business Rules for Ticket-Sale Channels | Business rules configuration (if the ticket hasn't been redeemed at 7:58pm, release it) | 1 | 5 | |
| Campaign Across Orgs / Shows | Campaign management across organizations - shared discount codes, etc. | 5 | ||
| Check-in System | Check-in systems | 3 | 1 | |
| Connect Tix Purchases to Other Data About Person | Ability to collect user data | 11 | ||
| Contextual Help | Contextual help for backend | 1 | 1 | 2 |
| Co-selling | Books available for performance (co-selling and merchandising) | 4 | 8 | |
| Cross-Organization Login (for administrative users) | Unified cross-organization login so user doesn't need profile for each venue's ticketing system | 5 | 6 | 1 |
| Customizable Sorting w/ Reporting | Sort display of tix by days/performances/etc. for partons and staff | 3 | ||
| Dashboard - Realtime Reports | Real-time reporting (dashboard) | 12 | 3 | |
| Data-Mining | Info about path of patron/data mining | 2 | 1 | |
| Demand Pricing | Demanding pricing - pricing that changes | 3 | 4 | 1 |
| Direct Collaboration Across Users | Ability to exchange tickets with other users | 4 | 5 | |
| Discount Codes | Tracking discount codes and where they come from | 6 | 6 | |
| Embedded content | Ability to embed links and content (to YouTube, etc.) | 7 | 6 | |
| Flexibility w/ Add-Ons, Fees | Flexibility with add-ons (service charges, etc.) | |||
| Free ticketing tracking (comps) | Tracking free tickets | 5 | 1 | 1 |
| Gifts | Gifts and gift cards | 3 | 4 | 7 |
| Group Sales | Group sales | 4 | 7 | |
| GUI Picking of seats | Ability for user to enter specific seat into the system and see if it's available on one date or range of dates | 3 | ||
| GUI Picking of seats | Ability to choose exact seats | 6 | 4 | |
| High-Velocity support | Ticketing velocity support (hand-held credit scanners, etc.) | 9 | ||
| Hotwire.com functionality (user-set threshold sales) | Hotwire.com functionality for performances and/or seating | 2 | 5 | |
| Householding / disambiguation | House-holding (merging data); disambiguation of data | 3 | ||
| Human Support | Lots of Box Office support (easy way to report errors/bugs, etc.) | 2 | 4 | |
| Information Capture | Info capture | 1 | 1 | |
| Integration with other Ticketing Systems | Ability to interface with other ticketing systems | 1 | 3 | |
| Intuitive backend operation | Need not to be a computer expert to set these things up (backend usability) | 10 | 1 | |
| Intuitive User Inteface | Consumers shouldn't have to think/usability | 4 | ||
| iPhone/Blackberry support | Mobile/API Functionality | 5 | 1 | 1 |
| Line Item Reporting | Distinguish between ticket sales, service charges, etc. (line-item reporting) | 1 | 4 | |
| Mobile / Small Device | ||||
| Multi-performance ticketing (festival, multiple disciplines) | All-access passes for festivals or multi-show tickets | 2 | 4 | |
| Multiple Logins | Multiple logins | 3 | 1 | 11 |
| Non-Performance Events | Ability to sell classes and other non-performance events | 5 | 13 | 4 |
| Open-Ended Realtime Synidation | Allocation and open-ended syndication of sales | 2 | ||
| Open-Ended Validation w/ Manual Approval | Ability to approve/disprove orders | 1 | 3 | |
| Organizations Able to Setup Own Ticketing | Letting organization setup its own ticketing (arbitrary players can set up) | 4 | ||
| Other Patrons in Party Identification | Ability to find out who the purchaser is bringing to the show | 1 | 2 | 2 |
| Patron Ability to see when Related Patrons are Going | Ability for patron to see when friends are going | 3 | 5 | 5 |
| Patron-defined alerts (Venue, Actor, Director) | Alerts sent if favorite seats become available | 2 | 8 | |
| Patron-defined alerts (Venue, Actor, Director) | Alerts sent if favorite stars/directors are in shows | 3 | 5 | 2 |
| Patron-side calendar integration | Ability for user to cross-reference their own personal calendars | 1 | 6 | 1 |
| Payment from Any Source | Ability to accept all forms of payment (cc's, debit, ATM card, PayPal, e-check, ING withdrawal, cash) | 4 | 9 | |
| Popular Media Searching Mentions | Algorithm that looks at popular media so it pulls in reveiws / mentions (with ability to filter); for Google Alerts, Facebook, NY Times, etc. | 5 | 2 | 3 |
| Priceline.com functionality (bidding on tickets) | Priceline.com functionality | 1 | 6 | 13 |
| Granular opt-in and opt-out functions | 4 | 4 | ||
| Rebranding | Control over aesthetic/branding | 5 | 2 | |
| Reports, Data, Templates for old and running shows to re-open shows just by adding dates | Ability to access archived shows / archived data and can add dates to older shows (re-use data) | 8 | 3 | |
| Reports, Data, Templates for old and running shows to re-open shows just by adding dates | Templates to set up shows based on previous shows, etc. | 14 | 1 | |
| Rewards Program (cross-organization) | Rewards program within and across orgs | 2 | 10 | |
| Salesforce (sales team) incentives | SalesForce incentives/tracking | 1 | 5 | 14 |
| Security | Security | 11 | ||
| Self-Service Returns | Self-service returns | 4 | 5 | 18 |
| Sell a Ticket Twice or "n" times | Ability to sell tickets twice | 1 | 2 | 7 |
| Shadow demand reporting (tracking what people really wanted) | Shadow demand (what user wanted to buy but didn't buy) | 3 | 17 | |
| SMS Notifications | SMS alerts for staff | 10 | 6 | |
| Social Networking | Social networking links | 4 | 7 | 1 |
| Strong Customer Service (for ATHENA Tix software to venues / producers) | Strong customer service | 2 | 1 | |
| Surveys | Surveys | 2 | 5 | 2 |
| Ticket / Seat History | Seat history for patrons | 4 | 1 | |
| Track No Shows | Track no-shows | 1 | 10 | |
| Training | Training | 6 | ||
| Usability | Staff usability | 6 | ||
| User-Generated Comments | User comments on show | 2 | 4 | 8 |
| Venue Imagery | Effective venue imagery | 1 | 4 | 7 |
| Ability for patrons to search for best seats across a range of dates so that is shows them the best seats first instead of showing each date in order. | 2 | 5 | ||
| Ability for staff to make ticketing decisions on the fly | 1 | 2 | ||
| Ability to create discount codes / Pricing points on the fly | 3 | 1 | ||
| Ability to deal with cancellations / i.e. notify ticket holders via email, etc. | 10 | 4 | ||
| Customer Self-Service | Ability to exchange tickets online | 3 | 9 | 2 |
| Ability to give MPAA-type rating to performance and search accordingly for family friendly or more racy fare | 1 | 23 | ||
| Support for Secondary Markets | Ability to interface with half-price resellers (TKTS), papering organizations (Theater Extras), and high school ticketing programs (High 5) | 7 | 4 | |
| Ability to interface with Paychex, etc. for staff/crew/actors | 1 | 23 | ||
| Ability to know when and how patron is sorting info | 1 | 3 | 10 | |
| Ability to look at calendar and see what else is on that date (for staff and user) | 3 | 1 | ||
| Ability to save any configuration | 1 | 5 | ||
| Ability to save docs like Google Docs | 18 | 2 | ||
| Ability to search for cheapest ticket across dates ("I won't pay more than $ x.") | 4 | 5 | ||
| Ability to take money from actor's paycheck for friend's houseseats | 33 | |||
| Ability to track users cross-venue (sector participation) | 2 | 1 | ||
| Ability to use multiple types of payments | 2 | 5 | ||
| Abritrary house seating ability | 1 | 3 | ||
| Alerts on when tickets are being resold on other sites (for patron and staff) like StubHub, Ebay, TDF, TheatreMania, etc. | 2 | 4 | ||
| Algorithms to figure out how many seats must be held at each show if people have all-access passes | 2 | 11 | ||
| Around-Me or UrbanDaddy (iPhone apps) type of info about what is around the theatre - restaurants, other venues, etc. | 1 | 6 | ||
| Auto SMS notifications to patrons | 1 | 10 | 2 | |
| Constituent relationship | 1 | 2 | 4 | |
| Customizable check-out questions (join mailing list, purchase other tix, etc.) | 4 | 1 | 1 | |
| Customizable Reporting | Customizable reporting | 4 | 3 | |
| Different Dashboards by Role | Customizable time functions outside of just ticketing -- auto-emails, tec. | 1 | 2 | |
| Different interfaces for presenting houses and presentees | 3 | |||
| Ease of making ticket packages | 5 | |||
| Easy import and export to other databases | 9 | 1 | ||
| Easy methods of cancellation | 4 | |||
| Finding out what user is doing before and after show and incorporating those experiences (ancillary activities) | 1 | 3 | 1 | |
| Fraud-prevention for tickets | 5 | |||
| Geocoding / Tagging | 6 | 5 | 3 | |
| Hand-held information collectors | 3 | 5 | ||
| How many clicks per patron | 2 | 5 | 4 | |
| Human Support | Human support for front end and back ends | 8 | 1 | |
| Immediate access to info in terms of revenue | 1 | |||
| Automated Anomoly Detection | Indentify anomalies | 1 | 1 | |
| Info on all pricing information for user (inlcuding premium seating, rush tix, standing room, etc.) | 1 | 3 | ||
| Info on disabled seating (and ability to plug it into the backend) | 1 | 2 | ||
| Capture sales / patron info for cash sales | Info on non-web sales | 1 | ||
| Information availability for house managers | 3 | 5 | ||
| Integrating in-bound and out-bound advertising | 1 | 1 | ||
| Intuitive user interface | 7 | |||
| Inviting friends | 3 | 1 | 1 | |
| Privacy Controls / Prefs | Levels of confidentiality for user/privacy preferences | 9 | 1 | |
| Intuitive defaults | Minimum features to set up ticketing/clean-and-simple defaults | 4 | ||
| API / support for 3rd party developers | Multiple access points to data (support for 3rd party developers) | 1 | 1 | |
| Multiple end-points to the same database (consignment sales) | 1 | 2 | ||
| Offering preparatory information about show | 4 | 3 | 3 | |
| Parking / Transportation info | 3 | 10 | ||
| Preventing ticket-resellers / scalpers from buying mass quantities of tix as soon as they go on sale (through use of specialized software) | 2 | 1 | 1 | |
| Recognition of who is buying the ticket (donor, board member, etc.) | 5 | 3 | 1 | |
| Recognizes previous users | 7 | 3 | ||
| Repicking / upgrading seats if available | 7 | 1 | ||
| Resell tickets without turning into a scalper | 7 | 4 | ||
| Reserved Seating | Reserved seat ticketing | 14 | ||
| Seat maps | 6 | 1 | ||
| SeatGuru.com info for theaters (legroom, sightlines, etc.) | 1 | 3 | 8 | |
| Subscriptions | Series / subscription purchases | 7 | ||
| Show suggestions based on info plugged in by user ("I want a family friendly show with good saets and a star actor") or based on their previous purchases | 2 | 3 | 2 | |
| Software facilitates community of practice | 1 | 3 | ||
| Ties to frequent flier programs | 3 | 2 | 18 | |
| Upselling / co-selling opportunities | 2 | 4 | ||
| User profiles | 13 | |||
| Username / password generators | 1 | |||
| Alerts for Sales Levels | ||||
| Allocations / Consignment Sales | ||||
| Arbitrary Setup Workflows | ||||
| Arbitrary Statusing (not just letters, numbers, etc.) | ||||
| Auditing | ||||
| Auto-reminder | ||||
| Campaign ROI Tracking | ||||
| Cross Venue Data / Sales | ||||
| Customer Sorting / Filtering | ||||
| Customizable Transaction Info Gathering | ||||
| Detailed Venue Maps | ||||
| Discount Codes | ||||
| Easy Bug / Issue reporting for system users | ||||
| Good Documentation | ||||
| Granular customization | ||||
| Import from Other Ticketing System | ||||
| Integrated advertising | ||||
| Inviting a Friend | ||||
| Marketing for ancillary activities | ||||
| Multiple Discount Codes | ||||
| Patron seating preferences kept | ||||
| Pre-reservation | ||||
| Pricing Flexibility | ||||
| Reminder System for Patrons | ||||
| Report Purchases to Social Networks | ||||
| Snapshot / Reporting for Support | ||||
| Speedy Payment | ||||
| Status Meta-Data | ||||
| Subscriber Self-Service | ||||
| Support co-production / co-presentation (including settlement report) | ||||
| Support for Telephone Sales | ||||
| Threshold and Trigger Sales to Patrons | ||||
| Tools for Show Broadcasting | ||||
| Trady Buzz ???? | ||||
| Usability | ||||
| Validation | ||||
| Year-over-year sales projections | ||||
| Quickbooks integration | ||||
| Tessitura integration | ||||
| Filemaker integration | ||||
| Dynamics/GP integration | ||||
| Raisers Edge Integration | ||||
| Integration - Software / DBs | ||||
