Summary

  • On 6 September 2026, the ICANN Board resolved that the FY26–30 Strategic Plan would remain in force and unchanged after eight environmental-scan sessions with nearly 210 participants. The resolution says AI was raised in all sessions with the community and also notes apps and other naming spaces as a recurring trend.
  • ICANN’s adopted operating plan says the Annual Strategy Review Program would identify a threshold or criteria that trigger a change in strategy or actions. The Board record names a full review report and a supplemental trend mapping but does not link them or show the trigger applied. That limits public reproducibility without making the no-change decision invalid.

An institution can look directly at a new risk and rationally decide not to rewrite its strategy. That is what the ICANN Board says it did. Resolution 2026.09.06.07 leaves the Strategic Plan for Fiscal Years 2026–2030 in force without amendment. The decision followed environmental scans conducted from February through April with participation from the community, the Board and ICANN organization. It was adopted at the Board’s 6 September regular meeting and published three days later.

The important word is not “unchanged.” It is “after.” A strategic review creates value only if an observer can follow the path from signal, through an assessment rule, to a disposition. The resolution identifies several signals and states the outcome. The connector between them remains implicit.

No change is still an exercise of authority

The Board did not merely allow an old document to continue through neglect. It expressly affirmed that the plan remained relevant and on track. The Board Strategic Planning Committee had reviewed the emerging trends, supported by ICANN staff, and recommended that no modification was needed. Under its charter, that committee is responsible for reassessing strategic priorities at least annually, coordinating them across Board work, overseeing consultation and supervising the trends process. The Board then owns the final resolution.

That authority chain should be kept separate from the consultation chain. Nearly 210 participants are not 210 votes for or against an amendment. Environmental-scan sessions collect observations and perspectives; they do not produce a plebiscite or a binding community consensus. Nor does the fact that AI was raised in all sessions with the community establish that every participant agreed on its meaning, urgency or remedy.

The decision also should not be read as a finding that AI is harmless. ICANN’s rationale calls it both a risk and an opportunity for ICANN, the Internet’s unique identifier systems and the multistakeholder model. It separately points to apps and other naming spaces as forces that may alter the DNS marketplace over time. A Board can assign those trends to monitoring or operating work while deciding that the current high-level objectives are broad enough to contain them.

The operating plan promised a trigger

ICANN’s adopted FY27–31 Operating and Financial Plan gives the annual review a more testable shape than the resolution does. It says the program should determine whether the strategy remains relevant and whether adjustments are necessary. It lays out research, framework design, stakeholder input, data collection, assessment, stakeholder review and implementation stages.

One milestone is unusually precise. During tool development, ICANN would create templates for data collection, scenario analysis or issue identification and “identify threshold or criteria” that would trigger a change in strategy or actions. The wording allows two different outcomes. A trend can justify reopening the five-year plan, or it can leave the plan intact while changing an operational action. It can also fail the threshold for either response.

That design protects strategy from fashionable churn. It also makes the trigger the critical evidence object. Without it, readers see that AI appeared repeatedly and that the Board chose continuity, but they cannot test whether AI was mapped to an existing objective, assigned to an operating initiative, deferred for more evidence, or judged outside a threshold for action. None of those possibilities implies failure. They are simply different governance states.

The operating plan itself anticipates the trust problem. Its considerations warn that poor-quality data collection can produce a flawed understanding of current strategies, cause the community, Board and staff to distrust the process and reduce participation. A published trigger and disposition record would answer that risk more directly than a larger volume of narrative reassurance.

The cited evidence is not connected on the decision page

The September resolution says the full results are recorded in an “ICANN 2026 Annual Strategy Review Report.” It also says a mapping shows how the 2026 emerging trends fit the FY26–30 Strategic Plan. On the checked decision page, those two named supporting artifacts are not linked. The page does link the adopted strategic plan and the five-year operating plan.

This is a bounded observation. It does not prove that the report or mapping does not exist, that Board members lacked them, or that they will not be published elsewhere or later. It means a reader starting from the authoritative decision cannot retrieve the evidence package that the rationale invokes. The result is an attributable decision without a reproducible assessment path.

The distinction matters because the operating plan contains several plausible destinations for technology trends. Initiative 27 assigns the Office of the Chief Technology Officer to scan emerging technologies, use analytics, solicit stakeholder feedback and maintain tools such as Domain Metrica and the Identifier Technologies Health Indicators. Initiative 28 covers work with the IETF, Regional Internet Registries and root server operators, along with KINDNS, ITHI and OCTO publications. The FY27 organizational objectives add a broad commitment to scan the horizon for technologies that may affect ICANN.

Those activities show that “no strategic amendment” need not mean “no work.” They do not, by themselves, tell the public which activity received the AI signal, which owner accepted it, what output is expected or what later evidence would move the Board from monitoring to adjustment. The Board’s statement that AI priorities are already translated into operational work is therefore a claim that calls for a connector, not a reason to assume either inactivity or completion.

A trend-disposition receipt

ICANN could make the next annual review reproducible without publishing confidential deliberations or naming individual participants. A compact receipt could assign each material trend an identifier and record the dates and participant cohorts from which it came. It could then name the evidence classes, relevant strategic objective, operating initiative and accountable function.

The next fields are the decisive ones: the version of the trigger or threshold applied; the result; and the disposition. A controlled list might distinguish change strategy, change action, monitor, defer and outside remit. A linked action should carry an owner and milestone. A no-action state should be explicit rather than inferred from silence. Every row should have a next-review date and a correction history.

This is my editorial recommendation, not an ICANN requirement or a description of an existing system. It applies the authority-and-record separation in The Policy Mirror, the execution test in Running Code Primary and the evidence discipline in Why BTW Media Exists.

The Board has already supplied the most important constitutional fact: it considered the review and chose continuity. Publishing the trigger-to-disposition connector would not weaken that choice. It would let the community see why a widely observed trend produced monitoring, operational work or no change—and what evidence could change that result next year.

Sources