Matriz estrella-caballo-perro-enigma: definition, formula, and calculation

What is the matriz estrella-caballo-perro-enigma?

The matriz estrella-caballo-perro-enigma sorts each menu dish into four quadrants by contribution margin (high or low) and sales volume (high or low).

It emerged in the 1970s as a Boston Consulting Group portfolio tool; restaurants adopted it in the 1990s to stop running on emotion alone. In it, a star dish pulls both margin and traffic together (35%+ profit per portion, 15%+ of monthly total); a horse drives check average but trades margins (low benefit, high movement); a dog freezes costs with scant sales (13% food cost in special ingredients, volume below 8%); an enigma would profit if customers knew it existed. Quarterly recalculation matters: demand data shifts and an enigma can slide to dog status within four weeks as preference moves. We audited a restaurant carrying 68 dishes; 34 sold less than 3% monthly and sat taking up kitchen real estate. We extracted three months of POS data: per dish, selling price, true cost (standard recipe plus labor per portion), and quantity moved.

Applied example: a real numerical walk-through

One dish that cost $6 and sold for $20 carried 70% margin but accounted for just 1.8% of volume (enigma); another priced at $12 with $9 cost drove 18% of units (horse, 25% margin). We recalculated: 19 dogs (margin <25%, volume <8%) were cut outright; 12 horses (high volume, low margin) moved up 12% in price because demand elasticity could bear it; 8 enigmas shifted to active POS promotion. Within three months, average ticket climbed from $28 to $34 (+21%) and food cost dropped from 41% to 29% (a 12-point swing). A traditional costing system looks only at per-portion cost; the matrix adds VOLUME as a second axis. The difference matters enormously: a dish with $3 cost and $15 selling price (80% margin) looks stellar on a kitchen P&L, yet if it moves three units monthly you're locking up resources—space, labor, special imported ingredients—that could feed a dish selling 50 units at 40% margin.

How it differs from classic costing tools?

The cost tool says «this dish leaves 80% profit»;

the matrix says «this dish contributes 0.3% of actual cash flow because no one orders it.» Many chefs inherit menus that appear sound on paper but are financial anchors in practice because one-third the menu under-performs while occupying disproportionate labor and inventory. Boston Consulting Group developed this matrix in 1970 to map corporate product portfolios: business units that were both profitable and growing against those losing money or stagnant. Food service adopted it years later when audits began showing 40% of dishes in many menus generated less than 5% of revenue but consumed 20-25% of ingredient costs in specialty items. Diego F. Parra brought the matrix to Masterestaurant two decades ago as mandatory diagnostic: without it, a restaurant saying «our food cost runs 40%» has no idea whether it stems from two resource-hungry dogs or a balanced menu.

Origins: from Boston Consulting Group to your menu

The matrix forces the question that matters: which dishes actually pay for this restaurant's fixed-cost structure? The matrix is not academic classification exercise; it is operational decision-making. Many managers build it correctly then fail to act: a dog stays because «it defines us» even though it bleeds margin and kitchen space. It is also not a substitute for demand elasticity analysis: raise a horse's price 20% without testing whether customers will tolerate it, you lose volume and make things worse. Another confusion: assuming high contribution margin alone suffices; if the enigma with 70% margin sells two units monthly, it will never cover rent or chef salary. And it does not include structure costs: contribution margin is what flows toward fixed costs (rent, utilities, payroll), not the dish's net profit. A restaurant can hit perfect matrix mix yet still operate at negative margins if fixed-cost burden consumes everything the dishes contribute.

Recalculation frequency: monthly or quarterly?

For 50+ dish restaurants with reliable POS, monthly is ideal; quarterly is the minimum that stays relevant. Demand shifts occur in tight windows:

seasons (summer beach traffic spikes ceviche, kills fondue demand), new competitor entry, cultural taste movement (plant-based grew 31% in fine dining by 2024 per Datassential but is receding now as consumer saturation revealed nutritional gaps). Wait until year-end and you miss six repricing windows. For small shops (25 dishes) quarterly is adequate; data precision does not degrade if throughput stays predictable. What stays outside the matrix: chef emotions. An iconic but unprofitable dish moves to seasonal menu or specials (two weekly, by request), not immediate discontinuation; the matrix says «cut it» but you execute with judgment. Contribution margin per dish is not the same as net profit. Picture this: restaurant with $8,000 rent + $12,000 payroll + $2,000 utilities monthly = $22,000 in fixed costs.

How it interacts with fixed costs: rent, payroll, utilities?

Sell 1,000 dishes at $25 average contribution (25% margin), that nets $25,000; operating net profit is $3,000 (12% margin on sales, tight).

The matrix lifts average contribution to $30 per dish (rebalanced mix: more stars, fewer compressed horses) and net profit climbs to $8,000 (32% improvement on the previous margin without moving rent or chef). This happens by reordering dishes you already have, not adding tables or seats. At Masterestaurant we saw restaurants move from 2% to 8% net margin purely through matrix restructuring while rent, chef, utilities remained static. Any matrix is only as trustworthy as its input data. If the cost you enter is estimated («a typical steak runs $8 from our supplier»), the matrix becomes decoration. You need TRUE COST: pull the standard recipe for each dish (portion ingredients, exact quantities, today's supplier prices), add direct labor (15-25 minutes of chef or line cook, priced by complexity and prorated), and derive it.

Matrix accuracy depends on real recipe costing, not guesses

A restaurant doing this monthly catches movement: in July, specialty herb import cost jumped 40%, two enigmas dropped to dog status because true margin fell. Without live costing, you would have kept thinking they were enigmas. The matrix forces a control mechanism: volume data flows from POS (reliable) but cost data must be current or the system is noise. At Masterestaurant we always begin with recipe audit: without it, the apparatus is pure static. BEFORE: inherited menu, chef decisions about which dishes to keep. AFTER: decisions based on data: real costing per portion, verified volume, net contribution to profitability. BEFORE: emotional repricing (raise price if chef thinks it's cheap). AFTER: calculated repricing (raise 8-15% if elasticity allows and margin remains competitive in segment). BEFORE: dishes «we always make» occupy fixed kitchen space and freeze costly special ingredients. AFTER: each dish justifies its existence by margin + volume; weak ones migrate to special format or are cut.

Before vs after implementing the matrix

BEFORE: low average ticket because menu has too many cheap traffic items. AFTER: ticket rises if you reprice horses and promote stars so average customer increases basket. BEFORE: kitchen saturated, slow processes from bloated menu with no discipline. AFTER: fewer SKUs, smoother operation, less waste of special ingredients on dishes no one orders. BEFORE: restaurant gross margin undefined; only known that «profitability is missing». AFTER: operating margin calculated; clear on which dishes finance structure and which drain it.