Regional Sports Networks Collapsed. What Replaced Them Is Messier
Ask ten people to define sports industry — and you will get ten answers, most of them describing a symptom rather than the thing itself.
How it works
There is a version of sports industry — that is mostly ritual. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. There are organisations where the opposite is true, and they are not obviously worse off.
The second-order effects arrive about a quarter after the first-order ones. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen.
Where to go deeper
Consistency is worth more than any individual improvement to sports industry —. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next.
The interesting constraint is almost never the one in the brief. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem.
Nobody gets credit for the work that did not need doing. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. The version of this that works fits on an index card. The version that fails needs an onboarding session.
Why it is confusing
Consider the failure mode rather than the success case. The things that are easy to count are rarely the things that matter, and once a number reaches a dashboard it starts shaping behaviour whether or not it deserves to. When we mapped it out, four of the seven steps existed only to compensate for the second one.
Feedback loops shorter than the planning cycle change everything. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. The evidence here is thinner than anyone quoting it tends to admit.
A common misreading
The default answer is right often enough to be dangerous. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix.
Documentation is a symptom: you write it where the design is unclear. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. The clearest signal was that people stopped asking where things were.
The first thing to establish is what you are actually optimising for. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight.
The edge cases
It helps to separate the decision from the execution. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. In practice the answer showed up in the calendar before it showed up in the dashboard.
Measurement is usually where this falls apart. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. Set a date at which you will stop, and write down in advance what would make you stop earlier.
The cost of a bad decision is rarely the decision. It is the six months of building on top of it.
— Overheard in a retrospective
The vocabulary problem
Speed and reversibility are the trade-off worth naming out loud. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture.
Most of the difficulty lives at the boundaries, not in the middle. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. That said, none of this generalises cleanly across team sizes.
The tooling question is downstream of the constraint question. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review.
The checklist we ended up with:
- Name one person accountable — not a group
- Decide in advance what would make you stop
- Keep the feedback loop shorter than the planning cycle
- Prefer the reversible option when the evidence is thin
- Review the numbers monthly; change the targets rarely
Putting it together
A shared definition of "done" removes more friction than any tool. The first quarter shows the intended effect; the second shows what the intended effect displaced. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison.
Scope is the variable everyone adjusts last and should adjust first. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive.
The short version
The compounding effects matter far more than the individual wins. Sports industry — rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound.
The expensive mistakes here are rarely the technical ones. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it.
What it is not
What looks like a process problem is frequently an ownership problem. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests.
Consider the failure mode rather than the success case. The first quarter shows the intended effect; the second shows what the intended effect displaced. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer.
The default answer is right often enough to be dangerous. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. A useful test: if this disappeared tomorrow, how long before anyone noticed?
How it works
The interesting constraint is almost never the one in the brief. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not.
The short version: decide what you are optimising for, write it down, and revisit it when the answer stops feeling obvious.
Discussion
More from this issue.
Streaming Won the Rights War. Keeping Subscribers Is the Hard Part.
Sports industry — is one of those topics where the obvious answer is right about sixty per cent of the time, which is exactly often enough to be dangerous.
The Case Against Selling Every Match to a Different Platform.
Ask ten people to define sports industry — and you will get ten answers, most of them describing a symptom rather than the thing itself.
Why Free-to-Air Still Decides Which Sports Grow.
Ask ten people to define sports industry — and you will get ten answers, most of them describing a symptom rather than the thing itself.