Trends

Specifications were always useful and often skipped, because experienced engineers filled the gaps by asking questions. AI agents do not ask; they build what is written. That makes the specification the highest-leverage artifact in software and AI delivery: it determines what gets built, what can be verified, what can be governed, and what can be reused. This essay explains why specs matter more now and how to write ones that work.

Employees report large time savings from AI, yet company results barely move. This essay explains the AI productivity paradox: where saved time goes, why individual gains do not aggregate, why measurement misses what matters, and the operating changes, from redesigned processes to digital FTEs with attributable output, that convert AI speed into results a CFO can see.

The instinct to staff AI programs with large teams is wrong. Small teams of senior engineers directing AI agents ship more, with higher quality, than large teams of mixed seniority, because coordination cost falls, specification quality rises, and accountability is clear. This essay makes the case, explains the mechanisms, and gives a model for sizing and staffing AI work.

Digital FTEs change the economics of operational work by making capacity elastic, output attributable, and cost a function of work volume rather than headcount. This essay lays out the cost structure, the comparison with human and outsourced FTEs, the elasticity and quality dimensions, the hidden costs that trip up budgets, and what changes in how finance and operations leaders plan capacity.

For three years, enterprises ran AI pilots: dozens of experiments, few in production, and little to show a board. That era is ending. Budgets are being cut for pilots that never ship, leaders are demanding production results, and the companies that win are building platforms and deploying on evidence. This essay explains why the pilot era is over, what replaces it, and how to make the transition.

AI purchases are moving into standard procurement, and the contract terms are changing. Audit access, model change notice, and exit provisions are becoming the negotiated points.

Predictions about AI usually overshoot capability and undershoot operational difficulty. Here is a grounded view of what the engineering discipline is likely to look like.

Ask why an enterprise AI project is late and the answer is rarely technical. Data access approvals, unclear process ownership, and security review consume the schedule.

Forward deployed engineering, where senior engineers work inside the client's organization to ship production AI systems and transfer capability, is becoming the dominant delivery model for enterprise AI. This essay explains what the model is, why it emerged, why it beats consulting decks and outsourced tickets for AI work, where it fits and does not, and how organizations should use it.

Teams spend disproportionate energy choosing a model and little on the system around it. That ratio is inverted relative to what determines whether a deployment works.

AI makes generating output nearly free while checking it stays expensive, and the distance between the two is the verification gap. It explains why AI systems fail quietly, why productivity gains evaporate in review, and why trust in AI is scarce. This essay defines the gap, shows where it appears across code, content, analysis, and agents, and lays out how to close it with engineering rather than hope.

Traditional application security assumes code does what it was written to do. Agents interpret input that may contain instructions, which breaks that assumption at the foundation.

AI-native companies, which design their operations around AI agents rather than adding AI tools to existing work, are pulling ahead of AI-assisted competitors, and the gap compounds. This essay explains the mechanisms: platform reuse that makes each system cheaper, verification capacity that lets them scale safely, agent leverage on small senior teams, and an operating model built for mixed human and digital work. It also explains how incumbents close the gap.

The scarce skill is moving. Building AI features got easier; deciding whether the output is right, and running the system responsibly, did not.

Language models are probabilistic, and enterprises need outcomes they can rely on, audit, and repeat. The resolution is not to make models deterministic but to build deterministic systems around them: structured outputs, bounded actions, validation, controlled inputs, and evaluation that makes behavior predictable within known limits. This essay explains why determinism matters, where it comes from, and how to engineer it.

Legal work is built on documents, precedent, and judgment, and AI automates the first two faster than any profession expected. This essay looks at what changes for law firms and corporate legal departments over the next five years, which work moves to AI first, why professional responsibility and verification define the limits, how billing and staffing change, what stays human, and how legal leaders should prepare.

Outsourcing was built on labor arbitrage: the same work done by cheaper people elsewhere. AI does volume work cheaper than any labor market, which collapses the arbitrage and moves value to what AI cannot supply alone: senior engineering, verification, domain judgment, and accountable delivery. This essay looks at what changes for buyers and providers over the next five years and how both should adapt.

Product managers translate customer needs into what engineers build, and AI changes both ends: discovery and prototyping accelerate, and coding agents build what is specified, which makes the specification the primary product artifact. This essay looks at what changes for product management over the next five years, why PMs must learn to write specs agents can build from, what stays human, and how product leaders should prepare.

Quality assurance spent decades executing test cases and automating regression, and AI now generates tests, executes them, and produces the code they check faster than QA can keep up. This essay looks at what changes for QA over the next five years, why the function becomes verification engineering, why evaluating AI systems becomes its most important new work, what stays human, and how QA leaders should prepare.

Sales teams spend most of their time on research, outreach, data entry, and proposal assembly rather than selling, and AI automates all of it. At the same time, buyers use AI to research and shortlist vendors before any conversation. This essay looks at what changes for B2B sales over the next five years, what moves to AI first, why trust and judgment become the seller's edge, and how sales leaders should prepare.

Software agencies sold implementation by the hour, and AI coding agents implement in minutes what took days. This essay looks at what changes for agencies over the next five years, why the hourly model on implementation collapses, what clients will pay for instead, how agencies should restructure teams and pricing, what stays human, and how to turn the transition into an advantage instead of a margin collapse.

The first wave of enterprise AI put a copilot beside every knowledge worker. The next wave adds digital coworkers: agents that own defined work, act in systems, and are managed like staff. This essay explains the difference, why the shift is happening now, what changes in design, governance, economics, and management, and how organizations should prepare for teams that mix people and digital coworkers.

An agentic enterprise is a company where AI agents do a substantial share of defined work under human accountability, on a shared platform, with governance and measurement built in. This essay describes what that looks like in practice, how it differs from a company that has merely adopted AI tools, the operating model that makes it work, the risks that come with it, and the sequence for getting there without losing control.

Hundreds of AI tools launched; most were thin layers over a model API. Consolidation is under way, and what survives has either real infrastructure or real domain depth.