Profit Improvement — 90‑Day Cross‑Functional Plan (Practical Playbook)

Purpose

This 90-day cross-functional journey helps your team run a small set of focused experiments that raise margin quickly while creating sustainable standard work. It balances speed and rigor: run measurable tests, learn, then lock in what works. The plan fits single-unit restaurants through multi-location groups—tailor scale and measurement to your context.

Outcome Hangar (Primary Hungers)

Coordinate short, measurable cross-functional experiments that lift profitability quickly and create repeatable routines for continuous improvement.

High-level Timeline

• Discover (weeks 0–2) — gather data, run quick audits, and surface hypotheses.
• Prioritize (week 3) — choose the top 3 experiments with clear owners and metrics.
• Implement (weeks 4–10) — run experiments, measure, iterate weekly.
• Sustain (weeks 11–13) — standardize wins, hand off KPIs, and embed controls.

Who Should Be Involved

• Project Lead (Executive Sponsor): removes barriers, approves resources, ensures follow-through.
• Operations Lead (GM/Kitchen Manager): daily coordination and standard work owner.
• Chef or Menu Owner: recipe, portion, and menu experiments.
• Floor Manager / Service Lead: service experiments and guest-impact assessments.
• Purchasing / Inventory Contact: supplier, receiving, and waste tracking data.
• Data/Finance Contact: validates baselines and calculates P&L impact.
• Frontline Representatives: cooks, servers—essential for design and adoption.

Phase Details and Week-by-Week Actions

Discover (Weeks 0–2)

• Kickoff meeting: align aim, roles, communications, and cadence. Use a short experiment intake form (see Experiment Charter below).
• Collect and verify baseline data: daily sales mix (by item), food cost %, average ticket, labor %, ticket times, waste volumes and categories, inventory inaccuracy rates.
• Run quick audits (2–4 hour focused checks): receiving accuracy, fridge temp logs, portioning checks on 5 top-selling items, rush‑hour ticket timing sample, and a 48‑hour waste log.
• Encourage frontline input: 15‑minute huddles to capture improvement ideas and frontline problems observed.

Prioritize (Week 3)

• Convert findings into candidate experiments. Score each candidate by expected profit lift, ease of test, risk to guest experience, and time to impact.
• Select top 3 experiments (one from menu/food cost, one from waste/process, one from labor/service or revenue uplift).
• Create a one-page Experiment Charter for each (owner, hypothesis, metric, data sources, minimum detectable effect, test duration, required actions).
• Set weekly checkpoints and decide success/fail criteria in advance.

Implement (Weeks 4–10)

• Run experiments with tight controls. Keep other variables stable where possible (e.g., marketing, hours).
• Weekly checkpoint meetings (30 minutes): review results, iterate the test, decide whether to scale, modify, or stop.
• Keep rapid documentation of what changed and observed effects (photos, receipts, POS item-level reports, waste logs).
• When rolling a successful change, run a small-scale pilot at peak and off-peak times to validate across conditions before standardizing.

Sustain (Weeks 11–13)

• Standardize: convert successful experiments into SOPs, recipe cards, training checklists, and shift huddles.
• Assign KPI owners and daily/weekly monitoring routines. Embed measurement into existing operational rhythms (e.g., pre-shift huddles, weekly ops meeting).
• Handoff package: experiment summary, training plan, one-page SOP, monitoring dashboard (daily triggers and escalation rules).
• Plan a 30/60/90 day follow-up to confirm sustained impact and detect regression.

Sample Experiments (with simple measurement guidance)

Menu Rationalization

Hypothesis: Removing two low-margin, low-volume items will increase average check and reduce complexity, lifting margin by 0.5–1.5% within 4 weeks.

Metric: change in blended food cost % and average check for the same sales volume. Data: POS sales mix, recipe costs.

Waste Targeting: Prep Portion Control

Hypothesis: Adjusting portioning for a high-variance prep item reduces daily plate waste weight by 20% and lowers food cost by 0.4%.

Metric: daily waste weight for that item, ingredient usage vs expected by recipe yields.

Labor Rule: Smart Scheduling Pilot

Hypothesis: Implementing a simple rule (add one expeditor only for the top 30 minutes of rush) reduces ticket times by 10% and improves table turnover without extra scheduled hours.

Metric: ticket time distribution, covers per labor hour during test period.

Service Upsell Script

Hypothesis: Training servers to offer a specific high-margin add-on at check-in increases attach rate by 15% and adds X dollars per check.

Metric: attach rate, incremental average check, guest feedback/complaints.

Experiment Charter (Template)

Use this one-page form for every experiment:

• Experiment Name
• Owner (person accountable)
• Start / End Dates
• Hypothesis (If we do X, then Y will change by Z)
• Primary Metric and data source(s)
• Success Criteria (numeric) and Minimum Detectable Effect
• Actions to Run Test (step-by-step)
• Controls / Things to Keep Stable
• Risks / Mitigations
• Stakeholders to Notify

Weekly Checkpoint Agenda (30 minutes)

1. Quick Metrics Review (5 min): primary metric, any safety/guest-impact flags.
2. What happened this week (8 min): observations, issues, qualitative feedback.
3. Decide (10 min): continue / modify / stop / scale — based on pre-defined success criteria.
4. Actions & owners (5 min): who does what before next checkpoint.

Key Success Metrics (Examples)

• Net margin change (primary outcome)
• Food cost % by week and by item
• Waste weight/value per day
• Labor cost % and covers per labor hour
• Ticket times and remake rates
• Guest satisfaction/comments related to tested changes

Quick Audit Checklists (Discovery Tools)

Short checklists you can complete in 1–3 hours:

• Receiving Audit: deliveries matched to invoices, spot-checks of unit counts and temperatures.
• Portioning Audit: weigh portions for top 5 items vs recipe card.
• Waste Walk: record waste streams and approximate weights during a full service period.
• Ticket Time Sample: track 20 tickets across service periods for prep and ticket-to-table times.

Common Pitfalls & Tips

• Don’t run too many experiments. Three well-run experiments beat ten half-tracked ones.
• Measure before you change. Weak baselines make results meaningless.
• Protect guest experience. Pilot changes quietly then scale fast once validated.
• Bring frontline staff into design—adoption is often the biggest barrier.

Sustainment Handoff Checklist

• One-page SOP created and stored in operating binder or knowledge base.
• Training completed for all shifts (signed acknowledgment or short quiz).
• KPI monitoring assigned with thresholds and escalation path.
• 30/60/90 day verification scheduled.

Next Steps & Suggested Toolkit

Start with a two-week discovery, complete the three quick audits, then run a prioritization workshop. If you want to embed this Journey into your team space, consider adding an experiment tracker, a one-click Experiment Charter form, and a small KPI dashboard so owners can view live progress.

Image suggestion: team working on profit improvement plan