Needs vs. Wants vs. Wish List Overall weighting should be determined by the evaluation committee according to how close the stakeholders are to the business problem. For example, if the operations team weights certain requirements higher than other teams, and the solution will most closely affect operations, the requirements of this team should be weighted more heavily. Requirements may also vary by restaurant size, restaurant service type and restaurant function - drive-thru, table seating, etc.
NEEDS
WANTS
Business critical, usually part of your current solution. List everything so there are no holes or grey areas. There’s nothing worse than finding a solution you believe is a “home run” only to find out it’s missing something critical!
Try to think of current wants and future wants. For example, if you want to integrate kiosks down the road, ask about them now.
Examples:
Your wants could also cover the opportunity to eliminate some of your current integrations or partners. For example, moving to a new POS may remove the need for a different loyalty provider or for a delivery integration partner.
• Supports your business model (QSR, full-service, bar, etc) • Handles DT, KDS, OCBs, EFT, Kiosk, etc • Integrates with current partners • Above store reporting • Loyalty & marketing technology • Third-party delivery service providers & marketplaces • Payroll/HR options • Reporting • Accounting package • CC and gift processor • PCI compliance • Hardware & software support
RESTAURANT TECHNOLOGY NETWORK
WISH LIST These are items that you wish to have in a new solution, but may not be common or currently available. Examples: • Integration with an in-house developed accounting or loyalty program • Ability to manage menus and prices across POS and third-party delivery services
|8|
