90-Day Profit Improvement Journey Plan

Overview

This 90-day journey is a short, time-boxed program to find measurable profit improvements you can test quickly and lock into everyday operations. It combines a fast discovery phase, rapid experiments, weekly huddles that keep momentum, a mid-point review, and a scale-and-sustain phase. The plan is designed for restaurants and food service teams of any size and intentionally focuses on changes that can be tested with limited risk and clear metrics.

Core principles

• Keep experiments small, measurable, and owner-assigned.
• Use data-driven diagnostics before proposing fixes.
• Decide quickly: adopt, iterate, or stop based on simple acceptance criteria.
• Document learnings so improvements persist after the 90 days.

Roles & responsibilities

• Journey Sponsor (Owner): Area manager, GM, or owner who approves resources and removes barriers.
• Journey Lead (Operator): Oversees day-to-day execution, runs weekly huddles, tracks KPIs.
• Data Lead: Pulls POS, inventory, labor, and waste numbers for diagnostics and KPIs.
• Experiment Owners: Short-term owners for each experiment (chef, shift leader, purchasing lead).
• Team Members: Staff who execute experiments and provide feedback.

Week-by-week agenda (high level)

Weeks 1–2 — Discovery & Quick Diagnostics

Goal: Identify the highest-impact profit opportunities using data and frontline observation.

1. Data pulls: last 12 weeks of POS sales mix, food cost by category, top-selling items, labor hours, shift-level sales, and inventory variances.
2. Walk the workflow: receiving, prep, line, service, and waste areas. Note bottlenecks and obvious waste sources.
3. Short interviews: ask cooks, servers, and managers what they see as biggest loss points.
4. Prioritize 4–6 candidate experiments by expected impact, ease of test, and risk.

Weeks 3–7 — Rapid Experiments & Weekly Huddles

Goal: Run short, focused experiments (1–2 week tests) with clear metrics.

• Run experiments in parallel where they don't conflict (e.g., one menu change + one prep change).
• Hold a short weekly huddle (15–30 minutes) to review results, surface blockers, and assign next actions.
• Examples of experiments:
  • Menu: delist low-margin, low-volume items for two weeks; promote high-margin items with minor plating or upsell prompts.
  • Portion control: introduce portioning tools or pre-portioned pans for a subset of items.
  • Waste reduction: targeted waste tracking for one prep station or shift.
  • Scheduling: shift a small amount of labor between low and high-demand windows and measure throughput and guest satisfaction.
  • Receiving & storage: tighten receive checks on one supplier to reduce spoilage and invoice errors.

Week 8 — Mid-point Review

Goal: Decide which experiments to scale, which to iterate, and which to stop.

Review all experiment outcomes against decision rules (see below). For experiments that meet acceptance criteria, create a scale plan and assign owners to embed changes in standard work.

Weeks 9–12 — Scale, Standardize & Lock-in

Goal: Roll out successful experiments, update SOPs, train staff, and stabilize KPIs.

1. Scale proven experiments to all shifts/locations where appropriate in a controlled way.
2. Update recipes, checklists, opening/closing procedures, and training materials.
3. Set monitoring cadence and KPIs to ensure the improvement sustains beyond the journey.

Weekly huddle format (15–30 minutes)

1. Quick metrics snapshot (3 minutes): sales, food cost % (or daily food cost $), waste incidents logged, labor hours vs forecast.
2. Experiment updates (5–10 minutes): owners report results, learnings, and blockers.
3. Decisions (5 minutes): continue, scale, stop, or modify—assign next steps.
4. Operational items & shout-outs (2–5 minutes): issues requiring sponsor attention and recognition for team wins.

Experiment template (use for documentation)

Keep each experiment simple and recorded so it can be reviewed and repeated.

• Title: concise experiment name
• Owner: person responsible
• Hypothesis: If we [change], then [expected outcome] because [rationale].
• Duration: 1–2 weeks
• Metrics to track: primary metric (e.g., item food cost %, units sold, waste kg), secondary metrics (guest ratings, ticket time, labor minutes)
• Acceptance criteria: clear thresholds for success (example: reduce waste from target station by 20% and maintain guest satisfaction scores)
• Data sources: POS, inventory counts, waste log, manager observations
• Risks & mitigations: potential guest impact, supply constraints, staff training
• Result & next step: adopt / iterate / stop + notes

Recommended KPIs & sample targets (use as starting points)

Targets should reflect your baseline and ambition. These examples are illustrative — set realistic thresholds based on your data.

• Food cost % (weekly): aim to reduce by a measurable margin (e.g., 0.5–3 percentage points depending on opportunity).
• Waste weight or cost (weekly): track and aim for a step reduction (e.g., 10–30%) in target areas.
• Sales mix of promoted high-margin items: increase % of sales for those items.
• Labor hours per cover or per sales dollar: small improvements without hurting service quality.
• Order accuracy / remakes rate: maintain or improve while changes occur.
• Experiment win rate: percent of experiments adopted (reasonable target: 30–60% — depends on risk tolerance).

Decision rules

Simpler decision rules keep momentum. Examples:

• Adopt if primary metric improves AND no meaningful negative impact on guest satisfaction or throughput.
• Iterate if metrics show partial improvement but execution issues are blocking full benefit.
• Stop if no measurable benefit or if guest impact is negative.

Data & tools

Use POS reports, inventory snapshots, shift-level labor reports, and a short waste log (paper or digital). Capture experiment notes after each shift. Where possible, centralize results in a simple spreadsheet or the platform's data collection forms so weekly huddles focus on meaning, not number-crunching.

Embedding improvements

• Update recipes, portioning SOPs, and prep lists immediately after adoption.
• Train at least two staff per shift to avoid single-person dependence.
• Assign a 30/60/90 day check to confirm persistence of benefits.

Common pitfalls & how to avoid them

• Too many experiments at once — keep experiments limited and non-conflicting.
• No clear owner — assign ownership and decision authority for each experiment.
• Poor data cadence — commit to a weekly snapshot to keep decisions timely.
• Failure to standardize — turn wins into SOPs and quick training blocks.

Next steps & templates

Start with a two-week discovery sprint, pick 4 experiments, assign owners, and schedule the weekly huddle. Use the experiment template above and keep all records so the mid-point review can be evidence-based.

Ready-to-copy checklist: discovery data list, 4 prioritized experiments, weekly huddle time, Owner/Sponsor named, experiment template filled for each experiment.