Cynefin analysis · AFN BC TV System Transition
The AFN BC TV System Transition is not one problem. It is a bundle of problems that behave differently, and the organization has been applying a single response posture across all of them. That is the source of most of the planning friction, not disagreement about facts but disagreement about what kind of problem is being solved.
Cynefin sorts problems by the relationship between cause and effect and prescribes a different response for each domain. Its value here is diagnostic. It explains why capable people looking at the same schedule reach incompatible conclusions, and it identifies which demands are answerable and which are aimed at the wrong domain entirely.
01 · The sort
Each domain has its own relationship between cause and effect, and its own correct response pattern. The sort below is legible on its own; expand any item further down the page for detail.
Cause and effect are obvious. Best practice applies directly. These require no planning attention beyond ensuring they are not blocked. The offices running them are operating correctly and should be left to it.
Analyzable and expert-solvable. Right answers exist and are reachable through arithmetic and expertise. These are hard, but they are not uncertain. Confusing a long lead time with an unknown outcome inflates perceived risk: the dates below are facts to plan around, not hazards to hedge against.
No knowable right answer in advance. Understanding emerges from action, not analysis. No amount of analysis produces these answers ahead of time, not from the vendor, not from engineering, not from AFN. Dual illumination is a probe. The mid-December go/no-go gate is a probe result being read.
No time to analyze, no opportunity to consult. The response must already exist and already be rehearsed. This is the entire justification for retaining sports channel reversion on Riverside hardware, not because failure is likely, but because chaotic-domain response requires the answer to already exist.
The fifth state
Its symptom is that each participant defaults to the domain they are most comfortable operating in, producing concern without convergence. This is exactly the pattern the stakeholder meeting produced: no factual disagreement, no shared conclusion.
Contracting and legal
Operate as though clear
Follow the process, await the trigger. Correct for their own workload, but it treats the whole transition as procedural.
Engineering and technical services
Operate as though complicated
Specify, order, install, validate. Correct for equipment and infrastructure, applied past its boundary.
The Broadcast Center position
Operates as though complicated, with insufficient analysis
Demand more definition before commitment. The instinct is sound; it is aimed at a domain that cannot supply what it is asking for.
Command
Operates as though complex
Request options, convene a tabletop, plan in parallel rather than sequence. The correct posture for the complex portion of the problem.
Naming the domains is what converts disorder into a decision. Once each demand is placed in its own domain, the disagreement stops looking like a conflict of judgment and starts looking like four correct instincts pointed at different parts of the same problem.
02 · The diagnostic
This is the analytical payoff of the sort above.
The calls for a defined FOC, objective readiness criteria, clear training milestones, an integrated operational schedule, and demonstrated stability before commitment are legitimate and correct in the complicated domain. Complicated problems can and should supply that certainty before commitment.
But the portion of the transition generating the most concern is complex. Objective readiness criteria for a system nobody has operated cannot be defined in advance; they emerge from operating it. The request is the correct instrument applied to the wrong domain, which is why it feels simultaneously right in principle and impossible to grant.
In a complicated domain you commit to an answer. In a complex domain you commit to a decision point. The mid-December gate is the domain-appropriate form of commitment.
03 · Movement between domains
A static sort misses the part that matters operationally: items move between domains as conditions change, sometimes toward a better position and sometimes away from one.
Complex → Complicated
The cloud platform moves from complex to complicated as it stabilizes through testing and dual illumination. That migration is the goal, and burn-in is what earns it.
Complex → Chaotic
A reversion failure during the protected calendar drops the problem from complex to chaotic with no warning. A prepared, rehearsed response is the only mitigation available in the moment.
Complicated (believed) → Disorder (actual)
Untested capability sits in disorder while believed to be in complicated. A reversion path never executed is an assumption, not a capability, however confident the plan looks on paper.
04 · What the lens generates
Most of what this analysis produces is already stated elsewhere in operational language. These three are not.
Run sports channel reversion on Riverside hardware at least once, at low stakes, before the mid-December go/no-go. A reversion path never executed is an assumption. It is cheap now and impossible in February.
Currently there is effectively one probe: the platform itself. A low-consequence channel running on cloud early generates real operating data while the evidence can still change decisions.
Lead times on equipment, power, and furniture are knowable. Attack them with expertise and sole-source pressure, not contingency planning built for uncertainty they do not actually have.