Eos - Project Operations (@eospk4) profile picture
Joined July 2026
Everyone's work is no one's work. Ticket sat in its queue for three days, where everyone could see it and nobody did anything about it. When someone finally noticed, no rule had been broken — because no rule existed. It had no owner, no clock. No wonder. eospk4.com/blog/ticket-triag…
2
Approved time is not the same as billable time. Billable is not the same as invoiced. Invoiced is not the same as sent. Eight handoffs, each needing an owner, a readiness rule, and a next decision. Mostly agentic, but clearly approver-based. eospk4.com/blog/eight-handof…
2
4
We don't know anyone hoping to begin Friday evening with meeting a timesheet. A good time-tracking process defines “complete,” finds exceptions, clear corrections, provides context and gives Billing good data. So everyone can get out in time to have fun. eospk4.com/blog/time-trackin…
2
11
Do the project-health analysis BEFORE the status meeting. Not DURING it. Bring a short exception brief: • What changed? • What proves it? • Why does it matter now? • Who owns the response? • When do we inspect it again? Meetings are for decisions. eospk4.com/blog/make-status-…
1
10
Eos - Project Operations retweeted
We all talk about using semantic layers as a "single source of truth," but the real goal is to have something that makes data conversations boring. You never have to wonder whose definition of MRR got used for a calculation, because your semantic layer figured it out.
1
2
20
AI agents escaped OpenAI and entered HuggingFace's network. What we learned, as humans: Agents work weekends. Seven controls for Agent governance: Intent • Process • Capabilities • Simulation • Approval • Run evidence • Change control eospk4.com/blog/seven-contro…
1
9