Three questions people will ask you about Cognexo (and how to answer them off the cuff)

Had a few conversations this week where I had to explain how Cognexo actually works. If you've ever had a colleague, a line manager, or your own leadership ask "so how does this thing actually work" and felt yourself reaching for jargon, these are the three questions that come up most and how I'd answer them.

"How often are people actually being asked things?"
Two questions a day on compliance, plus a survey question layered in when one's due, and a quarterly % output assessment. It's not a big daily commitment, but it repeats, and that's the point. The same topic comes back round over time using spaced repetition, so it's not a one-off test where you either pass or forget it. It's less "did you learn this" and more "do you still know this in three months." And because we get great engagement, we use broadcasts as a communication tool to further embed new and changing process, policy and legislation.

"What happens to someone who's part-time or just started?"
Nobody's compared against someone who's been using it since day one. If you don't work a Monday, you don't get a question that day, and you don't lose anything for it. No penalty or catching up and no falling behind a colleague who happened to start earlier. Everyone just progresses against their own baseline based on their own competence at that time.

"How do you know it's actually working, not just people saying they feel confident?"
This is the one people push hardest on, and rightly so. If someone answers a question and shows they haven't actually read or understood something, like a policy or a safety update, it doesn't just get logged. The same question comes back a few days later to check the gap's actually closed. That's the difference between a sentiment score and proof of a behaviour change.

If you're ever put on the spot explaining Cognexo to someone who's never seen it, I'd lean on those three: frequency and repetition, fairness across different working patterns, and the follow-up loop that turns a wrong answer into a closed gap. 

Happy to go deeper on any of these if it helps.