The decision that changed the PGA Tour's audience was to stop restricting access. Rather than releasing content in a controlled drip, they opened it — inviting the golf creators already working on social platforms to come in (10:12).
The result is the number worth remembering: 80 per cent of the audience reached had never subscribed to the Tour's own channel (12:27).
Why that figure is unusual
Most content strategy metrics measure how well you serve people who already found you. This one measures the opposite, and it is the harder thing to move.
An organisation with a large existing audience optimises for that audience by default, because that is where engagement is measurable and where the feedback arrives. The result is content that performs well among people who were already watching and does nothing to change who is watching. Eight out of ten viewers arriving from outside is evidence of the rarer outcome.
The mechanism is worth naming precisely: they did not produce content for a new audience. They let people who already had that audience make it, which is a distribution decision rather than a production one.
The constraint that made this necessary
Golf has a specific problem the session states plainly: it is hard to see. The traditional broadcast form struggles to show what is actually happening (5:28).
That is a genuine format constraint rather than an excuse. A ball travelling three hundred yards against sky, on a course spanning miles, with the meaningful action distributed across dozens of simultaneous groups, resists the single-camera-follows-the-action grammar that serves other sports.
Which explains why creators found audiences the broadcast could not. They were not competing on production quality. They were solving a legibility problem — closer, slower, explained — that the established format had never solved.
What falls when production cost falls
The forward-looking claim is about economics: what was cost prohibitive is becoming accessible, and a creative person with the right idea can now think bigger than before (35:18).
For a sport with golf's visibility problem, that is more consequential than it would be elsewhere. The reason certain shots were never shown well was that showing them required equipment and crew that only a rights holder could fund. When that falls, the constraint on what can be depicted stops being budget and becomes imagination — and the people with the ideas are not necessarily the people holding the rights.
The session's honest note is that the Tour now finds itself looking differently at its own game because of the diversity of what is being made (13:48). That is a rights holder acknowledging that its audience is being shaped by people it does not employ, which is an uncomfortable position and a more truthful one than most such sessions reach.
关键数据
- 80%
- share of the reached audience that had never subscribed to the organisation's own channel 12:27
演讲章节
关键要点
- 01
Rather than releasing content in a controlled drip, they opened it and invited the creators already working on social platforms. 10:12
- 02
Eighty per cent of the audience reached had never subscribed to the organisation's own channel — a metric measuring who is newly watching rather than how well existing viewers are served. 12:27
- 03
The underlying constraint is a format problem: golf is hard to see, and traditional broadcast grammar struggles to show what is happening. 5:28
- 04
As production cost falls, the constraint on what can be depicted shifts from budget to imagination — and the people with ideas are not necessarily the rights holders. 35:18
- 05
They acknowledge the sport is now being shaped by the diversity of what outside creators make, which is an uncomfortable and honest position for a rights holder. 13:48
提及的实体
相关演讲
The practical counterpart to the argument made elsewhere this season that specification is what contains model entropy. Raval and Harris name the failure they are addressing precisely — a prompt-and-pray loop in which working code arrives with no record of what the model assumed, which requirements were fuzzy, what design was chosen or why, leaving nothing to review and nothing to iterate against when a defect surfaces months later. Their answer is three committed markdown artefacts: requirements written in a structured requirements syntax with acceptance criteria attached to each user story, a design document carrying technical decisions together with the reasoning behind them, and a task list whose entries cite the requirement numbers they satisfy. The traceability is the point — a reviewer questioning a decision in a pull request can follow it back through the task to the design to the requirement, all in the same repository. Notably they keep the human between each phase rather than after it, with the agent surfacing ambiguity as questions before proceeding.
Drawn from a year of engagements with more than a hundred companies, this is the most direct challenge in the season's programme to the assumption that faster code generation produces faster delivery. Mishra and Raja open with external evidence rather than their own: an industry study putting realised velocity gains in the ten to fifteen per cent range, and a controlled experiment in which developers using AI estimated themselves roughly a fifth more productive while measurement showed them a fifth slower. Their diagnosis is that both prevailing working styles fail for opposite reasons. Handing an ambiguous problem to an agent and awaiting a finished result produces a volume of code the developer must nonetheless sign for and cannot confidently review, so it stalls before production. The senior engineer's alternative — decomposing the work personally and inserting AI into narrow slots — keeps the intellectual load exactly where it was, and leaves the surrounding process untouched, so hours saved in editing are consumed by the meetings that process still requires.
Brooker builds the definition from the bottom up rather than asserting it, using a deliberately absurd arithmetic task to separate three categories: what a model computes reliably as a fixed function of its input, what merely needs to arrive in the system prompt, and what genuinely requires reaching into the world. Only the third category justifies a tool, and the distinction matters because most production disappointment comes from tools built for the first two. His working definition follows — a system given a goal that loops between inference and tool calls until it reaches one — with the observation that modern agents increasingly embed code in their definitions, not for expressiveness but because replacing inference steps with deterministic code improves reliability while lowering both latency and cost. The remainder covers what production actually demands around that loop: somewhere to run, memory that persists preferences, a gateway to internal and external tools, evaluation, and formal methods applied to policy.
The most concrete attempt this conference season to answer a question the agentic coding sessions mostly leave open: if commit counts and hours saved are the wrong measures, what replaces them? Otto's account is unusually specific about why the obvious alternative fails — summing the small time savings a platform team delivers produces figures exceeding a hundred per cent of a developer's time, and a minute returned is not code in production. Their replacement borrows from Amazon's retail supply chain, where cost to serve measures what it takes to place a package on a doorstep, and applies the same shape to software: total cost divided by units of delivery, with the unit chosen to fit the team. The supporting research is the more quotable finding — across tens of thousands of developers over five years, individual velocity reverts to the team's mean, making team velocity the strongest predictor of both individual output and perceived productivity, which is the empirical case against measuring individuals at all.
The framing statistic is organisational rather than technical: around eighty per cent of organisations expected to have platform engineering teams going into 2026, up from about forty-five per cent a couple of years earlier. The interesting part is the doubling. The problem described is teams solving the same problems separately, producing inconsistency and redundancy — dangerous not because of duplicated effort but because each independent solution has its own security properties, and the organisation's real posture is the weakest rather than the average. The most valuable content is that two financial services organisations went in diametrically opposite directions on workload identity and both are described as working, which implies the choice is determined by context rather than by a general answer. The honest note follows immediately: even with standardised patterns the result remains fragmented.
The line that explains this session comes from the customer in the last ten minutes: they are preparing for a world where metadata is how agent-based systems find the data they need and access it through the controls being built. That relocates a function — governance has spent two decades as compliance activity describing data that people locate by other means, and if agents navigate by the catalogue then the catalogue stops describing the access path and becomes it. An incomplete catalogue is a documentation problem when humans can ask a colleague; an agent has no such workaround. The most honest moment addresses the perennial failure that rules get written and ignored, with enforcement rather than publication as the argument. Generated descriptions and greyed-out classification suggestions divide the labour correctly, keeping a person accountable while removing the burden of finding candidates.