Menu Testing

Menu Testing for food and drink, menu-level performance evidence that item testing cannot deliver

Specialist menu-level testing for foodservice, QSR, restaurants, hospitality and contract catering. Three formats: pre-launch menu testing (before the menu goes live), operational pilot evaluation (during the pilot phase), and live menu performance optimisation (for menus already in operation). Integrated consumer behaviour and operational data with senior food and drink interpretation throughout. Designed for menus that need decision-grade evidence about how the menu performs as a coherent set, not just how individual items score.

What Menu Testing is actually for

Most foodservice menu work fails at the same point in evaluation. The individual menu items have been tested (typically through Product Testing’s in-restaurant format), they perform credibly, the team commits to the menu. Then the menu goes live and the menu-level performance is different from the item-level testing predicted. Consumers do not navigate the menu the way the team expected. Choice patterns surface gaps the item testing could not reveal. The range balance shifts performance in ways individual item scores did not predict. The menu reads differently in real consumer use than in development.

The structural problem is that item-level testing and menu-level testing answer different questions. Item-level testing evaluates each item against its own performance; menu-level testing evaluates the menu as an integrated system: range balance, navigation patterns, choice dynamics, daypart performance, cross-item substitution and complementarity, the experience of using the menu. Items can score well individually and the menu can underperform structurally because the menu-level dynamics were not in the evaluation evidence. Without menu-level testing, the commercial decisions about the menu are made against item evidence rather than menu evidence.

Menu Testing is the structured methodology for menu-level evidence specifically. The work brings together consumer behaviour research (how consumers navigate, choose and engage with the menu) with operational data analysis (what consumers actually order, how the menu performs operationally, commercial mix and margin implications) and senior interpretation throughout. Three formats scoped against the menu lifecycle stage: pre-launch testing before the menu goes live, operational pilot evaluation during the pilot phase, live menu performance optimisation for menus already in operation. Output is menu-level decision evidence: menu architecture validation, optimisation recommendations, ongoing performance improvement direction.

It is not the right tool for every brief. If the brief is item-level testing (specific menu items needing decision-grade evaluation), Product Testing’s in-restaurant format is the right tool. If the brief is qualitative depth on the menu experience (consumer experience research without statistical scale), Qualitative Product Testing’s in-restaurant format is the alternative. If the brief is menu development rather than menu testing, Menu Development is the structurally different alternative. Menu Testing sits specifically when the brief is menu-level performance evidence about how the menu works as a coherent set.

What we do differently

  1. Menu-level methodology, not multiple item tests aggregated

    The structural difference between Menu Testing and item-level testing applied across a menu. Our methodology is built specifically for menu-level analysis: how consumers navigate the menu, what choice patterns emerge, how the range balance affects performance, where the daypart logic works or does not. We do not deliver Menu Testing as a collection of item tests aggregated; we deliver menu-level evidence about the menu as a coherent system. The methodological design is different from item testing because the question is different.

  2. Three formats scoped against the menu lifecycle stage

    Different stages of the menu lifecycle need different testing methodologies. Pre-launch testing surfaces menu architecture issues before the menu goes live. Operational pilot evaluation validates the menu during real pilot phase with operational data alongside consumer evidence. Live menu performance optimisation works on menus already operating to inform ongoing optimisation. We scope the right format at the start against where the menu sits in its lifecycle, rather than defaulting to one methodology regardless of stage.

  3. Integration of consumer behaviour with operational data

    Menu performance is structurally a combination of consumer behaviour (what consumers want, what they choose, how they navigate) and operational reality (what gets ordered, kitchen performance, service workflow, commercial mix and margin). Generic menu testing focuses on consumer evidence alone; operational consultancy focuses on operational data alone. Our menu testing integrates both lenses, which is what makes the output decision-grade for the menu decisions that matter (range rationalisation, daypart strategy, menu architecture refresh, operational simplification).

  4. Senior food and drink interpretation alongside the data

    The technical difficulty of menu testing is reading what consumer choice patterns and operational data actually mean for menu decisions rather than taking the data at face value. A choice pattern that suggests cutting an item might be revealing a positioning issue rather than a popularity issue. An operational signal that suggests menu simplification might be hiding a training issue. Senior food and drink specialists interpret the menu evidence against foodservice commercial reality, which is the layer that separates useful menu testing from menu dashboarding.

