Key takeaways
- Reviews answer “how did this person do.” Courses answer “what should they complete.”
- The learning guide only lists products whose pages describe a learning system.
- FeedbackPulse is not on that list. Its pages describe surveys, reviews, and a directory.
- Buying both is fine. Calling them the same product is not.
I keep getting decks that put a performance tool in a learning shortlist because the review has a development question. A development question is not a course. I split them before I compare prices.
Two objects, two lists
- ReviewA form and a deadline
- CourseA catalog and a completion
A review cycle has participants, a form, a deadline, and a completion report for the form. A learning system has a catalog, an assignment, and a completion report for the course. The performance guide and the learning guide stay separate so a buyer can see which object they are pricing.
Who I leave off the learning list
FeedbackPulse’s public pages describe pulse surveys, reviews, 360s, and an employee directory for growing teams. They do not describe a course catalog. I leave it off this list on purpose. It remains on the other three guides where the pages match. That is a filing decision, not a slight.
Buying both is a normal stack
A growing company can run reviews in one product and courses in 360Learning or Docebo. The employee record has to agree about who is on the team. That is an HRIS problem, and it is solvable. It does not require one login for every job.
How I tell them apart in a demo
I ask to assign a course to a person who is not in a review cycle, and to open a review for a person with no assigned course. If the seller cannot do one of those, the product is only one of the two objects. The questions I keep for the learning demo are in questions I take into an LMS demo.