Micaiah_Chang comments on Who Wants To Start An Important Startup? - LessWrong

41 Post author: ShannonFriedman 16 August 2012 08:02PM

You are viewing a comment permalink. View the original post to see all comments and the full post content.

Comments (407)

You are viewing a single comment's thread. Show more comments above.

Comment author: sinak 18 August 2012 02:02:44AM *  2 points [-]

MIcaiah, thanks for the detailed and well thought-out response. I'll try and respond to some of your thoughts:

I imagine this would be very hard to monetize and get customers as-is.

As far as monetization goes, I think the best route would be to charge online education providers on per-API-call basis. The end goal would be to become something akin to the "Twilio of online learning." With a sufficiently developed system, I think it'll be possible to convince companies in the online learning space that this is a worthwhile value proposition for their users. End users who have committed to a particular online learning program are much more likely to be willing to use a spaced-repetition learning system to aid in their progress in a particular course.

Your emphasis though, would appear to be more oriented toward existing power users of SRS.

I think I gave the wrong impression here, I think I'd much rather target non-users of SRS. Building something simpler but more accessible seems like a more viable alternative. Gaining traction with average, non-SRSing users, and then later adding best-of-breed features to tempt online learning providers seems like a more reasonable approach.

The average user needs to be sold on the effectiveness of a product very fast, on the first usage (or perhaps even sooner!) in order for them to continue using. However, SRS software in general are almost by definition antithetical to that goal: Their benefits do not come until far into the future, worse still it's an undefined time in the future.

I've thought of a couple of simple use cases for this sort of platform that I think seem easy to build and quite compelling for an average non-SRS user:

  • Vocabulary expansion - For People looking to expand their vocabulary - a simple javascript bookmarklet that would allow users to learn the definitions of new words that they come across.
  • "Remember what you read" - It seems that given the number of things that an average person might hope to learn in a particular day, but which are instead soon forgotten, having a simple way to record those items would be quite immediately valuable. For example, as soon as I found Instapaper, I began saving documents that I wanted to read later. I could see a simple javascript bookmarklet for "things I've read online and want to commit to memory" being used in a similar fashion. This implementation would be a very, very crude version of SRS, but I think it could help get users on board.
  • Name-Face Identification - A tool that helps users learn the names of all the contacts in their LinkedIn or Facebook friends lists. Forgetting the names of acquaintances is a common problem, and an SRS program is an ideal solution.

Beginning with a simple, self-curated deck like the ones described above would also help to avoid the problem of not having good content for first-time users.

Very interested to hear feedback on the above.

Comment author: Micaiah_Chang 19 August 2012 08:23:38PM 2 points [-]

All three look promising. However, you might be pidgeonholing yourself by trying to go back to the "SRS as generalized learning tool". For most people, it would appear as if that's too abstract. You may be much better off focusing on the most generally appealing use case (The name-face ID one sounds the most promising; I can't imagine any people who weren't already self-motivated autodidacts using the first two). In fact, it might turn out to be much better than than the original Anki-as-service app; it appears to me that many more people view "oh god what's her name I just met her a week ago THINK" as a problem than "Oh, hm, it appears I've forgotten how to say 'praying mantis' in Japanese".

To extend the Name-Face identification concept, you could also add things such as people's birthdays, dates of important events such as anniversaries into it; although I'm not sure how many of those things aren't problems anymore because of calenders etc.

I can't comment too much on the "Twilio of online learning" idea; I don't know the interest level of online courses such as Udacity, Coursera and Codeacademy on something like that. Although I will warn that there's a real risk that it'll be treated as "just another complicated feature that I don't need to use" by the average student. But if you get a hardcore userbase who are happy with the product and willing to give feedback then you're in much better shape than trying to arbitrarily design for the "average" user.