What we use Menu Testing for

Pre-launch validation of new menu architecture

You have developed a new menu (typically from Menu Development work) and need menu-level testing before launch commitment. Pre-launch Menu Testing evaluates the menu architecture, choice patterns, range balance and consumer engagement before the menu goes live, surfacing menu-level issues that item-level testing could not capture. Output is launch-ready menu evidence base, with the menu architecture decisions defensible against operator, franchisee or board scrutiny.

Operational pilot menu evaluation

You are running the operational pilot phase for a new menu and need decision-grade evidence about whether the menu is ready for scale rollout. Operational pilot Menu Testing combines consumer behaviour data from real pilot venues with operational performance data and senior interpretation, scoped to deliver the scale rollout decision evidence the leadership team needs. The integrated methodology captures what consumer-only or operational-only evaluation cannot.

Live menu performance optimisation

You have a menu in operation and need ongoing performance optimisation evidence: which items earn their place, which are underperforming structurally, where the range gaps sit, how the daypart logic is working in real operation. Live menu testing provides the ongoing evidence base for continuous menu optimisation rather than as a one-off project, with the methodology designed for repeated waves rather than just single evaluation.

Range rationalisation testing

You are rationalising the menu (cutting items, tightening the range) and need evidence to inform which items go and which stay. Menu Testing scopes the rationalisation against consumer choice patterns, range balance impact, operational complexity reduction and commercial implications, with the rationale defensible against operator, franchisee or board scrutiny when the inevitable “why are we cutting these” question gets asked.

Daypart menu strategy testing

You are developing or refining daypart strategy (breakfast, lunch, dinner, late-night, all-day) and need menu testing scoped specifically against daypart performance. The methodology evaluates how the menu works across the dayparts, where the daypart-specific opportunities sit, how the menu logic should flex by daypart, and which items belong in which daypart context.

Menu refresh impact assessment

You have just launched a major menu refresh and need post-launch evidence about whether the refresh has delivered the commercial outcomes. Menu Testing measures the impact: which changes have driven performance, which have not, where the refresh has hit or missed the brief, what further iterations should follow. Designed to inform the next phase of menu work rather than as a retrospective report.

  1. Scoping call.

    Twenty minutes on a call. You tell us the menu context (channel, format, kitchen type, scale), the menu lifecycle stage (pre-launch, operational pilot, live operation), the decision the testing has to support (launch commitment, scale rollout, ongoing optimisation, range rationalisation), the audience for the deliverable, the integration with internal sales and operational data and the timeline. We tell you which format is right for the brief (pre-launch, operational pilot, live optimisation), what methodology makes sense, what consumer and operational data integration the brief requires and roughly what it will cost. Where the brief would be better served by Product Testing in-restaurant (item-level evaluation), by Qualitative Product Testing (qualitative depth), or by Menu Development (menu development rather than testing), we will recommend the right alternative honestly.

  2. Testing design.

    The senior team designs the testing methodology specifically against the menu lifecycle stage and the decision the work has to support: format choice, consumer behaviour methodology (in-venue research, exit interviews, observation, choice modelling depending on the brief), operational data integration framework (sales mix, ordering patterns, kitchen performance data, commercial mix and margin data where the client team can share), analytical approach. Design signed off by the client before fieldwork starts

  3. Fieldwork.

    Consumer behaviour research in real foodservice context (venue partnerships, in-venue research, exit interviews, observation work depending on the methodology) plus operational data collection or integration from the client team. Sample sizes scoped to deliver decision-grade evidence at menu level. Multi-venue work where the brief requires geographic or operator-type breadth. Full quality checks throughout.

  4. Integrated analysis and senior interpretation.

    The senior team integrates the consumer behaviour evidence with the operational data analysis and develops the interpretive layer: how the menu is performing at integrated level, what choice patterns and operational signals mean for menu decisions, where the optimisation opportunities sit, what the menu evidence supports the leadership team committing to. The integration is what makes the output decision-grade rather than analytically partial.

  5. Decision-ready menu evidence.

    A working readout session walking the team through the menu evidence and the implications, followed by the full deliverable: menu performance assessment at integrated level, optimisation recommendations with operational and commercial implications, prioritised next steps for ongoing menu work, transparent flagging of where the evidence is conclusive versus where further work would strengthen the case. The deliverable is built for the decision audience (board, NPD committee, brand leadership, franchisee or operator audiences) and lands within three weeks of fieldwork completion.

