Seth you familiar with the iron triangle? Good, fast, cheap pick two. You want it fast then it's either to be cheap but not very good or good but expensive. It's a good reminder that there is always a sacrifice that must be made.
In the product world we tend to thing more in MVP (minimum viable product). What is the thing that we can build that accomplishes the goal but has the absolute fewest bells and whistles. Maybe it doesn't scale or maybe it makes some assumptions for you on specific variables but once again sacrifices are made to ship it fast. You can always come back and add functionality if the hypothesis holds that there is value (usage/adoption) in it.
Great advice here! A practical way of giving realistic feedback on timelines.
Seth you familiar with the iron triangle? Good, fast, cheap pick two. You want it fast then it's either to be cheap but not very good or good but expensive. It's a good reminder that there is always a sacrifice that must be made.
In the product world we tend to thing more in MVP (minimum viable product). What is the thing that we can build that accomplishes the goal but has the absolute fewest bells and whistles. Maybe it doesn't scale or maybe it makes some assumptions for you on specific variables but once again sacrifices are made to ship it fast. You can always come back and add functionality if the hypothesis holds that there is value (usage/adoption) in it.