Recall our XP case study, where Greg Woodward noted that a lot of developers dislike the extreme environment and end up leaving after a few weeks. Th… - Cal Newport

Also as in natural settings, in workplaces without well-defined processes, energy minimization becomes prioritized. This is fundamental human nature: if there’s no structure surrounding how hard efforts are coordinated, we default to our instinct to not expend any more energy than is necessary. Most of us are guilty of acting on this instinct when given a chance. An email arrives that informally represents a new responsibility for you to manage; because there’s no formal process in place to assign the work or track its progress, you seek instead the easiest way to get the responsibility off your plate — even if just temporarily — so you send a quick reply asking for an ambiguous clarification. Thus unfolds a game of obligation hot potato, as messages bounce around, each temporarily shifting responsibility from one inbox to another, until a deadline or irate boss finally stops the music, leading to a last-minute scramble to churn out a barely acceptable result. This, too, is obviously a terribly inefficient way to get work done.

Acuity, ScheduleOnce, Calendly, and, of course, x.ai (to name a few examples among many)

Writing in the early 1990s, as the personal computer revolution first accelerated, Postman argued that our society was sliding into a troubling relationship with technology. We were, he noted, no longer discussing the trade-offs surrounding new technologies, balancing the new efficiencies against the new problems introduced. If it’s high-tech, we began to instead assume, then it’s good. Case closed.