Skip to main content

    Idea Pipeline

    Filter by idea status

    Filter by product area

    6162 Ideas

    TMaier
    TMaierHelper ⭐️

    Re-evaluate Scorecard Update Comment BehaviorNew Idea

    Hello! This is something that has bugged me for a while now and I remember a time when it wasn’t the case - something changed, but I’m not sure what the current expected behavior is either. Scorecard Measures contain a dedicated Timeline for special “update” entries that don’t show up on the normal Timelines. This is awesome because we’re able to tokenize datapoints used in the Set Score rules and I frequently use that mechanism to “show my work”. It helps users understand the selected score when they can see the math behind it. The issue that I’ve seen for some time now is that not EVERY Measure gets an update entry when the Set Score actions run. The previous explanation for this, if I recall, is that the Measure score must change in order for a comment to be generated. This is subideal, since it leaves gaps in Measures that don’t change and users sometimes question whether the score was recalculated correctly during the last scheduled rule cycle or not. Except, I’m also not sure that I quite buy that explanation of the expected behavior. I have some Measures that don’t change and DO get regular update entries every cycle no problem. I have other entries that HAVE clearly changed over time and show no entries whatsoever. What I’d like to see, in order of preference, is…Update entries are added to the Measure’s Timeline every time a Set Score Action runs, period. Consistent behavior across Measures regarding when an update entry is or is not added A clear and concise explanation of the expected behavior in Gainsight documentation

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

    Update filter for Badge IS NOT ONE OF to include users without badgesOpen

    As a Community Manager... I want to build segments that include users who have not yet earned a specific badge…In order to deliver personalized experiences and journeys viaWidget personalization features Email campaignsso that I can proactively guide them to the next the next step in their journey.  BlockerCurrent state The “[badge] Is not one of” filter only considers users who already have at least one badge; users with no badges at all aren’t included in the results. Engineering classifies this as a missing functionality rather than a bug, though I’ve flagged it with them as an unintuitive setup that could benefit from improvement. Behind my feedback that this setup is counter intuitive (I would assume that filter captures those without any badges), it’s a significant blocker on the ability to use the new widget personalization features and impediment to gamification journeys. Milestones and check points are often represented by a badge; we need a way to filter by those without the badge(s) in User Overview and save a a segment.  Additional use case: Analytics and Segmentation I want to build segments that include users who have not yet earned a specific badge…In order to understand the journey stages of users in my community.Yes, we can do the opposite [badge] is one of, but again that can be counter intuitive and requires calculation each time you want to answer the question of how many users do not yet have [badge(s)]. For example, our learning journey follows this pathIntro course → Novice Badge Level 1 program → Level 1 badge Role-based programs and certifications → role-based badges and certificationsIn designing experiences to guide users through all 3 phases of the path, and when reporting and briefing stakeholders, the focus is often on work to be done. Common questions I want to answer / metrics I want to provide: % of users do not have Novice badge or higher (blocked) % of users who have novice badge only (blocked - cannot combine badge-based filters … which I guess is another idea) % of users who do not have a role-based badge (blocked -- this would miss users without any badges) % of users who have a specific role-based badge (possible)Possible work arounds:Assign every user at least one entry level badge (silly, defeats the point of badges for differentiation) Also assign custom user roles for these badges (redundant and duplicative effort)