Three formats. Scoped to where your menu sits in its lifecycle.

Different stages of the menu lifecycle need different testing methodologies. The three formats below are scoped against the lifecycle stage: pre-launch before the menu goes live; operational pilot during the pilot phase; live optimisation for menus already in operation. Some major menu programmes commission across multiple lifecycle stages (pre-launch followed by operational pilot followed by ongoing live optimisation) as an integrated menu evidence programme.

Pre-launch menu testing

Menu-level testing before the menu goes live in operation. Methodology combines controlled-condition consumer behaviour research (how consumers navigate the menu, what choice patterns emerge, where the range balance reads) with select operational reality checks (kitchen workflow modelling, prep complexity assessment, commercial mix projection). Used when a developed menu needs menu-level validation before launch commitment, typically following Menu Development work. Typically delivers within six to ten weeks.

Operational pilot evaluation

Menu-level testing during the operational pilot phase, with consumer behaviour and operational data captured in real pilot venues. Methodology integrates real consumer ordering patterns, in-venue observation, exit interviews and operational performance data from the pilot operation. Used when the menu is in pilot phase and the team needs decision-grade evidence about whether the menu is ready for scale rollout. Typically delivers within eight to twelve weeks alongside the pilot duration.

Live menu performance optimisation

Menu-level testing for menus already in full operation, designed for ongoing optimisation rather than one-off evaluation. Methodology integrates sales data analysis, in-venue consumer behaviour research, operational performance data and senior interpretation. Used when a live menu needs ongoing optimisation evidence: range rationalisation decisions, daypart strategy refinement, item-level performance interpretation in menu context. Typically delivers in waves across an ongoing programme rather than as a single project.

Food and drink is all we do

We are not a generalist research agency that takes the occasional foodservice brief or an operational consultancy that adds consumer research on the side. Food and drink is the only sector we work in, and the foodservice channel is one of the contexts our senior team works in continuously. Our menu testing methodology is built around foodservice commercial reality (range balance, daypart logic, commercial mix, operational workflow) rather than imported from FMCG or generic research. The integration of consumer behaviour with operational data is what makes the output decision-grade for the menu decisions that matter rather than analytically interesting but commercially partial.

That focus is why we work with 11 of the UK’s top 40 food and drink brands.

Meet the Team

Other ways to build, test and refine what wins

Menu Testing is one tool in the broader Build, Test & Refine What Wins toolkit. Depending on the brief, one of these might be a better fit, or a stronger partner alongside the Menu Testing work.

Menu Testing that informed real menu decisions

Three real Menu Testing projects across different foodservice channels and different briefs.

FAQs

How is this different from Product Testing in-restaurant?

Scope of analysis. Product Testing’s in-restaurant format evaluates specific menu items individually: does this item perform on the food and drink-specific metrics, would it work commercially, how does it score against decision-grade quantitative methodology. Menu Testing evaluates the menu as an integrated system: range balance, navigation patterns, choice dynamics, daypart performance, cross-item substitution. Items can score well individually in Product Testing and the menu can underperform structurally in Menu Testing because the menu-level dynamics are different from the item-level performance. The two services answer different questions and are often commissioned together for major menu launches.

Which format do we need (pre-launch, operational pilot, live optimisation)?

Depends on where the menu sits in its lifecycle. Pre-launch testing is right when the menu is developed but not yet live, and the team needs menu-level validation before launch commitment. Operational pilot evaluation is right when the menu is in pilot phase and the team needs decision-grade evidence about scale rollout readiness. Live optimisation is right when the menu is already in operation and the team needs ongoing optimisation evidence. Some major menu programmes commission across multiple lifecycle stages as an integrated menu evidence programme.

How is this different from menu engineering or operational consultancy?

