chapter
II
The building process
Where to start when building a product and assembling your remote team?
10 min read
The MVP
Build the smallest thing that can be useful first (a so-called MVP - minimum viable product).
Many early startups dissolve at this stage because they try to make the first version of their solution too complex. It takes too long to build and the startup runs out of money. You risk burning out before you even started. It’s much better to launch something early, despite it being far from perfect.
Then continuously improve on the main aspects of your product and user experience:
1. Design (Wireframes first)
2. Build
3. Show it to users
4. Collect their feedback
5. Based on what you learn, decide what to build or fix next.
The MVP
Build the smallest thing that can be useful first (a so-called MVP - minimum viable product).
Many early startups dissolve at this stage because they try to make the first version of their solution too complex. It takes too long to build and the startup runs out of money. You risk burning out before you even started. It’s much better to launch something early, despite it being far from perfect.
Then continuously improve on the main aspects of your product and user experience:
1. Design (Wireframes first)
2. Build
3. Show it to users
4. Collect their feedback
5. Based on what you learn, decide what to build or fix next.
Thank you for subscribing!
Subscribe to Building Remotely updates to get:
- Alerted for new podcasts and articles
- Summaries of our best insights from remote leaders
- Book chapters as they’re released
