Dilip Waghmare · Maintenance
Corto drafted this. Everything below is the case for it, out of records that already existed — and the last section is what Corto cannot stand behind.
Drafted by Corto from the founder's expectation of Maintenance and agreed by him. Dilip has not opened Corto, so nobody has entered anything on his behalf and he has not seen it.
Where it came from
A goal Corto proposed has a reason it exists. This is that reason, with the record behind it.
No finding sits behind this one. It was written by its owner rather than proposed from the diagnosis, which is not a fault — but it means Corto cannot tell you why it exists, only whether it holds up.
It serves Less of the company depends on any one customer's decision., a company goal.
What Corto read
2Every record under every number in this goal — where it came from, how it was read, and when it was true.
What each person entered about themselves when they joined
the company's own figure, not a recordUsed for: A breakdown log live on the connected drive by 19 September
- The record
- What they gave about themselves — role, what they do, what they are good at
- How read
- typed or tapped by the person in their own words; nothing was renamed or inferred for them
- True as of
- 26 Aug 2026 · refreshed when a person edits their own details
Daily Production Log (shared drive), registered cadence-only
from a filed or system recordUsed for: Unplanned downtime: 38 → 15 hours a month
- The record
- Daily Production Log.xlsx - merged cells and formula columns; content parsing off
- How read
- cadence observation of the tenant's own file; contents deliberately not parsed
- True as of
- 26 Aug 2026 06:20 · refreshed daily
Why these key results are enough
If every one of them lands, is the goal true? If the answer is no, the goal is measuring the wrong things.
Taking on a new customer means promising capacity, and capacity the company cannot rely on is capacity it cannot promise. A breakdown log and a service schedule that is actually followed are what this department owes that promise.
Is it a good goal
4 of 5SMART, checked against the goal itself. Where Corto asks more than SMART does, it says so — it is not a badge, it is what was actually tested.
- S
Specific
holdsThe goal names a change, and leaves every number to its key results.
SMART asks a goal to be specific. Corto asks it to be specific WITHOUT a number in it, so the target can move without rewriting what the company is trying to do.
- M
Measurable
holdsAll 3 key results carry a start value, a target, a unit and the record they are read from.
SMART asks for a number. Corto asks WHERE THE NUMBER COMES FROM — the actual record — because a target nobody can read is not measurable, it is only numeric.
- A
Achievable
not yet3 key results read from something that does not exist yet, so the goal cannot be scored at all.
Corto does not judge whether an ambition is realistic — that is the founder's to set. It checks the two things it can see: that somebody is working on it, and that the number can actually be read.
- R
Relevant
holdsIt serves “Less of the company depends on any one customer's decision.”, which is a company goal.
SMART asks whether a goal matters. Corto asks WHAT IT SERVES, by name, all the way up to one of the three destinations — so relevance is a chain you can follow rather than an opinion.
- T
Time-bound
holdsIt runs to Oct – Dec 2026, and nothing is scored before that period begins.
What Corto cannot stand behind
7Read this before you argue with anybody using the rest of the page. A case that states no limit is a sales sheet.
What each person entered about themselves when they joined — the company's own figure, not a record
This is the company's own figure, not a filed or system record. Anything resting on it inherits that.
What What each person entered about themselves when they joined cannot tell you
what a person is accountable for, which is their manager's to sayhow well they do any of itanyone who skipped the screena measurement of anything — this is description, not data
What Daily Production Log (shared drive), registered cadence-only cannot tell you
quantity producedline or machine outputcapacity utilisationrejection or rework rateanything at all about the contents of the file
“A breakdown log live on the connected drive by 19 September” cannot be scored
No drive is connected for Maintenance. There is nowhere for the log to be live.
“Planned service done on schedule on the four main machines” cannot be scored
The instrument is the joining wizard, and Maintenance has completed 0 of 1 — the 1 being Dilip himself.
“Unplanned downtime: 38 → 15 hours a month” cannot be scored
The production log records cadence only; stoppage hours are not in it. This is gap-utilisation in the plan.
Dilip has not accepted this
It was agreed by whoever rules on it, not by the person who has to deliver it. Nothing is measured against it until they say yes.
Assembled from records that already existed — the diagnosis, the interview, the derivation registry and the goal itself. Nothing on this page is written about the goal after the fact. The line to the destination