90-Day Profit Improvement Program (Cross-Functional Journey) — Playbook, Week-by-Week Plan & Experiment/Review Forms

Welcome — What this Journey Is For

This 90-day cross-functional journey is a structured way for your restaurant or food service team to diagnose the biggest profit opportunities, run focused experiments, and turn successful changes into reliable operating practice. It’s designed to produce measurable margin improvement while protecting guest experience and team capacity.

Intended outcome

Deliver measurable margin improvement in 90 days by running short, hypothesis-driven experiments, stabilizing wins, and embedding changes into standard work.

How to use this Journey

Keep the program pragmatic: pick a handful of experiments your team can operate and measure consistently. Use daily huddles and weekly reviews to keep momentum. Treat data as feedback, not judgment. Use the interactive fields below to record experiment definitions, daily huddle snapshots, and diagnostic baselines. Submitting an experiment or huddle saves it to the project record so your team can review progress and share learnings.

High-level cadence

• Week 0 (Preparation & Diagnostic) — Baseline metrics, form the team, identify quick wins and risks, prepare communications.
• Weeks 1–3 (Quick Wins) — Run short experiments that require little investment but can quickly improve margins (portion control, waste capture, menu nudges).
• Weeks 4–8 (Medium-impact Projects) — Implement slightly larger changes that need coordination (inventory accuracy, recipe standardization, scheduling tweaks).
• Weeks 9–12 (Scale & Standardize) — Hardwire successful experiments into SOPs, training, dashboards, and roll out to other shifts/locations as appropriate.

Roles & RACI (example)

• Sponsor (owner/GM) — Accountable: approves priorities and resources.
• Project Lead (ops manager) — Responsible: runs the journey, coordinates owners, reports progress.
• Kitchen Lead — Responsible for kitchen experiments and training.
• Front-of-House Lead — Responsible for guest-facing or service experiments.
• Finance/Data Steward — Consulted: provides baseline KPIs, tracks results.
• Purchasing/Supply — Consulted: supports supplier actions and cost changes.
• Communications Lead — Informed/Responsible for team messages and briefings.

Core metrics and KPI guardrails

Track an outcome metric and a few guardrails to avoid unintended consequences.

• Primary outcome: Net margin or gross margin points (define how you calculate margin).
• Food cost % — daily/weekly monitoring.
• Labor cost % — watch changes as you shift tasks or schedules.
• Waste dollars or weight per day — simple waste log helps convert weight to dollars.
• Guest experience guardrails — NPS, star rating, or simple daily guest comments; also ticket times and remakes %.
• Sales volume — keep an eye for revenue displacement from price or menu changes.

Set reporting cadence: daily huddle snapshot, weekly review with numbers, and biweekly project review with the Sponsor.

Week-by-week plan (practical checklist)

Week 0 — Diagnostic & setup

1. Assemble the cross-functional team and confirm Sponsor and Project Lead.
2. Capture baseline data for the last 4–8 weeks: sales by hour/item, food cost, labor, waste, remakes, average ticket.
3. Run a rapid opportunity scan: 15–30 minute kitchen walkthrough and FOH walkthrough to list visible wastes and friction points.
4. Prioritize experiments into Quick Wins and Medium Projects (use impact × effort).
5. Create an experiment backlog and assign owners with timelines.
6. Prepare communications: launch note to staff and daily huddle agenda template.

Weeks 1–3 — Quick wins (2–3 week experiments)

Run 3–6 short, data-backed experiments. Examples:

• Portion control clampdown: verify portions on 30 tickets per shift; retrain if variance > 10%.
• Waste capture pilot: use a simple kitchen waste log for 7 days and calculate dollar loss.
• Menu placement nudge: highlight a higher-margin item with the server script for two weeks.
• Reduce free giveaways and comps: set a clear policy and measure frequency.
• Prep list optimization: reduce over-prep by aligning prep to forecasted demand for the next two weeks.

Weeks 4–8 — Medium-impact projects

Start projects that require coordination and training:

• Inventory accuracy push: weekly cycle counts for high-value SKUs and reconcile issues.
• Recipe and plate standardization: create or refine SOPs and train two cooks per shift.
• Supplier review: renegotiate pricing for top SKUs or consolidate orders to reduce freight/waste.
• Scheduling experiment: test staggered shifts or micro-forecasts to reduce labor during slow windows.
• Quick equipment fixes: eliminate bottlenecks causing remakes or ticket delays.

Weeks 9–12 — Scale, standardize, and sustain

1. Choose successful experiments to standardize into SOPs, checklists, and training modules.
2. Create simple job aids and run train-the-trainer sessions.
3. Build a one-page dashboard that shows the primary outcome metric and guardrails for daily shift review.
4. Formalize the handoff: who will own ongoing measurement, how often results are reported, and how new locations/shifts adopt the change.
5. Celebrate wins and document lessons learned for future cycles.

Experiment (mini) playbook — use this card for every experiment

Every experiment should use the same lightweight structure so results are comparable and learnings are captured.

• Name: clear and short.
• Owner: who runs it day-to-day.
• Hypothesis: if we do X then Y will change by Z metric in N days.
• Metric(s): primary outcome and 1–2 guardrails.
• Duration: 7–21 days typical for quick wins.
• Success criteria: numeric threshold or decision rule to adopt/iterate/stop.
• Steps: concrete actions, who trains, who measures.
• Notes & lessons: short log of what happened each day/shift.

Communication templates

Launch note to staff (example)

'Team — Starting Monday we’re running a 90‑day profit improvement program to sharpen our operations and protect everyone’s jobs and hours. We’ll try small changes and check results together. If you have ideas, bring them to the daily huddle. Our goal is to improve margins while keeping great service. — GM'

Daily huddle script (example, 5 minutes)

1. Quick metrics: sales, covers, any inventory or equipment issues.
2. What we tried yesterday and what changed.
3. Today’s focus and owner.
4. Safety or quality flags.

Handoff & scale checklist (short)

1. Results summary: before/after numbers, sample size, and confidence in results.
2. SOP or job aid attached.
3. Training plan: who trains who, when, and how competency is verified.
4. Dashboard widget or tracker set up and owner assigned.
5. Review date for ongoing measurement assigned (weekly/monthly).

Common mistakes and how to avoid them

• Running too many experiments at once — focus on a small portfolio and measure well.
• Not defining success criteria — decide ahead how you’ll judge results.
• Losing the guest experience — always include a guest-facing guardrail metric.
• Poor data hygiene — ensure sales and inventory data are reconciled before you draw conclusions.

What success looks like

Short‑term: clear wins on at least one primary metric with no deterioration in guest experience. Medium‑term: a handful of SOPs and one-page dashboards that keep the improvement in place. Long‑term: a cultural rhythm where the team runs short experiments regularly and shares learnings across shifts or locations.

Next steps

Start by running the Week 0 diagnostic and creating 3 experiment cards. Use daily huddles to keep measurement honest and the project lead to run weekly reviews with the Sponsor. Use the interactive forms below to save experiment definitions and daily huddle snapshots to the project record.

End of journey.