Here are some of the best free or free-tier tools fast-casual teams can use to test and improve throughput, kitchen flow, and bottleneck reduction. I’ve grouped them by use case so you can mix and match based on what stage you’re in.

1) Process mapping and workflow analysis

These help you visualize the current kitchen flow and identify delays.

• diagrams.net (Draw.io)
  Best for: process maps, swimlanes, station layouts, spaghetti diagrams
  Why it’s useful: free, easy to share, works in browser, good for mapping order flow from ticket to handoff.

• Lucidchart free plan
  Best for: simple flowcharts and collaboration
  Why it’s useful: useful for teams already in Google Workspace or Slack, though the free plan is limited.

• Miro free plan
  Best for: collaborative brainstorming, whiteboarding, affinity mapping
  Why it’s useful: good for teams sketching changes to prep, expo, make line, and handoff flow.

2) Time study and stop-watch style measurement

These are good for measuring step durations, ticket times, and station cycle times.

• Google Forms + Google Sheets
  Best for: manual time studies, order timing logs, simple data collection
  Why it’s useful: completely free, easy to create a quick timestamping form for testers to log order start/end times, delays, and notes.

• Airtable free tier
  Best for: structured time study data, lightweight databases
  Why it’s useful: better than spreadsheets for logging tasks, stations, and timestamps with a cleaner interface.

• Toggl Track free plan
  Best for: tracking how long tasks or experiments take
  Why it’s useful: useful when a manager or team lead is observing and wants quick duration tracking, though it’s more general-purpose than kitchen-specific.

3) Video observation and annotation

Very useful for kitchen workflow testing because you can review the same run multiple times.

• Google Drive / Dropbox basic storage
  Best for: storing test-run videos
  Why it’s useful: easy sharing and review.

• Loom free plan
  Best for: recording short walkthroughs or annotated observations
  Why it’s useful: good for narrating what changed in the workflow and what the team noticed.

• OBS Studio
  Best for: recording longer video from a phone capture or screen overlay
  Why it’s useful: completely free and powerful for recording test sessions.

4) Data analysis and visualization

Use these to identify before/after effects of changes.

• Google Sheets
  Best for: averaging ticket times, calculating percent improvements, pivot tables, charts
  Why it’s useful: probably the most practical free tool for throughput experiments.

• Looker Studio
  Best for: dashboards and trend visualizations
  Why it’s useful: free, and it can pull from Sheets to create easy-to-read performance dashboards.

• Microsoft Excel Online
  Best for: teams in Microsoft 365 ecosystems
  Why it’s useful: free web version is good for basic analysis.

5) Lean / operations improvement support

Useful if you’re using more formal continuous improvement methods.

• Kanban boards in Trello free plan
  Best for: tracking experiments, action items, and follow-ups
  Why it’s useful: helps teams organize test hypotheses, changes, and results.

• Notion free plan
  Best for: experiment logs, SOP drafts, improvement notes
  Why it’s useful: great for keeping a central “workflow improvement” hub.

• ClickUp free plan
  Best for: task management plus documentation
  Why it’s useful: good for coordinating kitchen test projects, though it can be a bit heavier.

6) Basic statistical and simulation tools

If you want to get more rigorous about results.

• Google Sheets with formulas
  Best for: basic significance checks, averages, percentiles, control charts
  Why it’s useful: enough for many restaurant test cycles.

• R / RStudio Desktop
  Best for: deeper analysis, control charts, process capability, queue analysis
  Why it’s useful: free and powerful if someone on the team is analytically inclined.

• Python in Google Colab
  Best for: scripting analysis and simple simulations
  Why it’s useful: free, browser-based, and good for modeling order flow or station capacity.

---

Best “starter stack” for most fast-casual teams

If you want the simplest effective setup, I’d recommend:

1. diagrams.net for mapping current and future-state flow
2. Google Forms + Sheets for collecting time study data
3. Looker Studio for reporting results
4. Trello or Notion for managing experiments and action items
5. Phone video + Google Drive for reviewing test runs

---

What to measure in a throughput test

Regardless of the tools, track these metrics:

• Ticket time: order placed to order complete
• Station cycle time: time per station step
• Queue time: time waiting before a station starts work
• Touches per order: number of handoffs or re-handlings
• Bottleneck duration: how long a station is backed up
• Error/rework rate: remakes, missing items, corrections
• Peak vs. off-peak performance

---

Quick recommendation by team maturity

• Small team, low budget: Google Forms, Sheets, diagrams.net, Trello
• More collaborative team: Miro, Notion, Looker Studio
• More analytical team: Sheets, Python/Colab, RStudio, video review
• Multiple locations: Airtable, Looker Studio, Notion, shared Drive folder

If you want, I can also give you:

• a free tool stack by budget and team size, or
• a sample throughput test template you can use in a fast-casual kitchen.