Description: During review sessions ahead of R2.1 launch, content stakeholders questioned why the Guide Card description text was required. It was determined that a full/proper conversation with the analytics team about what we can realistically measure for the GC descriptions is required.
A primary reason for this is: the GC description includes qualitative data points vs. quantitative (e.g., since there are no actions that the user takes to interact with the GC description, and since the description is required, we will not have the ability to compare the interaction performance between GCs that have descriptions vs GCs that do not have descriptions.), which will require discussion to refine testing.
Creating this backlog ticket so as to remind ourselves to review the possible guide card description text analytics.
Revisit if this ticket is necessary for further investigation following the results from the analytics from the Guide Card with Image and Description without Images on the Grants & Training page.
Description: During review sessions ahead of R2.1 launch, content stakeholders questioned why the Guide Card description text was required. It was determined that a full/proper conversation with the analytics team about what we can realistically measure for the GC descriptions is required.
A primary reason for this is: the GC description includes qualitative data points vs. quantitative (e.g., since there are no actions that the user takes to interact with the GC description, and since the description is required, we will not have the ability to compare the interaction performance between GCs that have descriptions vs GCs that do not have descriptions.), which will require discussion to refine testing.
Creating this backlog ticket so as to remind ourselves to review the possible guide card description text analytics.