Moodlepreneur Monday: Dos And Don’t In Pitching xAPI (Or Whatever Your Tech Edge Is)
“Contacting SkyNet” by Christopher Michel is licensed under CC BY 2.0
“3D Tin Can Phones” by Chris Potter is licensed under CC BY 2.0

Controversial a practice as it is, Rustici’s banding efforts are worth considering. On the positive side, they have played an active role in promoting open standards in EdTech. A large component of their model involves xAPI, CMI5 and even SCORM. A play so successful, many still think “Tin Can,” a Rustici’s trademark, is xAPI’s actual name. Rustici was also savvy enough to register the and the domains. Its SCORM Cloud plugin family, a non-free bundle, has become the de facto driver for Moodle.

Post Pages - Post Inline - WIRIS

Previously in MoodleNews: Attention Learning and Development professionals – Check out the difference between SCORM & cmi5 standards

Even Rustici is aware of the limits of shoving a branded technology. A recent presentation by Chris Tompkins discusses Request For Proposals, and leveraging technological differentiators. Here are 3 of their most sensible tips.

Don’t assume. Plain and simple. Do your best not to believe many assumptions out of the gate: That everyone needs your tech. That spending so much into building an advantage makes it exciting for people. Above all, that your cutting-edge tech is all you can offer. Expertise is supposed to be a broadening, multi-threaded process.

Learn to “nurse” your customer. Don’t keep at it with xAPI if you had them at SCORM. We sure wish things were different, but cash-prudent organizations need cost-effective learning solutions with clear short-term results. Bogging them down with your manifesto of xAPI as the gate towards a new stage in collective consciousness might not elicit the kind of business response that would keep you afloat. As promising as xAPI can be, it continues to be challenging to sell the burdens its implementation and ongoing deployment would ensue to run-of-the-mill learning organizations. Identify the technological ability and warmth of your potential customer, and appeal to it first and foremost.

Establish a dialog about affordances. Do not think disinterest for your tech means your vision is not worth pursuing. Find the sweet spot between your potential customer’s contractual demands and your core value propositions. Offering your unique tech edge as an added bonus, instead of a paid-for feature, changes the frame of mind. Users will be more tolerant to experimentation and be more open to an emotional relationship with the benefits your tech provides to them.

View “Adding xAPI to your RFPs: Rethinking your process” at■

eThink LogoThis Moodle Practice related post is made possible by: eThink Education, a Certified Moodle Partner that provides a fully-managed Moodle experience including implementation, integration, cloud-hosting, and management services. To learn more about eThink, click here.

Previous articleWe Are Your Friends. Moodle Users Association Ponders Annual Plan To Aid Moodle HQ
Next articleFBI Warnings To EdTech Makers And The User Community


Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.