Skip to content

Category Maturity (CM) Scorecard testing iteration II

Adam Smolinski requested to merge asmolinski2-master-patch-71549 into master

Why is this change being made?

After the most recent wave (July 2020) of CM Scorecard testing utilizing the current process, there were some themes in the feedback that need to be addressed for the next iteration of CM Scorecard testing:

  • Too time consuming, overall
  • Too many JTBD/tasks
  • Too heavy of a process
  • Accuracy concerns

To address the above, a new iteration has been developed and is captured in this MR. The new iteration leverages the existing and proven UX Scorecard measuring process. The proposed iteration aligns the UX Scorecard process & the CM Scorecard testing process by using the same scoring criteria. In theory, this allows the team to conduct a lightweight UX Scorecard to infer where the experience may land with CM Scorecard testing.

NOTE: The wording of the UMUX Lite question is currently being evaluated and validated. This may result in an update to the wording of this question in the near future.

Author Checklist

  • Provided a concise title for the MR
  • Added a description to this MR explaining the reasons for the proposed change, per [say-why-not-just-what][transparency]
  • Assign this change to the correct DRI
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager.
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in [#mr-buddies][mr-buddies-slack].
    • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files.
Edited by Adam Smolinski

Merge request reports