The build-side signals rhyme: a product lead can now stand up a repeatable model eval in an afternoon, the designer's real object becomes the agent's decision boundary rather than the screen, and even product durability gets relocated from roadmap to governance structure. What they share is a move away from the artifact you ship toward the system of judgment around it — the eval, the guardrail, the ownership model. The uncomfortable read for anyone building is that verbal fluency in AI no longer proves capability, so the differentiator is quietly becoming the internal machinery no vendor sells you.
Great Products, Bad CompaniesA veteran product voice reframes a long-held belief — that great products build great companies — arguing that product success attracts predatory investors and board actors who displace mission-driven founders, and endorsing a new governance book on 'mission-locked' company structures as the defence.
Industry lens
Will any high-profile technology or travel company actually adopt mission-lock governance at IPO, or will investor demand for liquidity and control keep such structures confined to founder-heavy private companies?
A repeatable evaluation harness, built live in under an hour with Claude Code, ran five frontier models through 64 blind generations across PRD, prototype, agentic, and voice tasks — blending human scoring at 70% with LLM judging at 30% — and the model-by-task verdict diverged from benchmark expectations.
Industry lens
If repeatable, self-built eval harnesses become standard product practice, do published vendor benchmarks lose influence over enterprise model-selection decisions, and does that pressure model makers to compete on task-level transparency rather than leaderboard scores?
Performative overstatement of AI capability — 'life-changing' agent workflows that in practice trigger half the time and need heavy hand-holding — is framed as doing measurable damage: it breaks hiring signals now that verbal fluency in MCP, RAG, and agents no longer proves competence, distorts genuine adoption, and manufactures a reverse-hustle culture where burning tokens replaces showing outcomes. The named drivers are attention economics, the difficulty of verifying anyone's claims, marketing that sells certainty AI can't deliver, and VC-to-exec-to-employee pressure to perform miracles.
Industry lens
As agent reliability improves through 2026, does the hiring signal recover — or do case-study and work-trial screens become the permanent default across product and engineering teams?
Accessibility treated as a feature or a one-off audit degrades over time; the case made is for running it as an operational capability — owned, tooled and embedded in workflow and process — so conformance is sustained continuously rather than retrofitted before launch.
Why it matters
Reframing accessibility as process rather than feature moves the cost out of pre-launch audits and into tooling and team ownership — a budgeting and org-design decision, not a design-QA one — and it changes who is accountable when something regresses.
With agentic systems, the designer's object is no longer the interface but the decision boundary — what the agent is permitted to decide, and under what constraints — making guardrail and permission design the core discipline rather than screen layout.
Why it matters
If the deliverable becomes the decision boundary, design reviews and design-system artifacts need to encode permissions and constraints, not just components and states — a different skillset and a different review process than visual critique.
Fashionable visual trends — abstraction, vagueness, aesthetic minimalism — erode conversion on sales pages by burying concrete value and relevance beneath style, trading the clarity that drives action for the look of being current.
Why it matters
The trends that hurt conversion are precisely the ones teams adopt to look modern, so the risk is internal: a redesign that scores high on craft can quietly suppress booking conversion, and without isolating those elements in tests the cause stays invisible.
Field notes from inside leading AI labs report two shifts in how software gets built: agents running in the cloud rather than locally becoming a major workflow, and coding harnesses — the scaffolding of prompts, context and guardrails around the model — spreading beyond specialist craft into mainstream engineering practice.
Why it matters
If cloud-run agents and harnesses become the default build method at the frontier, the competitive variable shifts from model access to harness quality — internal capability that can't be bought off the shelf — so two teams with the same model ship at very different speeds.
