Product Lesson : Get out the door, quickly and so often

One week ago, I’ve learnt a marketing lesson, the hard way. I wanted to write it and may be posting it on my office’s wall.

So, let me start with a little bit of background.

The story started with me and my fellows building a high-tech product on top of open-source platform. The product has a R&D nature and it took us about 6 months to get our first proof-of-concept. It all started when we have been approached by a Tech Savvy from a Major Company (Let’s refer to him as Mr. X) to expand our technology to serve his needs as we have a niche expertise in this very specific field. Out of the definitions of Geoffrey Moore for customer types, I would call Mr. X a Technology Enthusiast/Savvy and an inventor, he’s very keen to try out new technologies at very crazy high frequency. And the visionary decision makers in his company (The Early Adopters Visionaries) would definitely refer to him to make investment decisions in technology and product in this field (That’s my own assessment).

So, what was the hard lesson ?

After we spent those first 6 months building our first most proof-of-concept, we took a decision that it’s not ready to show off to Mr. X, simply because it’s not perfect. And the hypothesis we had at that time, is that Mr. X (A corporate guy), won’t like a half baked solution. So, we spent another 8 months (Yes, way more that the first phase), trying to get our solution more into mass production, perfect, deployable shape. But after those 14 months spent, the product wasn’t ready to be consumed by public or even to be beta-released, and it’s still a proof-of-concept. So, now it’s 14 months with us working inside a lab, closing a door on ourselves, without giving or receiving any feedback from the initiator of the project idea. Then we decided, well, let’s just show him what we have. and we did.

So, here comes the lesson, we figured out that he went a long way past that idea, and he doesn’t need our solution anymore. And guess what, our proof-of-concept was a very good story for him that he got excited about it, and willing to reference us for other folks who are interested. 

The lesson here is clear, we should have approached him 6 months ago, he’s a Tech Enthusiast, and those guys doesn’t care if you have a half baked solution, as long as you’re giving them first hand on your technology, and give them the truth. They’re just willing to accept bugs and shortcomings if this will enable them to be atop of the ride. And the good part, is that they’re willing to give constructive feedback that could drive your product in a good way.

Not only going early to market would have been a good chance to get his hands on the tools and getting a quick feedback. But, also going early to market has the benefit of putting the team under market’s fire, and get them working at a light speed to satisfy the immediate customer needs. Instead of working at leisure with no direct pressure.

The take home message here, don’t be shy from showing your progress to Tech. Savvys, They’ll just help you for better steering, and may introduce you to visionary decision makers (Who usually use them for that purpose). And may get your product co-developed, or introduced to Market faster. Get out of the door, more often, and never shut your doors.


Focused Learning Plan

I had always an issue with focusing on reading one certain book and finish it before moving to the next, that doesn’t only make reading books takes longer, but it also reduces my ability to grasp the knowledge from each of those.

Another problem I’m facing also, is deciding what to read, and I tend to add huge number of books to my shopping cart, then ordering them later, only to actually read fraction of those.

But, now that I’m preparing for a Product Management position, I’ve decided to create a focused reading and learning plan to span the following categories :

  1. Technical (Coding Interviews)
  2. Marketing
  3. Entrepreneurship
  4. Management
  5. Design

Over a duration of 6 months, a total of 28 books to read and 10 online courses to take, with estimated total time requirement of 900 hours, beside a full-time Product Management job, that means a nightmare and a need for tight and efficient plan.

So, I’ve followed the following strategy :

  1. Breaking down the needed tasks in Trello board
    1. Book Reading Tasks (1 task of 10 hours/book)
    2. Book Summarizing Tasks (1 task of 5 hours/book)
    3. Course Following Tasks (1 task of 10 hours/course)
  2. Then to visualize my progress and my ideal burndown of those tasks, I’ve linked my trello account to

So, this is how my burndown chart looks like, right now.

Learning Burndown Chart 11 Nov 2015

And this is the list of books on my next 6 months plan :

Books to read, 11 Nov 2015

Now, let’s see how it goes. I’ll keep you posted  🙂