Articles

Token costs are production costs, not developer allowances. Put them in the portfolio P&L, measure human plus AI labor against accepted outcomes, and stop mistaking visible inference bills for economic governance.

A letter from the executive seat to developers, managers, and directors on why AI adoption slows down when speed outruns trust, authority, and production reality.

Your token burn is not the problem. It is the first invoice honest enough to show that your engineering work has no value discipline.

Before you optimize token spend, measure the completed work, human attention, cycle time, and risk reduction those tokens bought.

The old software heroes explain the last era. The loudest influencers explain the demo. The builders answering customers in public are the ones closest to the truth.

The irony is familiar: you debate a $400 model bill, approve a $180,000 SOW, and pay an outsider to say what your own engineers already told you.

What if the most productive thing your software organization could do this quarter is not come to work?

A synthetic user is an LLM agent calibrated to a real reader persona that can navigate your product, read your copy, and tell you what is wrong before a real customer does. Here is how to build them, where they break, and why your feedback loop is six weeks too long.

Everyone talks about autonomous AI development. Norman is actually building it. A system of agents that predicts what players want, builds a browser game, ships it, measures it, and iterates, no human in the product decision loop. Here are the rules.