Menu Testing Plan: Alternative Protein Dishes

Overview

This research project defines a repeatable pilot to trial one or more alternative-protein dishes in a real-service environment. The goal is to learn whether the item can deliver acceptable guest satisfaction, predictable food cost and margins, reliable supply, and manageable kitchen impact before any broader rollout.

Why this matters

Alternative proteins can attract new guests and support sustainability goals, but untested rollouts risk higher costs, slower throughput, inconsistent quality, and dissatisfied guests. This plan helps minimize those risks with measurable tests, operational checks, and a go/no-go decision framework.

Objectives & Hypotheses

• Primary objective: Determine whether the candidate dish(es) meet target guest acceptance and profitability thresholds during a controlled pilot.
• Secondary objectives: Verify supply reliability and shelf life, measure prep and service impact on throughput and labor, and identify recipe or process changes required for consistent quality.
• Example hypotheses:
  • H1: Guest satisfaction score for the test dish will be within 10% of the comparable incumbent dish.
  • H2: Food cost % for the test dish will not exceed target margin thresholds (e.g., food cost < 30%).
  • H3: The dish can be prepared without increasing average ticket time by more than X minutes during peak periods.

Success Criteria & Scoring

Use a simple weighted rubric to decide scale-up. Example categories and weights:

• Guest acceptance / satisfaction — 40%
• Profitability (food cost & projected margin) — 25%
• Operational impact (prep time, throughput, equipment) — 20%
• Supply reliability & waste/spoilage risk — 10%
• Staff confidence & training burden — 5%

Score each category on 0–100, multiply by weight, and sum. Define thresholds: e.g., >80 = green (scale), 60–80 = yellow (refine & re-test), <60 = red (do not scale).

Test Design

Approach

Use one or a combination of the following, depending on risk tolerance and dining format:

• A/B menu placement: Offer the alternative-protein dish alongside an incumbent or control item. Randomize by daypart, table, or POS modifier when possible so you can compare acceptance and conversion.
• Limited-time special: Promote the item as a special for a fixed window to measure demand with a small-scale run.
• Soft launch / staff test: Serve the dish to staff or a friends-and-family event to surface operational issues before guest-facing pilot.

Variants to test

• Full-featured plate vs. simplified prep version (to measure labor impact).
• Different portion sizes or price points to find optimal margin and acceptance.
• Garnish or sauce variants that may drive preference.

Sample Size & Duration

Estimate a pilot duration that captures weekdays, weekends, and busy vs. slow shifts. Typical pilots run 2–4 weeks or until a minimum number of sales is reached (e.g., 100–300 orders) to produce meaningful feedback. Adjust sample targets to your average daily sales volume; smaller operations may need proportionally longer pilots.

Pricing Experiments

Test at least two price points if practical. Track conversion rate (how often guests choose the item when offered), average check impact, and margin. Use price elasticity observations to model expected contribution margin at scale.

Supply Chain & Procurement Checks

1. Confirm supplier lead times, minimum order quantities, case sizes, and cold-chain requirements.
2. Request sample shelf-life and storage temperature data; run a short spoilage test under your storage conditions.
3. Identify at least two alternative suppliers or substitution strategies for critical components.
4. Check packaging waste, handling needs, and any waste-stream or recycling considerations.
5. Verify labeling, allergen declarations, and regulatory considerations for your jurisdiction.

Kitchen Prep & Operations Impact Assessment

Document and measure:

• Detailed recipe with standardized yields and portioning rules (include prep steps and mise en place).
• Prep time per portion at normal and peak speed (time-and-motion observations recommended).
• Equipment needs or constraints (special pans, searing temps, blenders, holding times).
• Temperature control or food-safety steps specific to the ingredient.
• Additional staging or plating steps that could affect ticket times.
• Training minutes required for cooks and front-of-house staff.

Collect before/after metrics during pilot shifts: average ticket time, ticket throughput per station, number of remakes, and staff-reported difficulty.

