← Selected workAll work

Analysis, Shipped, Ultranative

Measuring one seat: a six-source workload audit

When the workload question came up, I measured instead of estimating: every calendar event parsed programmatically, 135 recorded meetings, sampled mail, Slack, 867 build-session transcripts, and commits across 14 repos — overlaps merged so nothing counted twice. The result sized the seat at sixteen distinct functions, each with its hours accounted for.

  • The method is the point: union of calendar and verified build activity, parallel sessions merged, travel and phone excluded and declared as understated.
  • The finding: sixteen distinct functions running through one seat — the scope, measured rather than estimated.
Six sources, parsed programmatically and merged into one timeline with overlaps removed, then coded into sixteen functions.CALENDAR135 MEETINGSMAILSLACK867 TRANSCRIPTS~860 COMMITSMERGEoverlaps removed16 FUNCTIONSeach with its hours accounted forMETHOD ONLY · 8 WEEKS · SIX SOURCES
Six sources merged into one timeline, then coded into sixteen functions.

The sixteen functions, one seat

  1. 01Full-stack product engineering
  2. 02Operations & innovation
  3. 03Food-service general management
  4. 04Certification-program management
  5. 05Corporate development
  6. 06Chief of staff
  7. 07Product management
  8. 08AI & automation engineering
  9. 09Legal filings, registrations & nonprofit compliance
  10. 10Grants & development
  11. 11Brand & design production
  12. 12Partnerships & accounts
  13. 13Platform, deployment & IT security
  14. 14Finance operations
  15. 15Program & portfolio management
  16. 16Recruiting & HR