Skip to main content

Updates to the CNCF Adopter Interview Process for Moving Levels

· 3 min read
Karena Angell
Karena Angell
CNCF TOC Chair

The TOC has updated the Due Diligence Guide to clarify expectations for adopter interviews during the moving levels process. These changes aim to reduce delays, improve the quality of adoption signal, and give projects a clearer picture of what to prepare before applying.

Here is a summary of what changed and what it means for projects and TOC members.

What changed​

Adopter submission is now a formal application requirement​

Projects applying to move levels are required to submit 5-7 potential adopters as part of their application. This is not new guidance, but it is now explicitly documented in the Due Diligence Guide with a direct link to the submission form.

Projects should submit their adopter contacts via the Adopter Submission Form before or at the time of application. The TOC will select a minimum of three adopters from the submitted list for interviews, but may request additional interviews depending on the diversity of perspectives represented.

TAB Reference Architectures can replace individual interviews​

A project's inclusion in a published TAB Reference Architecture may now serve as a replacement for an individual adopter interview. Reference architectures represent validated, production-level adoption by the submitting organization and provide equivalent signal to a traditional interview.

TOC members should note the reference architecture in the adoption section of the Due Diligence in place of the interview summary it replaces. This gives projects with strong TAB engagement a faster path through the adoption assessment without reducing the quality of evidence.

Why these changes matter​

Adopter interviews are one of the most time-consuming parts of the Due Diligence process. Scheduling, conducting, summarizing, and getting approval on interview summaries can add weeks to a project's timeline. By requiring adopter submissions up front and recognizing reference architectures as equivalent evidence, we reduce avoidable delays while maintaining the standard of adoption signal the TOC and the community expect.

What projects should do now​

If your project is planning to apply to move levels:

  1. Prepare your adopter list early. Identify 5-7 adopters who use the project in an operational or production capacity. Prioritize contacts who are not project maintainers or governance participants.
  2. Submit via the Adopter Submission Form. Do this before or at the time you file your application issue.
  3. Check if your project appears in a TAB Reference Architecture. If it does, note this in your application. If your adopters are interested in submitting a reference architecture, see the TAB Reference Architecture process.

Questions?​

Reach out in #toc on the CNCF Slack or file an issue on the TOC repo.