![]() It sucks, right? We did this in a couple of days and it went along with what we had defined for this test: ![]() #7 - You’d go back to your GetSocial wordpress plugin and activate those (no code) and magic would happen.#6 - You’d leave the WordPress environment (again!) and configure the apps you’d want to use.#4 - You’d then request an API Key, copy it and paste it on your GetSocial wordpress plugin.#3 - You’d leave the WordPress environment and create an acocunt on GetSocial’s website.#2 - You’d search and install the GetSocial plugin (now the fun starts).#1 - You would login into your wordpress admin dashboard.I know I’ve said twice how poor the experience was but let me show you how it worked. Our test was clear: Do people fail to install our tools because of . Remember, we weren’t testing if a) the wordpress user converted to paying users faster or b) if the wordpress user installed more apps than the web version user. The experience was poor though, but that was not the point. This plugin would allow wordpress users to easily install, no code needed, GetSocial tools on their websites. So we took a shortcut and we created a humble and simple WordPress plugin. We didn’t want to spend 1 month of product development in improving something we weren’t 100% sure it would work out. ![]() It was a secondary (but important) goal to be fast. Think about it, how do you get paying users if they’re not even using/installing your product? So Nuno and the product team made a serious effort to remove any friction from the installation experience. But the message we were having from customers was clear: “I’m not using the product because I don’t know how to code”. We discussed copyright, we discussed removing features, creating a new onboarding process, etc. So low, we even stopped every paid acquisition (why bother?).īack in November the team defined that our main goal should be increasing our usage rate. So, getting back at my point, this was resulting on low usage rate. In a simple yet complete product, this would mean that a user could have to handle as much as 7 or 8 snippets of code to get the full deal. For that, she would have to install our library code (code #1) and code #x for every feature she would want to use. After a user creates her account at GetSocial, she will have to actually install our tools in her website. We were getting (disappointing) low usage rates. Some of you told us about it but most of all our metrics reflected it. ![]() It was an error from our side to expect you’d be ok with several snippets of code scattered across our product experience. I get it, we’re engineers, we complicate things. But for the last months, those tasks weren’t easy for most of you. Nothing makes us happier than people using and buying our product. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |