90‑Day Profit Improvement Plan

Overview

This 90‑day Profit Improvement Plan is a focused, cross-functional sequence you can follow to find where profit is leaking, test the highest‑impact fixes, and lock in measurable margin gains. It is designed for busy restaurant and hospitality teams who need clear, short cycles of action, measurement, and decisions—not more meetings.

Core Outcomes

• Identify 3–6 highest‑impact profit opportunities (food, labor, waste, pricing, throughput).
• Run prioritized experiments with clear owners and success criteria.
• Deliver measurable margin improvement within 90 days and create a repeatable playbook.

Who Should Be Involved

Keep the team small but cross‑functional: a Sponsor (GM/Owner), Program Lead (ops manager), Finance Lead (bookkeeper/analyst), Kitchen Lead (chef/manager), FOH Lead (floor manager), and one shift representative. Assign a Data Steward to gather baseline and experiment data each week.

How This Journey Works

Organize the 90 days into three overlapping phases: Diagnose (weeks 1–2), Pilot & Iterate (weeks 3–8), Scale & Sustain (weeks 9–12). Use short weekly huddles, simple experiment cards, and a lightweight governance rhythm so actions are fast and accountable.

Experiment Card (use this for every test)

Every experiment owner should complete a single card with these fields:

• Title
• Owner
• Hypothesis (If we X, then Y will improve by Z)
• Baseline metric and source (food cost %, $ waste/day, labor hours, average ticket, etc.)
• Target and success criteria
• Duration (typical 1–3 weeks)
• Actions (what will change, who trains, what signage/SOPs)
• Data collection (who collects, frequency, where stored)
• Risks & mitigations

Week‑by‑Week Plan

Weeks 1–2: Diagnose & Prioritize

• Collect baseline metrics: weekly sales by period, food cost %, labor % by shift, daily waste log (by category), ticket time, and key inventory variances.
• Run 1–2 listening sessions: brief shift interviews and one customer insight check (quick survey or review scan).
• Map the top value streams (menu categories, busiest dayparts) and spot obvious leaks (over‑portioning, slow stations, inaccurate schedules).
• Create a short list of 6–8 candidate experiments and score them by expected impact, effort, and risk (impact/effort matrix). Pick 3–4 for the pilot phase.

Weeks 3–8: Pilot, Measure, Iterate

• Run parallel small experiments—each with a single owner and clear measurement. Typical pilots: portion control training, targeted menu price/portion change, shift start-time adjustments, simplified prep lists for rush, targeted waste capture and weighing station, and focused receiving/ordering changes.
• Hold a weekly 30‑minute Profit Huddle. Each owner gives a 5‑minute status: data, quick learnings, blocker, recommended next step (stop/adjust/scale).
• Document learnings on the experiment card and update baseline metrics weekly.
• Stop experiments that don't move the needle after their agreed duration; scale and standardize those that do.

Weeks 9–12: Scale & Sustain

• Take successful pilots and convert them to standard work: updated recipes, training checklists, schedule templates, inventory par lists, and supplier notes.
• Build a simple one‑page Profit Playbook with the top 5 proven changes, owners, and monitoring cadence.
• Run a 90‑day review with Sponsor, share measured margin gains, and set the next 90‑day improvement cycle (continuous improvement cadence).
• Create a lightweight governance plan to prevent slippage: weekly checking leader, monthly metrics review, quarterly re‑scan.

Example Quick Wins (fast to test)

• Portion control: weigh one menu item for 3 shifts, correct training, measure food cost change.
• Small price adjustment on low‑frequency high‑margin items with signage and staff script.
• Optimize the late‑night schedule by trimming overlap 1 hour and measuring labor cost vs. check averages.
• Receiving SOP tweak: check ONE high‑value SKU daily for variance; reduce over‑ordering.
• Waste station & daily weigh: capture prepped but unsold items for 2 weeks to find repeatable causes.

Key Metrics & Data Sources

Track these at minimum:

• Food cost % (weekly and rolling 4‑week)
• Labor cost % and hours per cover
• Average check and covers by shift
• Waste weight and $ loss by category
• Ticket time / throughput during peaks
• Inventory variance (receiving vs. recorded usage)

Primary sources: POS reports, inventory counts, daily waste logs, time‑clock exports, and supplier invoices.

Governance Cadence

• Weekly Profit Huddle (30 minutes): status, blockers, decision to stop/scale.
• Data check (Data Steward): update dashboard before huddle with latest week vs baseline.
• Midpoint review at day 45 to re‑prioritize experiments and reallocate resources.
• 90‑day review with Sponsor: finalize scaled changes and embed playbook.

How to Decide: Stop, Adjust, or Scale

1. Compare the metric to the target and expected variability band.
2. If improvement is below threshold and no operational problems solved, stop and document learning.
3. If partial improvement or operational issues, adjust the action and re‑test for one more short cycle.
4. If success criteria met and operationally stable, standardize, train, and monitor.

Embedding Improvements

Turn successful experiments into short SOPs, quick training scripts, recipe cards, and shift checklists. Add the top items to your onboarding and pre‑shift brief. Make sure one person owns monitoring and that the metric is visible weekly.

Common Pitfalls to Avoid

• Trying to fix everything at once—focus on highest impact experiments.
• Confusing activity with results—measure the metric you care about.
• Letting ownership fade—assign and publicize experiment owners.
• Not documenting learnings—capture both data and operational context.

Next Steps & Templates

Start by scheduling a 90‑minute kickoff in week 1 to collect baseline numbers and pick your 3 pilot experiments. Use the Experiment Card template for each test and assign a Data Steward.

At the end of 90 days, convert the playbook into a living domain for your team so future locations or teams can copy and run the same journey.