The integration of consumer behaviour with operational data. Generic menu engineering focuses on operational data (sales mix, contribution margin, item profitability) and produces engineering decisions from that data alone. Operational consultancy focuses on workflow optimisation and produces operational decisions from operational evidence. Our Menu Testing integrates consumer behaviour evidence (how consumers navigate, choose and engage with the menu) with operational data, and adds senior food and drink interpretation throughout. The integrated approach is what makes the output decision-grade for the menu decisions that matter rather than analytically partial.

How big does the sample need to be?

Depends on the format and the brief. Pre-launch testing typically runs with two hundred to six hundred consumer-side respondents in controlled or simulated menu contexts. Operational pilot evaluation captures real ordering patterns from pilot venues (the sample is the actual order volume from the pilot period, typically supplemented by in-venue research with one hundred to four hundred consumers across the venues). Live optimisation works with the live menu order data (typically running into thousands of orders depending on the venue and time window) supplemented by structured in-venue consumer research. We design the sample at scoping against the format and the decision the work has to support.

What metrics do you measure?

Menu-level metrics scoped against the brief. Standard menu-level dimensions: choice patterns (what consumers order across the menu, where the popularity sits, where the gaps are), navigation and engagement (how consumers move through the menu, where they pause, what they consider), range balance (whether the menu sections are balanced commercially and culinarily, where the dead zones are), daypart performance (how the menu works across breakfast, lunch, dinner where relevant), cross-item dynamics (substitution between items, complementary ordering, missed-sale opportunities), operational integration (kitchen complexity per item, service workflow implications, commercial mix and margin). Custom metrics added where the brief requires.

Can we integrate this with our internal sales and operational data?

Yes, and this is the most useful commissioning structure. Where the client team can share sales data, operational performance data, ordering pattern data or commercial mix data, our methodology integrates this directly with the consumer behaviour evidence we capture, producing decision-grade integrated evidence. The integration is structurally critical for live menu performance optimisation (where the live order data is the foundation evidence) and significantly strengthens operational pilot evaluation. Pre-launch testing typically relies less on internal operational data because the menu is not yet generating it.

What is the actual deliverable?

Menu-level performance assessment scoped for the decision audience. Specifically: menu architecture assessment (range balance, daypart logic, navigation patterns at integrated level), item performance interpreted in menu context (which items earn their place, which are underperforming structurally, which represent opportunities), optimisation recommendations (range rationalisation candidates, daypart strategy adjustments, menu architecture refinements), commercial and operational implications of the recommendations, prioritised next steps. Format agreed at the start so the work feeds the next phase of menu work rather than reading as a research report.

How long does Menu Testing take?

Six to twelve weeks from scoping call to decision-ready readout depending on the format. Pre-launch testing typically six to ten weeks (the most operationally compressed of the three formats because the methodology can run in controlled conditions). Operational pilot evaluation typically eight to twelve weeks alongside the pilot duration. Live optimisation typically runs in waves across an ongoing programme (each wave four to six weeks; full programme runs across the brief duration). Realistic timelines at proposal stage.

Can we run this internationally?

Yes, with careful scoping. International menu testing is operationally more complex than single-market work because the operational reality (kitchen equipment, staff capability, supply chain, consumer expectations, channel norms) varies materially between markets. We run Menu Testing across the UK and Europe with established channel relationships, and selectively in the US and UAE for specific channel briefs. We will scope international capability honestly at the scoping call based on the specific markets and operational context.

How much does Menu Testing cost?

Project-based, scoped against the format (pre-launch, operational pilot, live optimisation), the menu complexity, the number of venues for in-venue work, the integration with internal data, the geographic scope and the depth of analytical work. Single-format pre-launch testing for a focused menu is the lowest entry point; multi-venue operational pilot evaluation or ongoing live optimisation programmes are the highest. We give a clear, all-in quote at proposal stage with no hidden extras.

Got a menu that needs decision-grade evidence about how it performs as a coherent set?

Tell us the menu context, the lifecycle stage, the decision the testing has to support, the integration with internal sales and operational data and the timeline. We will tell you which format is right (pre-launch, operational pilot, live optimisation), what methodology makes sense and what it will cost. Where Product Testing, Qualitative Product Testing or Menu Development would be better, we will recommend the right alternative honestly.