The job
A company is growing. The founder doesn’t know if the bottleneck is sales, delivery, or operations. The team feels stretched. The budget is getting squeezed. Someone spends a day pulling data from timesheets, project trackers, and accounting systems. They build a spreadsheet. They answer the question: where are we stuck. Then the next month someone does it again.
The dish reads the source data on a schedule. Where time is being spent across projects. How much work is billable versus overhead. Where projects are over budget or off schedule. It surfaces the patterns: this department is at ninety-five percent capacity. This project is consuming thirty percent of delivery time but generating five percent of revenue. This vendor is costing twice what we budgeted. It flags where the Chef needs to pay attention.
Plated well, this looks like: the Chef sees resource constraints before they break. The team isn’t surprised by budget overages. Decisions are made from data, not from whoever complained last. Overallocation is visible and addressable. The Chef allocates resources like a Chef allocates seasoning. Intentionally, based on what the dish needs.
The recipe
All seven ingredients still apply. The leverage is Measurement (Ingredient #6). The station needs to know what matters to measure. Not every metric. The ones that tell you if the business is functioning. Utilization by department. Revenue per hour by project. Cost variance by vendor. These are your load-bearing metrics.
Output Over Process (Ingredient #5) is the second lever. The destination isn’t “pull all the data.” It’s “show the Chef where the constraints are, in a format they can act on.” A dashboard. A memo. A ranked list of resource bottlenecks.
Context (Ingredient #2) is the third. The station needs to know where the data lives. How utilization is tracked. Which projects are strategic. Which are legacy. Examples (Ingredient #4) teach the station what “good analysis” looks like. Three past analyses you did. The metrics you chose. The patterns you called out. The actions those patterns led to.
How to build it
-
Define what you need to measure. Utilization by department. Revenue per hour by project. Cost variance by vendor. Capacity headroom. Project timeline status. Not every metric. The ones that tell you where to allocate next.
-
Identify the source data. Timesheet system. Project tracker. Accounting system. Which system holds which metric. Write down the data path for each.
-
Define the constraints that matter. Anything over ninety percent utilization is a flag. Any project over budget by ten percent is a signal. Any vendor costing more than twenty percent above budget is a problem. These thresholds are your guardrails.
-
Write three analyses by hand. Real analyses from the past three months. The data you pulled. The patterns you called out. The decisions they led to. This trains the station on what “actionable” looks like.
-
Define the output format. A dashboard that updates weekly. A memo landing in Slack. A spreadsheet. Define where and when the analysis lands.
-
Set the schedule. The analysis runs every Friday at 4 PM. The Chef reviews Saturday morning. By Monday, decisions are made on current data.
-
Run a test cycle. Have the station run the analysis for last month. Compare it to the one you would have written. What did it catch. What did it miss. Where does the measurement need sharpening.
-
Measure the outcomes. Did the analysis surface a real constraint. Did the Chef act on it. By week four, is the data shaping decisions.
What breaks it
-
Metrics are disconnected from action. The analysis says “department X is at ninety percent utilization” but nobody knows what to do about it. Measure what you can actually change.
-
The measurement definition is fuzzy. Utilization could mean hours booked or hours productive. Cost variance could be actual minus budget or actual minus forecast. If you don’t define it, the station guesses. Numbers diverge month to month.
-
Data is stale. The timesheet system was last updated three days ago. The project tracker hasn’t been touched in two weeks. The analysis is showing old reality. The Chef makes decisions on lagging data.
-
No feedback loop. The analysis surfaces a constraint. The Chef acts. The next month’s analysis doesn’t reflect whether that action worked. The station never learns what constraints actually matter.
When it’s working
By week one, the analysis lands on time. Seventy percent of the metrics are clean. Thirty percent need a spot-check or definition sharpening. By week two, the data is trusted. The Chef is making decisions based on what the analysis shows. By week three, the analysis is being used proactively. When a project starts looking over budget, the team already knows because the analysis caught it. By week four, the analysis is a routine input to the Monday resource planning call. The Chef allocates based on data, not on guesses.
The signal that the recipe is sharp: the station surfaces a constraint before anyone asks about it because the measurement was sophisticated enough to catch the pattern early.
Monday Move
Pull the data for last month the way you normally would. Utilization. Revenue. Cost variance. Build the analysis. Show the station. Have it build this month’s analysis while you watch. Where does it match your logic. Where does it miss the pattern. What measurement definition needs to sharpen.
Dish 9 of 10 on the Operations Station. Build-note leverage: Measurement (Ingredient #6).