There's a setting/feature in Cognexo called ‘Full Stack’. Default is 10 questions.
Here's what it does. If a learner goes quiet for a while, questions don't just keep stacking up behind the scenes forever. Once they've got 10 unanswered sitting in their queue, Cognexo stops sending new ones. Instead it starts nudging them to come back and clear what's there.
The logic behind this. You'd think more questions waiting = more nudges = more chance they come back. Wrong direction entirely. What actually happens is someone opens the app after three weeks away, sees 40 unanswered questions, and closes it again. The backlog itself becomes the reason they never come back. So the cap exists to stop your own platform from talking someone out of re-engaging.
I mention this because when we're looking at QBR data and someone's "full stack" number is high, that's not a milestone, it's a warning. It means learners have hit the ceiling and are sat there waiting.
If you're an admin and 10 doesn't fit how your workforce actually uses the platform, it's adjustable and If you're a line manager and someone on your team is capped out, don't just tell them to go clear it. A few questions worth asking to get to the bottom of WHY they may be at full stack:
- "I noticed you've got a few questions waiting in Cognexo, what's getting in the way right now?"
- "Is it more that you haven't had time, or that the questions haven't felt relevant to your day-to-day?"
No replies yet