AI Extraction of Roadmap Points

Hi Maturity Team,
Below is the initial result of using AI to extract potential actions for
the roadmap from our meeting notes. I used all the meeting notes from 2025
and the following prompt:

What are the points made in the minutes that should be considered in a
future roadmap?

I have this all saved. So we could play with the prompt or even use it for
something else. Perhaps a discussion for next week?

*The Results*

Key areas identified for future work include enhancements to the model's
structure, integration of new technologies like AI, and refinement of
tooling and language:
Model Content and Proof Points

   - *Financial Allocations (Budgeting):* While the current version places
   a proof point related to *financial planning and committed funding*
   within the "Oversight and Culture" dimension, the idea of having this
   budget proof point in *all dimensions* remains an ongoing consideration
   for future releases.
   - *Strengthening Procurement Language:* Issue 323, concerning the
   strengthening of motivation for procurement language, has been
marked for *future
   work*.
   - *AI Implications and Bias:* There is significant interest in exploring
   the role of Artificial Intelligence (AI) in the model. Future releases
   should consider:
      - Adding proof points for *AI*.
      - Addressing potential issues of *discrimination or bias* related to
      AI usage.
      - Issue 322 specifically proposes adding a proof point to the support
      section concerning *AI agents*. This is slated to be combined with
      another issue Sherri was working on.
      - Providing advice on where and how to use AI.
      - Exploring how a company can stay accessibility mature while using
      AI.

Model Structure and Nomenclature

   - *Governance and Strategy:* The need for a specific dimension focused
   on governance and strategy is a recurring issue, with plans to potentially
   rename the existing "Culture" dimension or add a new one.
      - Issue 341 discusses the *missing governance/policy* component.
      - Sheri suggested that the dimension name should be *Governance*,
      arguing that governance inherently requires oversight.
      - It was decided to wait on adding a new Governance dimension
until *after
      the initial release*.
   - *New Dimensions (Equity and Sustainability):* Future additions could
   include dimensions such as *equity and sustainability*.
   - *International Terminology (ICT):* The term *ICT (Information and
   Communications Technology)* is not widely known outside of policy areas
   or international circles. The roadmap should consider:
      - Adding a sentence to explain that it may also be referred to as
      "digital technology".
      - Filing a note that suggests organizations may want to adjust the
      term based on their application area (e.g., using "EdTech" or "Digital
      Tech").
   - *Clarity of "Proof Point":* The term "Proof Point" is deemed unclear
   (Issue 318). This may require writing a small explanatory section in the
   introduction for the next release.

Tooling and Assessment Platform

   - *Replacing the Spreadsheet:* Creating a more accessible platform than
   the current Excel spreadsheet is a priority. The goal is to develop an *HTML
   platform in the form of forms*, though this was not included in the 2025
   initial release.
   - *Scoring/Tracking System Evolution:*
      - The team plans to discuss renaming the scoring system to a "*tracking
      system*" or "*progress tracking system*" to better reflect maturity
      progress.
      - Mark Miller has scoring ideas he plans to share.
   - *Standard Reports:* A future iteration may include *standard reports*,
   which would make documenting changes and customizations very important.

Future Releases and Normative Work

   - *Version Control:* Janina suggested marking the initial publication as
   "*1.0*" to allow for future updates like a *1.1 version* that would
   likely incorporate AI improvements.
   - *Normative Model:* Fazio mentioned that *2.0* could potentially be
   explored as a *normative* version. However, the Task Force is not
   currently chartered for normative work, and re-chartering would be required.
   - *WCAG 3 Alignment:* Future discussions are planned on how the maturity
   model can be inserted into or line up with *WCAG 3*.
   - *Release Cadence:* Concerns were raised that making changes too
   frequently (subsequent releases) could cause "havoc," suggesting that a
   maintenance release should be marked as a ".x" release.
   - *Process and Review:* The roadmap should include a *plain language
   review* of the document. Fazio intends to look for time to build a
   timeline for future work.


-- 
Thank you,
Mark Miller