90‑Day Profit Improvement Workbook — Cross‑Functional Plan, Agendas & Trackers
A practical, editable workbook and meeting cadence to run a focused cross‑functional 90‑day profit improvement program. Includes a sprint-style structure, KPI huddle and experiment-review agendas, ready-to-use trackers for KPIs, experiments, owners and risks, and a short communications and recognition plan to keep staff engaged.
Purpose and outcome
This workbook helps a small team (operations, culinary, finance/GM) run a structured 90‑day profit improvement program that produces measurable margin gains. The intent is concrete: run a short series of rapid experiments, focus daily and weekly attention on a small set of KPIs, assign owners, remove obstacles, and embed wins into standard work so gains last.
Who should use this
Store managers, general managers, kitchen leads, chefs, controllers or operators of single or multi‑site businesses who want a repeatable cross‑functional process to raise margins within 90 days.
What success looks like
- Clear 90‑day margin target (e.g., +1.5 percentage points gross margin or $X/week improvement).
- 3–6 prioritized experiments in flight with named owners and measured outcomes.
- Weekly KPI huddles with a visible scoreboard and corrective actions.
- Documented changes captured as standard work so gains endure.
90‑Day structure (overview)
- Week 0 — Launch & baseline: set targets, baseline KPIs, assign owners, and agree cadence.
- Weeks 1–12 — Execute in three 4‑week cycles: propose experiments, run, measure, iterate, and scale or stop.
- End of Day 90 — Consolidate wins, update SOPs, set sustainment checks, and plan next cycle.
Core weekly cadence (recommended)
- Daily quick check (10 minutes): ops lead and shift leader—review yesterday's sales vs forecast, high‑impact issues (waste, outages, staffing), and any immediate containment actions.
- Weekly KPI huddle (45–60 minutes): cross‑functional team—review scoreboard, experiment progress, decisions, and owner commitments.
- Biweekly experiment review (30–45 minutes): deep dive on 2–3 experiments—what worked, data, and next steps.
Weekly KPI huddle agenda (template)
- Opening & quick wins (5 min): recognition from last week.
- Scoreboard review (15 min): discuss trends for each KPI — sales, COGS%, labor%, waste $/day, ticket times, and any site‑specific KPI.
- Experiment status (15 min): owner reports (RAG: Red/Amber/Green), immediate data, and ask for resources/decisions.
- Risks & blockers (5 min): items needing escalation.
- Decisions & actions (10 min): assign owners, deadlines, and measurable acceptance criteria.
Key KPIs to track (starter set)
Pick 4–6 metrics that most directly influence margin for your operation. Examples:
- Weekly sales (net)
- Food cost % (COGS %), tracked daily/weekly
- Labor cost %
- Waste dollars per day (spoilage, prep waste, production waste)
- Ticket time / throughput (if throughput affects staffing or service)
- Number and value of menu remakes / voids
Define how each KPI is calculated and the data source (POS, inventory counts, payroll, waste logs).
Scoreboard (how to set up)
Create a single visual that shows baseline, current week, target, and variance for chosen KPIs. Update it weekly for the huddle and post a simplified version for the team.
Columns: KPI name | Baseline | Target (90d) | Current week | Week over week change | Owner
Experiment log (template)
Use one row per experiment. Keep experiments small, observable, and time‑boxed (1–3 weeks where possible).
- Experiment name
- Hypothesis (If we do X, then Y will change by Z)
- Primary metric (and how it is measured)
- Owner
- Start date / end date
- Resources required
- Outcome (quantitative result) and decision (Scale / Iterate / Stop)
Owner templates (example areas)
- Inventory owner — weekly cycle counts, receiving checklist, reorder alerts.
- Labor owner — schedule optimization experiment, cross‑training plan.
- Menu owner — portion control audit, recipe standardization, price checks.
- Waste owner — daily waste log, hot/cold hold checks, prep change experiments.
Risk register (short)
Track the highest priority risks that could derail the 90‑day plan and the contingency actions.
- Risk description
- Likelihood x impact (High/Medium/Low)
- Mitigation owner & action
- Status
Communications & staff engagement
Keep the team informed and involved. Simple ideas:
- Weekly one‑page update after KPI huddle (what changed, what we tried, who won).
- Shift briefings that link daily checks to the 90‑day goals.
- Publicly recognize small wins (digital board, sticker, short shoutout at shift change).
Short checklist to start Week 0
- Agree 90‑day margin target and the KPIs that matter.
- Collect baseline data for 4 weeks where possible, or use most recent steady period.
- Form the cross‑functional core team and assign a program lead.
- Schedule weekly huddles and owner touchpoints.
- Create a shared scoreboard (sheet or simple dashboard).
- List candidate experiments and rank by expected impact & ease.
Sustainment & next steps after Day 90
Document changes as SOPs, transfer ownership to daily managers, set monthly sustainment checks, and plan the next 90‑day cycle with adjusted targets.
Where to adapt this workbook
This is a starter structure. Tailor KPI definitions, experiment cadence, and owner roles to your business size and data availability. Keep experiments small and data‑driven: the faster you measure, the faster you learn.
Templates to copy
Below is a short list of copyable templates you should create in your shared docs or platform space before launching:
- Scoreboard sheet (one tab per KPI + leaderboard)
- Experiment log (one row per experiment)
- Weekly huddle agenda with action tracker
- Daily quick check form for shift leads
- Risk register
Quick tips
- Limit scope early—fix a few high‑impact areas rather than many small ones.
- Use owners with authority to act and clear escalation paths.
- Measure using the simplest reliable data source first (e.g., POS and daily waste log).
- Celebrate small wins publicly to sustain momentum.
Notes: This workbook is intentionally platform‑agnostic. If you want an interactive version that collects experiment results, stores weekly submissions, and drives a live scoreboard inside the platform, consider adding interactive trackers and saved forms so the system can store progress and generate reports.
Discussion
Comments and conversation will live here.