Preseed Web Lab process.
This is what it looks like for each idea at Preseed Web Lab towards it’s transition into a Minimum Viable Product.
- Ideation — We have a habit of not letting go of problems the solutions to which(the idea) can greatly improve our very own lives, at the least. That has made us see problems as opportunities, as gaps that need to get filled anyway. The fun part starts when after tirelessly thinking, interacting with you and researching about possible solutions (apps//products/platforms that already exist, trying to solve the same or a similar problem), we get a crisp idea. That idea takes us into a journey suggested below. Its that, what feeds our soul.
- Brainstorming — We discuss it with Preseed Web Lab team of thinkers, hustlers, designers, hackers and if need be our extended network of some well achieved developers and entrepreneurs, for further validation, which kicks of the whole gammot of works (It’s at this stage the idea goes into our PWL Idea Sheet on which we manage multiple ideas we are either toying with or looking to toy with-:
a. Further Research — The most important aspect of today’s web development
1. Product Vision — At this stage a detailed research is done to ensure we are clearly differentiated from anything that already exists within the scope of our vision. This stage greatly influences our products feature list. Anyway, generally since the goal is to build the MVP first, we generally dabble with just one feature, that exact feature which solves the problem in question simply, no more, no less.
2. Communication of the product vision — We document the vision well enough to communicate with you, the hackers/hustlers/designer, to have you understand what we are looking for.
3. Product Development Satge 1 - Researching and identifying elements of a complete product that already exist. Open APIs have induced a culture of pre built solutions for most of what we would look for, for development. Thus, leaving most of the developers job today to research well in order to integrate all that exists and code only that, that doesn’t already exist. We try to ensure that it is through the hacks we build our products for the point we are trying to make is that MVPs should not take a lot of resources to build. (In fact Preseed Web Lab is about building products like that, while teaching the same to many, or atleast we hope so).
- b). Collaborative Whiteboarding (Done on mural.ly) and some sheets of papers for defining user experience — Here we together collaborate on anything that needs to be brought into our product plan perspective. The online collaborative nature of this stage ensures that our team can collaborate on research from wherever they are located.
c). Finally, packaging the concept so far on a mural to state the product vision, r&d data, UI/user experience perspective and product architecture broadly. (however this step is optional at our end, for sometimes in words we define the product vision and leave to the hackers to do the mockups based on their understanding of the product vision).
- MVP — This is where we need you, the hacker. The first iteration of the product is generally to build in the core functionality we need. Then we run a feedback loop among ourselves to translate the first iteration to a MVP. This MVP is actually about the first use case of the codes we are about to write. However when that first use case is achieved to satisfaction with many users using it, we may or may not move to tweaking the product to achieve other use cases too.
- Early adoption and lessons — While the hacker is building the MVP, the PWL management bakes the possibility of some early adoption for the purpose of testing through feedbacks. This system is about -
a). Prelauch Marketing
b). Creating such a seem less experience of feedback that more can be taken.
- Moved to Preseed Projects.
System of Preseed Web Lab
A brief look into a simple system of humanity we run Preseed Web Lab through.
Step 1 — Our semi thought of ideas get listed on the internal spread sheet.
Step 2 — All the corresponding details vis-vis the idea and it’s vision gets written into this internal spread sheet, as the idea starts maturing.
Step 3 — After the idea’s purpose is established with clarity over a period of time, it gets listed openly on the web page of Preseed Web Lab in those little boxes for all of you to take notice.
Step 4 — The prelaunch marketing and the parallel product vision documentation
Step 4a — The prelaunch marketing starts at this stage. To read about this further read another post by me titled Marketing precedes coding.
Step 4b — The product’s overall vision and, version v1 vision and features get listed. The product version 1 vision is the vision just about enough for the MVP to be useful enough to early adopters.
Step 5— We list opening for dev. at job boards like hasgeek or our own social media campaigns.
Step 6— People working on the idea get listed with their contact info once found through job boards like hasgeek, geek list, angel list etc. into the internal sheet and into Podio / Producteev work groups.
Step 7— Thereafter, they remain in constant dialogues with us towards achieving the MVP on our Product Vision.
Step 8 — MVPs get made; purely out of an idea, faith and remote collaboration.
Step 9 — They are made marketable based on the protocols defined on our main guiding sheet. We call this ‘Product Packaging checklist’ sheet. This is the sheet where we define the call to action for the product to now evolve itself in the market of early adopters.
Step 10 — The MVPs are then hustled with to translate them into customer validated products through our connections and know how into MVP launches for getting early adopters.
Step 11 — Imidiately after reasonable customer validation. The projects get listed on as Preseed Projects.
Step 12 — The projects are blown out of proportion here after, with more possible use cases, if relevant.