Tech startup iterations and evolution of technology stack - the lean way.

Tech startup iterations and evolution of technology stack - the lean way.

The goal of tech startup should be using iterations to move closer to desired result with minimal investment of time and resources while validating and improving the idea with every step.

The chosen technologies should be based on your team's expertise - what they know best. If you don't have a team then let the person you choose to lead your technology decide on the stack.

Let’s get straight to the point. Most tech startups can and should follow following iterations.

Iteration 1: Wireframes 

  • Pick a mockup tool (e.g. Balsamiq, draw.io, Marvel).
  • Visualize the end product/service in terms of rough mockups and user flows.
  • Share with a few close advisors.
  • Analyze feedback and incorporate changes into mockups if necessary.

 

Iteration 2: Prototype 

  • Choose a JavaScript framework (e.g. Angular). This is important so that the work you do during prototyping will be reused in the next iteration. Deploy on Amazon S3 as static website. This is also applicable to Mobile prototypes. You can create responsive prototype which can be viewed on a mobile device.
  • Create something people can play with. Don't worry about business logic. Just use some mocked data.
  • Share with a few close advisors and potential investors.
  • Analyze feedback and incorporate changes into prototype if necessary.

 

Iteration 3: Beta 

  • For native mobile apps: iOS/Swift and/or Android.
  • For Web applications: you already chose JavaScript framework in previous iteration. Stick with it and reuse as much as possible.
  • Choose service and database technologies (e.g. Service: Java, Spring Boot; DB: MySQL or Cassandra or MongoDB, depending on requirements).
  • Develop MVP (Most Viable Product).
  • Concentrate on attracting early adopters and not the mass target market.
  • Analyze progress and feedback and decide on improvements.

 

Iteration 4: V1.0.0

  • Continue with tech stack chosen in Iteration 3. Add new technologies only if necessary for new features (e.g. messaging, analytics, etc). Do not replace any existing technologies unless you discovered a real problem.  
  • Develop improvements from Beta iteration.
  • Kickoff marketing campaign (this depends on your business).
  • Analyze progress and feedback and decide on improvements.

 

Iteration 5..n: New  version(s) of the product

  • Only add one major improvement at a time, validate and measure success.
  • Iterate on a regular basis to stay ahead of competition and keep customers engaged.
  • Enjoy growth.          

 

A lot of work and details go into each iteration, but the important take away is: start small, make errors early, learn, validate, and take corrective actions.

----

"Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away."

- Antoine de Saint-Exupery

---

crisp and to the point.

Like
Reply

Thank you for the info. Very useful.

Like
Reply

To view or add a comment, sign in

More articles by Igor Royzis

Others also viewed

Explore content categories