Logbook Entry#20
Time, Cost, Quality. Pick two. A rule from 1969, what it hides about Quality, and what AI brings to the surface. With Pirsig, Atkinson, DSDM's reshuffle, PMI's quiet retreat from the model, and the half-ass that outlives each version of it.

Logbook Entry#19
Encountering change and successfully encountering change are two very different things. With AI, the test takes about fifteen minutes, and most positions don't survive it.

Logbook Entry#18
The labor shortage isn't a people problem. Through David's refusal of King Saul's armor, this post traces the intergenerational pattern, the German school system, and what AI does to the thinker/doer divide.

Logbook Entry#17
From Chaplin's feeding machine to token leaderboards: four costumes, one law. Why measuring AI consumption as productivity produces more output with less value…And what 22,000 developers reveal about the dashboard illusion.

Logbook Entry#16
Every job has two deals. The written one works. The unspoken one breaks. Why sacrifice gets rewarded, loyalty stays irrational, and the game keeps running.

Logbook Entry#15
Whose job is it to sharpen the axe? That question is already the first step away from taking responsibility. About tools, blame, projections, and the game that nobody wins.

Logbook Entry#14
Every agile framework runs on loops. Sprints, retrospectives, reviews, planning. But is anyone inside the loop awake?

Logbook Entry#13
Frameworks without culture is just a costume. Now AI joins the ballroom wearing its own mask. What happens when the music stops and the masks come off?

Logbook Entry#12
One mistake in AI becomes part of the system. Then the system builds on top of it. Semantic drift doesn't just happen. It compounds and becomes its architectural foundation.

Logbook Entry#11
AI makes building fast. But who checks if you're building the right thing? Speed without validation isn't efficiency. It's waste with the fast-forward button held down.

Logbook Entry#10
Agile and its ceremonies cost big bucks per team per year. The real number is probably double. AI won't make them disappear (at least at the moment), but it changes what your team actually spends time on — while we need to question how that time is spent.

Logbook Entry#09
Planning at 100% means you're already at 150%. Part 2 asks: if you had room, would you actually use it or would the system fill it before Monday's standup?

Logbook Entry#08
Your brain mistakes pressure for productivity. Cortisol sharpens focus, dopamine rewards the crunch and your prefrontal cortex pays the bill. Why content teams win.

Logbook Entry#07
The Product Backlog is not a planning tool. It's a delivery mechanism. But what does that mean exactly? And why do most organizations skip the step that makes agile actually work?

Logbook Entry#06
Four people say "I’m done!" Four people mean something different. How the Definition of Done quietly became a quality checklist instead of an outcome definition.

Logbook Entry#05
Priority without criteria is just noise. When everything is labeled urgent, nothing is urgent. The Result: a system that keeps running on declarations instead of decisions.

Logbook Entry#04
Hidden complexity doesn't go away. It shows up as meetings, spreadsheets, and sleepless nights. When a tool is simpler than your work, you're not reducing complexity. You're hiding it.

Logbook Entry#03
Story Points were supposed to help teams talk about complexity. Then someone put them on a dashboard. What happens when a conversation tool becomes fantasy math with a deadline.

Logbook Entry#02
A team told me the User Story was the thing they hated most about their daily work. Turns out, it wasn't the format that was broken. It was where we put it.

Logbook Entry#01
Organization plans blind. They estimate effort for their own team and pretend the rest doesn't exist. Here's how a team on the edge of failure changed that.