toolEnglish

Governance and Best Practices

How to run the assessment responsibly before launch, during collection, and after results.

EnglishEspaƱolFranƧais

Documentation follows the current system language. Missing translations fall back to the page's canonical language.

Governance And Best Practices

The assessment is most valuable when it is treated as an organizational learning process, not as a compliance exercise.

Before Launch

  • Confirm the purpose and audience.
  • Decide whether the study is anonymous.
  • Define the division tree before importing participants.
  • Enable only the languages the study can support.
  • Review translations for organization-specific terminology.
  • Set dates that leave enough time for reminders.
  • Define how results will be shared before responses are collected.

During Collection

  • Monitor completion by division without pressuring individual respondents.
  • Use the due date for reminders and the until date for final closure.
  • Avoid changing enabled languages or division structure after launch unless necessary.
  • Keep a record of any study configuration changes.

After Results

  • Start with the formal maturity bottleneck.
  • Use investment to identify useful higher-level work.
  • Compare divisions to find local strengths that can become internal examples.
  • Convert advice into a short action plan with owner, timeframe, and evidence to collect.
  • Repeat the study only after enough time has passed for meaningful organizational change.

Interpreting Individual Perspectives

Individual results can reveal differences in how people experience learning practices. They should not be used to rank people. If individual advice is enabled, frame it as a perspective that may help explain variation across divisions.

Version Control

Keep the baseline instrument, scoring thresholds, and maturity-cell mapping versioned. If the instrument changes, keep old results tied to their original version so year-to-year comparisons remain valid.