Guest Feedback Capture Template (sample)

Combine short in-person prompts with a brief take-home or QR survey linked to POS modifier. Keep it under 6 questions for higher response rates.

Short in-venue prompt (server or QR):

• "We’re testing a new [dish name] made with [alternative protein]. Would you like to try it?" (Yes/No)
• If yes: "On a scale of 1–5, how would you rate the flavor?"
• "On a scale of 1–5, how satisfied were you with portion size/value?"
• "Would you order this again?" (Yes/No)
• Optional open text: "What did you like or dislike?"

Link POS modifier codes to each sale so responses can be joined to sales, price point, daypart, and server.

Data Sources & Collection Plan

• POS data: sales volume, check averages, voids, and modifiers.
• Guest survey responses linked to sales via modifier or ticket number.
• Inventory pulls: track ingredient usage vs. expected recipe yields to detect waste and variance.
• Time-and-motion logs: prep times, cook time, ticket completion times recorded during service windows.
• Waste logs: record plate returns, remakes, spoilage, and trim waste tied to the test item.
• Supplier confirmations and incoming quality checks during receiving.

Decision Framework & Scale-Up Plan

Use the weighted rubric to produce a composite score after the pilot. Recommended decision actions:

• Green (>=80): Approve scale-up. Create Standard Recipe Card, supplier contracts, inventory par updates, and staff training materials. Roll out in stages (e.g., additional locations or increased menu presence) with monitoring for initial 4–8 weeks.
• Yellow (60–79): Identify specific improvement areas (price, portioning, prep steps, supplier) and run a focused re-test for those items.
• Red (<60): Retire or rework the concept substantially before re-testing. Document lessons learned to inform future alternatives.

Risks & Mitigations

• Supply disruptions — maintain safety stock during pilot and identify alternate suppliers.
• Guest rejection — limit exposure via time-bound pilot and clear staff messaging to set expectations.
• Operational slowdowns — pilot in off-peak shifts first and simulate peak cooking during dry runs.
• Cost overruns — track real-time food cost and cap pilot spend; test lower-cost plating variants.

Timeline & Roles

Example 6-week cadence:

1. Week 0: Recipe finalization, supplier confirmations, staff training, setup POS modifiers.
2. Weeks 1–3: Guest-facing pilot (collect POS, time-motion, feedback).
3. Week 4: Data consolidation and analysis.
4. Week 5: Decision meeting and plan for scale, refine, or retire.
5. Week 6+: If green, phased scale and monitoring; if yellow, targeted redesign; if red, document and close project.

Assign a project lead (chef or ops manager), a data owner (manager with POS access), a procurement lead, and a QA/food-safety reviewer.

Appendix: Example Recipe Card & Scoring Rubric (templates)

Standard Recipe Card (short)

Dish name: [name]

Portion yield: [g / servings]

Ingredients & weights: list in grams/oz per portion

Prep steps: numbered steps with times

Plating: photos and time estimate

Holding & hot-holding limits: times/temps

Scoring Rubric (example values)

• Guest acceptance: average survey rating converted to 0–100
• Profitability: inverse scaling of food cost % vs. target (100 = meets target)
• Operational impact: measured increase in ticket time and remakes (lower impact = higher score)
• Supply reliability: score based on supplier performance checks (lead times, MOQ, spoilage)
• Staff readiness: qualitative score from staff survey after training

Next Steps & Knowledge Capture

At pilot close, store the following artifacts in your domain collection for reuse: finalized recipe card, supplier contact & spec sheet, POS modifier mapping, guest feedback dataset, time-motion logs, waste logs, and a short lessons-learned note. These artifacts make future pilots faster and help other locations adopt successful items.

This plan is intended as a practical, adaptable template. Tailor timeframes, sample sizes, and success thresholds to your operation’s size, traffic patterns, and financial targets.