Personal Productivity OEE
Score your own day the way a factory scores a machine - Availability × Performance × Quality.
OEE decomposes machine downtime into three separate losses instead of one vague "productivity" number. Applied to a personal day, it does the same thing - and usually reveals that the real leak isn't effort, it's availability or rework.
01 /
The Problem.
// "I was busy all day but got nothing done"
A vague sense of "productive" or "not productive" doesn't tell you what to fix. Was the problem that you didn't have enough time available? That you worked slower than planned? Or that you did the work but had to redo half of it? Each of those needs a completely different fix.
OEE forces that decomposition on a shop floor. This project forces the same decomposition on a personal day.
02 /
Methodology.
// three ratios, multiplied
Availability
Actual Hours Worked / Planned Hours. Lost to interruptions, meetings, or simply not
starting - time that was never available to begin with.
Performance
Tasks Completed / Tasks Planned. Of the time you actually had, how much of the
planned output did you hit - the "speed" loss.
Quality
(Completed − Reworked) / Completed. Work that had to be redone or abandoned
counts against you exactly like a defective part does on a line.
Personal OEE
Availability × Performance × Quality. The same 85% "world-class"
benchmark from manufacturing applies - most days land nowhere close, and that's diagnostic.
03 /
What’s in the build.
// shipped features
One log per day
Planned/actual hours and planned/completed/ reworked tasks - that's the whole daily input.
Automatic A/P/Q breakdown
Each day shows all three component ratios, not just the final OEE number, so you know which one to fix.
Live trend chart
An inline SVG bar chart of daily OEE against the 85% world-class benchmark line.
Rolling average
Tracks your average OEE across all logged days, not just the most recent one.
Sample week
Preloaded 7-day sample so you can see the pattern before logging your own days.
Local persistence
Your log is saved in the browser between visits - nothing is sent anywhere.
04 /
Stack & Outcome.
// what it took, what it shipped
Stack
Outcome
A week of logging usually shows the same lesson factories learn: most personal "productivity" loss isn't a motivation problem, it's an availability or quality problem - and now it's visible.
Live Tool