Skip to main content

    Idea Pipeline

    Filter by idea status

    Filter by product area

    6164 Ideas

    PeterG_1P
    PeterG_1PContributor ⭐️

    Skilljar: backup / export at course levelNew Idea

    It would be helpful for Skilljar by Gainsight to include additional backup / export functionality, as this increases data resiliency, and could improve the ability of teams to review and update content on an ongoing basis. The Current StateCurrently: There is no graphical UI affordance to allow users to export, backup, or download course text content at the lesson level. It is possible to select each Content section, select Source Code, and manually copy / paste each section in order to back it up to another location. It isn’t possible to export the entirety of a course (encompassing multiple lessons) or multiple courses. It isn’t possible to export HTML lesson content as a SCORM file (although it is possible to create a lesson from an existing SCORM file). It is possible to download Assets (videos, images) and SCORM files.In total, if a Skilljar user wants to export content from Skilljar, this is currently an intensive manual process, or would require a script to attempt to crawl the site and download content. Possible SolutionsA graphical UI element or menu that allows the user to export content, ideally at the course level.For example: an export of HTML files for each lesson, packaged and zipped in a folder/file hierarchy that mirrors the course / lesson hierarchy. Associated media assets (images, movie files) could be included in the folder of a given lesson, along with the lesson’s HTML file. Operational GoalsIncrease data resiliency. Give the customer the ability to store current Skilljar course data in a secondary location to reduce risk to data. Backups are key to any organization’s data resilience strategy. Improve ease of review for course material updates. For example, some companies may require consultation with internal stakeholders before a team makes updates to a published course. Such reviews are typically easiest to accomplish using internal company platforms and collaborative document-sharing solutions. They also help avoid the temptation of provisioning Skilljar access for team members who usually don’t need it. The ability to export HTML data from Skilljar opens the door to implement content updates more systematically or even programmatically - for example, if we are implementing updates to a brand name, “replace all X with Y” becomes easier with a data export feature. Currently a Skilljar user needs to manually edit each section in each lesson of each course iteratively. Increase the value of other product features. For example, proposed product Ideas like content version control, when combined with backup functionality, could allow a team to 1) Take a report from a customer about incorrect or outdated course content, 2) identify who authored the content and when, 3) conduct internal review to identify new content to be published, and 4) implement the new content in Skilljar - secure in the knowledge that it’s safe to do so, because the existing content is doubly protected from data loss by both version control (snapshot / rollback functionality) and the export feature (functionally an offsite backup). Align with existing Skilljar functionality. Skilljar offers a download button in the Assets and SCORM tabs already. Adding similar functionality to courses would extend the design logic of existing UI affordances to the most useful level for customers looking to ensure data resilience.

    DannyPancratz
    DannyPancratzVIP ⭐️⭐️⭐️⭐️⭐️

    Product-wide URL Exclusion Rules for EngagementsNew Idea

    As an AdminI want to set a “global” rule to exclude certain URLs from ALL engagementsIn order toEnsure specific pages of the UI do not trigger engagements Login/log out pages {other pages specific to customer products and UX} Ensure consistency / avoid human error Especially when working with a team of partial-admins who can launch engagements Avoid repetitive/duplicative work to always exclude the same URLs for each engagement Use Case ExampleProduct has multiple entry points / users might go straight to a specific URL, rather than always land on home page Want to show a certain engagement when users begin their session, regardless of which page they start on (minus certain exclusions) NPS and other surveys Alerts and info (ex. product upgrades, issues, etc) Marketing (webinar promotion, etc) Intentional Friction / Customer Journey (ex. “you haven’t completed your onboarding yet, click here”) Current State Pain PointsEngagements had been showing on our login/logout authorization pages Users were previously identified from earlier sessions Users initiated a session that the began with a log-in page, but engagement triggered based on user attributes from previous identify call / PX cookies fitting them into audience criteria May be identified from session in same browser in a different instance/environment (ex. Partners/Consultants working with multiple Customers)   To avoid this for the many use cases above, we have to remember to / audit whether each engagement is set to exclude these URLs. Thus:  Added effort to set up and/or audit Risk of human error, especially across teams

    DannyPancratz
    DannyPancratzVIP ⭐️⭐️⭐️⭐️⭐️

    Trigger Engagement from Multiple BadgesNew Idea

    When I am creating an engagement for {business objective}I want to have the ability to trigger that single engagement from every place relevant within the UXin order to Have all the metrics for that one initiative/objective within one engagement + add holistic engagement metrics to dashboards within a single widget Have audience & schedule (recurrence) rules within one engagement  And ultimately to avoid the extra work/hassle/complexity of logic of duplicating the engagement multiple times and configuring audience logic / recurrence rules manually combining the engagement metrics into a single report Example Use CasesWhen there are a suite of features or related features that exist on multiple pages of the UI, and perhaps you want to engage users on each screen of the UI: Survey users about this feature suite Collect specific feedback about this feature suite  Inform users about this feature suite on each screen of the UI A relevant upcoming change An alert about an existing issue Best practices Link to documentation (new features, beta features, etc) Trigger an on-demand onboarding/tutorial flow (new features, beta features, etc)Similarly, if you wanted to do similar things specific to the customer journey across multiple screens of the UIGuide them to the next stage of their learning journey Alert them about an expiring certification or missing pre-requisite Promote a webinar

    sam.walker
    sam.walkerHelper ⭐️

    Support content version controlNew Idea

    It would be very useful if Skilljar could allow us to version content, including restoring previous versions and surfacing different versions of content to learners.We have two use cases that would greatly benefit from content versioning and might require different solutions.Restoring courses or lessons It’s currently possible to, for example, accidentally delete an entire text lesson, save the lesson, and then be unable to retrieve the lost content. This can also happen when two Dashboard users edit the same lesson and overwrite each other’s changes. Support for viewing and restoring previous versions could fix this risky situation. Google Doc’s Version History interface is a good model for this. This is a more “automatic” approach to versioning. Surfacing content that matches learners’ software version. Our desktop and server products use a traditional versioned release model. This fact means our courses have to correspond to a specific release. Learners ideally take the training using the exact version matching the course content so that the UI and functionality match exactly. They cannot even take the newer training if they have an older version because the provided instructions and example files will not be compatible. Therefore, we’d like to support surfacing different versions of content to users. This feature is common in software documentation. For example, click Other Versions on this page: https://pro.arcgis.com/en/pro-app/latest/arcpy/main/arcgis-pro-arcpy-reference.htm. Most solutions support this use URLs to indicate which version is being used. These names are usually branches or releases in a version control system. https://pro.arcgis.com/en/pro-app/latest/arcpy/main/arcgis-pro-arcpy-reference.htm https://pro.arcgis.com/en/pro-app/3.4/arcpy/main/arcgis-pro-arcpy-reference.htm Our current workaround uses course names, tags, and published course URLs to let users choose which training version to take. But we know learners struggle to find the right content, particularly when using an older software version. This is a more manual approach to versioning.

    sam.walker
    sam.walkerHelper ⭐️

    Learning path and lesson completion metrics graphNew Idea

    ProblemThe completion rate is one of the most useful metrics to me as a course manager. This metric indicates if learners are empowered and motivated to complete a course. We can currently easily view this for individual courses, which is useful, but specific and more useful pieces of information require manual work to extract:Completion rate by course within a learning path Completion rate by lesson with a course This sort of exists, but you can only see lesson views, not completion rates Completion rate by lesson by course within a learning pathThese visualizations/tables built into the Dashboard Analytics would significantly reduce manual effort.Potential SolutionsI've attached an Excel workbook with mockups of what I'm picturing. The data is fake. The third option (lessons in courses in a path) presents a pretty overwhelming chart so that it might be better presented as a table. Or perhaps a table with sparklines.I can get all this data from the Analytics section, but putting it together in this format requires manual work.My preferred route to get to these would be:Dashboard > Analytics & Reports > Reports > Paths > click a path in the list That currently goes to a page of path enrollments. Perhaps you could copy the behavior that happens if you click a course from the Courses report. That takes you to a tabbed view of Enrollments and Lessons. In this case, for paths, it would take you to a tabbed view of Enrollments and Courses. Then the Courses page would have the course completion rates within the path as a table and chart. Dashboard Analytics & Reports > Reports > Paths > click a path in the list Same path as above. Again, adding it as a tab on the specific course analytics page would work. Add a tab called Lessons and show a table and chart of the completion rate for all lessons in all courses in a path, in order. If you think of this more as "analytics" rather than "reports," I could see an argument for adding a Path entry to the Analytics section in Analytics & Reports instead. But I think the pages would end up being pretty similar. You could even do both. If you do that, you might also need to do the same for courses. In that case, I'd just add completion rate as a column on the existing course analytics page.These proposed pages are similar to the existing view you get if you click a course on the Course page in Analytics. However, that page only shows lessons within a course, and I would also greatly prefer it to show the lesson completion rate rather than the lesson views or time. We use quizzes on every page to gate completion and "prove" the student engaged with that page. But I think the location of this page in the Dashboard and the general layout of the page could be cribbed for these charts.

    bradley
    bradleyExpert ⭐️

    Improve Group Send Engagement ReportingNew Idea

    Group Send has some features that are helpful on the surface for users - one of those is the ability to report on email engagement OOB in the Home UI. This is about the reporting itself, as I find the options to be a bit disingenuous and incomplete. Specifically, I’m referencing this Email Log V2>Status field which even appears in the documentation:  There is no such Status field in Email Log V2. This could present a problem if users see this and want their admin to create a similar report (or, if they have report builder access try and create their own) because those options are actually different fields. Email Logs had a single field similar to this, but they are not the same and Email Logs shouldn’t still even be getting data. Failed does not appear to be a relevant data point in Email Log V2, so I’m not sure what that is referencing. Again, see prior bullet point. Unsubscribed, Rejected, (marked as) Spam are *not* on this list but they *are* reportable in Email Log V2. It seems like those would be relevant to include here - are they all captured under “failed”?.Why was a field seemingly fabricated out of thin air, reference an existing MDA, but not accurately reflect the data in the object itself? Please review this field/filter option and have it more accurately reflect the data in the object it is referencing. Please also add the field itself to the MDA object so it is usable outside of this single UI element.