Retrospective on ScrumPad Product/Market Fit
The first stop in the journey is "Product/market fit." For the uninitiated (I am not an expert either, learning from doing), all it means is to prove that there is a large enough of a market for the product or service that I am building. The goals of this stage of a new business development is to identify/define that market with specific details- who are the users, why they like our product, and the business model that would work the best, and a repeatable sales model.
The best way to do this is to look back to understand where we are (since it's been 18 months that we are working on ScrumPad, but did not apply leanstartup model). I'll break the retrospective in two parts- 2008 retrospective, and 2009 retrospective.
Version 1- Free ScrumPad: 2008 Retrospective
What was our hypothesis?
All started with a itch of ours. We looked for a tool that fits our needs. We found two- Basecamp and Version One. But, none was what we were looking for. After trying both, we had decided to build one that we liked. So, since we liked what we had built, we thought there must be more like us who would also like ScrumPad.
How long did we spend to validate this hypothesis?
6 months.
What did we do during this period?
- We primarily focused on adding functionality (product development, not customer.). We thought more functionality = more satisfaction = more users.
- We were releasing incremental version of ScrumPad every two weeks using Agile/Scrum process.
- We did not do anything on the customer development front. Did not do any marketing. Did not talk to customers for feedback (did not get out of the building).
- We completely deferred design thinking that design and usability is secondary to functionality. We thought once we have the functionalities in, we could always add design and improve usability.
- We did not charge for our service. We thought we need to first build out the full product (not thought about an MVP) before we can start charging.
- We did put some basic tracking- Google analytics as well as some custom ones (i.e., number of projects, users, and overall project activity index that we defined). It helped us detect some early issues with signup and getting started with ScrumPad.
We did get a constant stream of SEO traffic from search engines. This traffic resulted in a trickle conversion 1 to 2 every week. Received some unsolicited feedback, primarily from those who liked it. However, when we started charging in early 2009, most of the users from 2008 stopped using the service.
New Visits Bounce rate Avg. Time on Site Pages per visit Conversions
3,521 48% 00:02:50 2.61 5%
What did we learn?
Our product is better than the opensource counterparts. However, as a paid service, we did not learn anything about whether we have a market yet as a paid service.
- We changed our logo, updated the UI, and continued to tweak the interface to improve usability.
- However, we spent a significant amount of time in refactoring (rework) to fix the sprawling code-base that resulted from the quick piling up of functionality.
- We started actively asking for feedback. We in fact incorporated a short exit interview during the cancellation process.
- We did not charge for our service. We thought we need to first build out the full product before we can start charging.
- We still did not do any CPC marketing.

Recent Comments