Hotels now pay to be looked atReframes the OTA commission as a subsidy hotels never saw: for three decades intermediaries absorbed the cost of all the looking that never converted, charging only on the booking that landed, and AI agents running thousands of searches per session turn that buried cost into a standing bill the moment a hotel exposes rates directly. Cites airlines' NDC shift — taking back content control while inheriting the cost of being shopped — as the precedent hotels are now repeating.
Industry lens
Will hotels that have gone direct start gating or pricing agent queries — as Air Canada did with its GDS distribution-cost surcharge — and if so, does that toll re-route agent traffic back to whoever can absorb look-cost at scale?
Distilling Soleio Cuervo's hiring lens, the argument is that the gap between competent and exceptional designers is posture rather than craft — communicating intent over showing work, confronting users while ideas are still cheap to change, asking whether a feature should exist at all, and refusing to delegate strategy and impact to PMs.
Why it matters
The claim that a designer who only executes the "what" cannot be excellent redraws the design–product boundary as a hiring and org-design decision, not a craft tip — it changes who a leader hires and how the design role is scoped against PM.
An executive coach to frontier-lab leaders argues that as AI commoditizes knowledge and effort, teams are restructuring into 'NBA rosters' — flatter orgs, shrinking headcount, player-coach roles, more capital per person — where the scarce, decisive skill becomes emotional clarity: discernment, productive conflict, willingness to fail, and positive self-talk.
Industry lens
As Indian OTA and product orgs adopt agentic tooling, will the first measurable hiring shift show up as reduced execution-role headcount or as new player-coach and judgment-weighted roles — and which competitors move first?
A follow-up to last year's 'agent as design-system reader' argument documents that agents now write to design systems — placing real components on the Figma canvas via use_figma, proposing and committing token changes through Storybook and Figma MCP servers, generating documentation, and even authoring the SKILL.md and DESIGN.md files that instruct them — removing the human translator between system and implementation.
Why it matters
Once agents author components, tokens and docs at machine speed, the load-bearing failure shifts from generation quality to review: the sign-off that used to sit between a change and what ships becomes nobody's explicit job, so teams need a review and provenance model built for probabilistic authorship before they widen agent write access.
Vendor-sponsored research (Aven Hospitality with Skift Studio) finds only 11% of hotel organizations run AI agents that can actually complete bookings or price inventory in real time, while roughly 80% confine AI to chatbots and marketing — the gap, it argues, decides whether a property surfaces in conversational recommendations at all.
Why it matters
The contested ground is the recommendation moment, not the checkout, so the defensible work is making rate-and-availability data machine-readable and retrievable by agents rather than optimizing rank position in a fading link-based results page.
A playbook of 20-plus reusable agent loops for PMs, each defined less by its prompt than by an explicit stop condition and an independent grader — harden a PRD until two engineers reading separately would build the same thing (checked by a second model reading cold), cluster feedback until themes stop changing, plus competitor watch and ship checks.
Why it matters
The leverage is not the prompt but specifying "done" precisely enough that an agent and a grader can self-terminate, which reframes the PM skill to build as writing falsifiable acceptance criteria rather than collecting prompt templates.
Proposes a six-layer model of AI experience — interface, context, harness, model, governance, emergence — extending Garrett's Elements of UX and Mill's Product Design framework into probabilistic systems. The argument: because the model itself introduces variance, designers should shape the conditions and leverage points beneath the interface rather than specify every state, and the interface's role shifts from driving the system to overseeing it as onboarding becomes the system learning the user.
Why it matters
If interface work shifts toward oversight and the real leverage moves to context, harness and governance, then design hiring and tooling investment should follow it beneath the surface — toward people who can shape model behaviour, context systems and guardrails — rather than producing more chat-UI patterns.
