60 Hours to 30

A person working 60-hour weeks should be able to drop to 30 and still get more done than before — “if we do it right.” That’s the claim. It’s worth defending on its own terms before anything softer gets said about it.

“A person working 60-hour work weeks should be able to go down to 30-hour work weeks and still get more done than they did before if we do it right.”

The obvious objection

Any engineering leader running a team through the same AI transition has a ready answer to that: my team is 40% more productive, so I ship 40% more. I’m not sending anyone home — I’m competing.

That’s the default position, and in the short term it wins the output race. The 60-to-30 claim only holds up if it answers that objection on the objection’s own terms — commercially, not sentimentally.

Here’s the answer:

“We can always ramp up productivity with more AI, but we can never replace the human perspective.”

The logic: if AI makes the same productivity gain available to everyone — the same models, the same tools, the same speed-up — then productivity stops being what separates one team from another. What’s left to compete on is the human judgment sitting on top of the tooling — the discernment, the angle a specific person brings after enough accumulated experience.

And that’s exactly what overwork erodes:

“…the more people become disconnected digitally and isolated from the real world, the more they spend long hours working, the more likely they are to become stressed. People who are stressed are more tunnel vision, less creative, and less human.”

Stress produces tunnel vision. Tunnel vision produces less creative work. Less creative work is exactly the thing that was supposed to become the differentiator once AI made raw output cheap. A team that reinvests its entire AI productivity gain into more hours at the same intensity is optimizing for the metric that’s about to stop mattering, at the cost of the one that’s about to start.

“So the true competition is not just productivity—it’s going to be innovation and authenticity.”

Where the surplus goes

The 60-to-30 claim isn’t an argument for less work, and it isn’t the “use AI to be more human” sentiment already common in this conversation. It’s specifically about where the surplus goes.

“I do not believe that we will essentially become like house cats who don’t have work. I believe that we need to have meaningful work, but that our work should become more meaningful and less drudgery.”

Meaningful work stays. What goes is the drudgery — and, at minimum, the time currently spent in meetings that don’t need to happen.

The proof, not the aspiration

An assertion about hours and output is easy to make and hard to check. This part is checkable: a specific practice with a twenty-year history and a file on disk today.

The discipline dates back to Patient Wisdom, where Chris worked as lead developer under Nate Perry-Thistle — now his business partner, then his CTO. Among the practices the team built:

“Backlog items would capture a user story, description, clear acceptance criteria, and tech notes so that anybody who picked up a backlog item could execute it and pick up the context.”

That discipline is on disk today, as the file his AI agents load before drafting a backlog item — create-backlog-item/SKILL.md, canonical in his command_center repository and synced out via script to the other project repos that use it. The file’s own header records when it became formal team practice:

“Registered — Chris-approved at the 2026-06-19 Friday review.”

And the rule it enforces is the same test from the Patient Wisdom era, generalized from people to agents:

“Could a competent stranger review this without a meeting, and could a parallel agent build it without DMing you?”

What used to be “anybody who picked up a backlog item could execute it and pick up the context” is now literally the instruction his AI agents follow before they write one. The throughline is a file anyone can open.

The honest exception

This isn’t a claim that teamwork always wins. Unprompted, Chris volunteered the counter-evidence and qualified it in the same breath:

“Though I also learned that there were other ways of working that could be highly productive, where people worked alone for longer periods of time and had their own projects, I definitely did not see as many positive benefits in terms of the culture in those environments.”

Solo, long-form work can be genuinely productive. The argument here is that stress and overwork corrode the thing that’s about to matter most, whether the work in question is solo or shared.

Where it ends

“And even to add to that, the human mind, as it grows, develops more language and more experiences. It becomes a much richer and richer world of experience and more valuable. So the most valuable thing is going to be human minds that are full of languages, perspectives, experiences, and so on. And the other thing that a machine will never be able to do is love. So only humans have free will and the ability to sacrifice for others and to love.”