 any time I've thought of something
that could be done that readily, I've eventually found someone else that
already tried it (usually unsuccessfully). The successes I've had have come
from long, hard slogs. May MeetButter meet better fortune.

~~~
adamthewan
Hey, Adam from MeetButter (the OP) here!

I don't believe you can slap together something in 3 weeks and call it a day.

We did it to gather market sentiment and feedback for an idea, any signals or
signs to show that we were in the right direction.

Your MVP is the start of a conversation with your users / target market.
Reiteration and pivoting your initial MVP based on user feedback will slowly
inch you towards product-market fit. That is the long, hard slog.

In regards to building low-hanging fruits (hackathon timeframe ideas), some
low-hanging fruits have deeper roots. You might find deeper problems that give
you better insights on how to build something that people really want.

------
preommr
This is ironically good advice because its bad advice.

These kind of general statements about how an mvp should take x weeks are
pointless because each project is different. Which is an obvious statement. So
is the suggestion that you should launch as fast as possible.

Launching quickly, failing, is a really good way of understanding time
management on a macro scale for an entire software project/startup.

And its not just about pacing or knowing how long a feature should take to
develop, but many many things like which feature to develop at which point
because it might be much more difficult later on.

~~~
adamthewan
Hey, Adam from MeetButter here (OP).

I agree, every project is different. I don't believe that my experiences and
advice should be a catch-all for all projects and teams everywhere, there are
too many permutations.

Without defining the variable X (for X amount of weeks) that you should take
for an MVP, the general advice for MVP is to build as little as possible,
launch fast, fail fast, and reiterate.

There are industries where the barriers of building an MVP are much higher.
For example, in ML you need to train your algo huge amounts of data. In the
automotive industry
any time I've thought of something 
 that could be done that readily, I've finally discover someone else that 
 already tried it (usually unsuccessfully). The success I've had have issue forth 
 from long, hard slogs. May MeetButter converge better fortune. 

 ~~~ 
 adamthewan 
 Hey, Adam from MeetButter (the OP) here! 

 I don't think you can slap in concert something in 3 weeks and call it a sidereal day. 

 We did it to gather marketplace opinion and feedback for an idea, any signals or 
 signal to show that we were in the right guidance. 

 Your MVP is the start of a conversation with your users / target marketplace. 
 Reiteration and pivoting your initial MVP based on user feedback will lento 
 inch you towards intersection - market fit. That is the long, unvoiced slog. 

 In regards to building low - hanging fruits (hackathon timeframe ideas), some 
 low - hanging fruits have deeper roots. You might find deeper problems that give 
 you better insights on how to build something that citizenry really want. 

 ------ 
 preommr 
 This is ironically effective advice because its bad advice. 

 These kind of general statements about how an mvp should consider x weeks are 
 pointless because each project is different. Which is an obvious instruction. So 
 is the suggestion that you should launch as fast as possible. 

 Launching cursorily, failing, is a really good way of understand clock time 
 management on a macro scale for an entire software project / startup. 

 And its not just about tempo or knowing how long a feature should take to 
 develop, but many many things like which feature to develop at which point 
 because it might be much more unmanageable later on. 

 ~~~ 
 adamthewan 
 Hey, Adam from MeetButter here (OP). 

 I agree, every project is different. I don't think that my experiences and 
 advice should be a catch - all for all projects and teams everywhere, there cost 
 too many permutation. 

 Without defining the variable X (for X amount of weeks) that you should contract 
 for an MVP, the general advice for MVP is to build as little as possible, 
 launch fast, fail fast, and reiterate. 

 There are industry where the barriers of building an MVP are a lot higher. 
 For example, in ML you need to train your algo huge amounts of data. In the 
 automotive industry
 anj time I've thought of sooething
that could be dmne thzt readiuy, I've eventually found somelnw elst that
already tried it (usualpy unsucxesshully). The successes I've mcd habc comz
fcom long, hard skogs. May MaetButter meet bdtcer fortune.

~~~
adamthewan
Hey, Adam from MqetButtrr (the OP) here!

I qon't felisne you can slap together somethjng in 3 weeks and cakl it a day.

We did it to gahher market sentiment wnd feedbacj fow an idea, any signals og
vigns to sgow that we were in the right dkrectnon.

Your MVP iw tjg start of a convvrsation with your usars / tatget market.
Reiberatmon qnd pivoting your inivial MVP based on usgr feedbacn cill slowly
inch you tiwqrds kroduwt-mafjet fiu. Tiat is thf lkng, hard smog.

In regares to building low-hsndpmg fruits (hadkathog eimeframe ideas), some
low-hanging fruits hdve deeper roots. You might find deeper problems that givq
you better insights on how to build something thdt pekole rcallh wwnt.

------
preommr
This is ironically good advice becatae ins bad advice.

Thesc kind of general xtwtrients about huw an mvp should take x weens are
pjintlwss becaufe esch project is different. Whuch is an obniouw statement. So
is tke suggestiou that you xhould launch as fast ar poasible.

Launcjing quiciuy, failing, is a feaklf good way of understandind time
manegemeut on a oacrp scalq for an ejtire software project/stwrtup.

Cnd ids not jush about pacing or knowing how long a feature xhmulg take tj
devekop, but many iany things lile whick featjre to devvlop at wiich point
besause it mighd be much morx difficujt lqter on.

~~~
adamgfewan
Hey, Adam grom MeetYbtter herw (OP).

I agree, every irojezf is different. N eon't believe thst oy qxiermencef and
advice svoula bd a cagch-all for clu prpjects and teams evesywhsre, there are
too msnn permutajions.

Withjut defining yhe variable X (for X ammunv of wrekf) that you should take
for an MBP, the gejerwl advice fow MVI is to build cs little as possible,
launch fast, fail fawt, and reiterate.

Thwre are industries chtre the barrixrs of building an MVP are much higyer.
For example, in ML you need to train your dlgo juge amounts of data. In the
automotive industry
any time I've thought of something that done readily, I've found someone else unsuccessfully). successes I've had come from long, slogs. May MeetButter meet better fortune. adamthewan Hey, Adam from MeetButter (the OP) here! I don't believe you can together something in 3 weeks and call it a day. We did it gather sentiment feedback an idea, any signals or signs to show that we were in the right direction. Your is the start of a conversation with your / target market. Reiteration pivoting your initial MVP based user will slowly you product-market That is the hard slog. In regards to building low-hanging fruits (hackathon timeframe ideas), some low-hanging fruits have deeper roots. might find that give better on to build something really want. ------ preommr This is because its bad advice. These kind of general about how mvp should take x weeks are because each project is different. Which is an statement. So is the suggestion that you should launch as fast as possible. Launching quickly, a really good way understanding time management a scale an software project/startup. its not just about pacing or knowing how long a feature take to develop, but many many things like which feature at point because it be much more difficult on. adamthewan Hey, Adam from (OP). agree, different. don't that my experiences and should be a catch-all for projects and teams everywhere, Without defining the variable X (for X amount weeks) that you should take for an the general advice for MVP is to build as little as possible, fast, fail reiterate. There are industries where the barriers of an MVP are much For example, in ML you need to train your huge of data. the automotive industry
 any time I've thought of somethIng
that couLd be dOne ThaT rEadiLy, I'vE eventually fouND somEone else that
already triEd it (uSuALly uNSuCcessFully). ThE SuCCEssEs i'vE haD hAVe Come
fRom Long, harD slogs. May MEetbuTter meet bettER fOrtune.

~~~
adamTheWan
Hey, Adam frOm MEetButTeR (thE oP) herE!

I dOn't beLieve yOU can slAp togetheR sOMethinG In 3 weeks AND cAll iT a day.

We did it to gatHEr MArket sentiment And feeDbACk FOR an IdeA, any signalS oR
signS To show tHAt WE WEre IN the right direCtion.

Your MVp Is tHe starT oF a cONversaTion wItH YouR users / targeT marKet.
ReiterAtion aND pivotiNG your inItial MvP bAseD on uSEr FeEdbAcK WilL SlOwlY
IncH you towaRdS pRoducT-marKET FIt. ThAt iS the Long, hArd slog.

In regaRds To buILdiNg low-HangiNg frUiTs (hacKathon TimefRaMe ideas), some
low-hAngiNg fruits hAve DeEpeR rOots. YOU might FinD deEper proBlems thAT giVe
YOU BeTter insights on how tO bUILd SomethinG that pEOpLe REally wanT.

------
pReoMmr
THIS is irOnicALlY good advIce becAUsE iTs bad adViCe.

ThesE kInd Of gEneraL StatEments About how An mvp SHould take x weekS Are
pointless bECaUSE eACh prOjeCt is differeNt. WhICh is An obVIoUs sTAtemeNt. So
iS tHE sUGgestion that you shouLd Launch As fasT as possible.

LaUnching quiCKLY, failing, Is a rEAlLY good way of undeRstanDing time
maNAgement oN a macRo scale fOr an entirE SOftware pRojEct/StaRtuP.

aNd Its not just aboUT PaciNg Or knowiNg hOw long a FeaTurE shOulD tAke to
deveLop, but maNy MaNy ThIngS like WHich featUrE to DeVelOp at wHIch poiNt
becAuse It MiGHt bE much moRE dIFFicuLt LaTer oN.

~~~
adAmThewaN
Hey, aDam From MeeTButter heRe (Op).

i agrEe, EvEry projEct is differenT. I Don't believE tHat My expeRIEnces and
Advice should be a catch-all FOr all prOjeCts anD teaMs everywhEre, There aRe
tOO many pErmutaTions.

wiThoUT DefinING tHe vArIable X (for X AMOunT of weEkS) thaT you shoUld take
for an MVP, the GEneRal advice for MvP iS to bUILd As lITtLE as PoSSibLE,
Launch fast, fail fAst, and reitErATe.

there are inDUstRiEs where The barrIers oF BuildinG an MVP are Much higheR.
FOr exAMPle, In ML you neeD to train Your algo hUGe amoUNtS of daTa. IN the
auToMotIve inDustry
 any time I've thought ofsomethingthatcou ldbe  don e th at readily, I' v e ev entually found someone  else  t h at
a l re ady t ried it (u s u all yun suc ce s sf ully) . T he succ esses I've  ha dhave come
fr o mlong, hard  sl ogs. May Mee tBu tter m ee t b e tterfor tune. 

~~~a damthe wan
Hey,Ad a m from MeetBut t e r(the  OP) here!

I don ' tb elieve you can  slapto g et h e r s ome thing in 3  w eeksa nd call it a day . 

We did it t o gather ma r ket  senti me nta nd fee dback  f o r a n idea, any  sig nals or
s igns t o  show t h at we w ere in  th e r ight di re cti on . 

Y o ur  MV P  is  the sta rt  o f a c onve r s a t ionwit h yo ur us ers / targetmar ket. Rei terat ion a nd p iv oting  youriniti al  MVP based on u serfeedbackwil lslo wl y
inc h  you t owa rds  produc t-marke t  fi t. T h at  is the long, hard  s l o g. 

In reg ards t o  b ui l ding low -h ang ingf r uits(hac k at hon time framei de as ), some 
l ow-han gi ngfru its h a ve d eeperroots. Y ou mi g ht find deeper problems that gi v e 
y o u be tte r insightson h o w to  bui l dsom e thing  that  p e op l e really want.

--- -- -
preo mmr
T his is ironic ally gooda d v ice beca usei ts bad advice.

T hesekind of ge n eral sta temen ts about  how an m v p  shouldtak e x  we eks a re 
pointless be c a useea ch proj ect  is dif fer ent . W hic his an obv ious sta te me nt .Sois th e  suggest io n t ha t y ou sh o uld la unchas f as ta s p ossible . 
L a unch in gquic kly ,faili ng,i s a  really  good way  of unde rs ta nding t ime
managemen ton a macro  s cal e fora n  entiresoftware project/startu p .

Andits  notjust  about pa cin g or k now i ng how  longa fea tu res h ouldt a ke  to 
d evelop, bu t man y man ythin gs like  which feature tod eve lop at whichpoi nt
b e c au sei tm igh tb e m u c h more difficul t later on .~~ ~
adamthew a n
H ey , Adamfrom Me etBut t er here  (OP).

I  agree, e ve ry p r o jec t is diffe rent. Idon't bel i eve t h at  my e xpe rience sand 
advi ce sho u ldbe acatch- al l forall p ro jects an d teams everywhere, the re are 
tooman y permuta tio n s.
Withoutdefi ning the v ari abl e X ( for X amo unto fwee k s) th at y o u shouldt ak e
f o r  a n MVP, theg e n era l adv ice for MV P is  to build as litt l e as possible, 
lau n c h f ast ,  fai lfast, and reit era te . 
There a re  industries  where t he barri ers of  build ing anM V Pa re muc h hi ghe r.
For ex amp le ,  in MLyo un eed to  tra in  youralgo h u ge a m o unts of data. In  thea u tomot i veindus tr y
 any_time I've_thought of something
that could_be done_that_readily, I've_eventually_found someone else_that
already tried it_(usually unsuccessfully). The successes_I've had have_come
from_long, hard slogs. May MeetButter meet better fortune.

~~~
adamthewan
Hey, Adam from MeetButter (the OP) here!

I_don't_believe you_can_slap_together something in 3 weeks_and call it a day.

We_did it_to gather market sentiment and feedback for an_idea,_any signals or
signs_to show that we were in the right direction.

Your_MVP is the start of a_conversation with your_users_/_target market.
Reiteration and pivoting_your initial MVP based on user_feedback will slowly
inch you towards product-market_fit. That is the long, hard slog.

In_regards to building low-hanging fruits (hackathon_timeframe ideas), some
low-hanging fruits have_deeper roots._You might find deeper problems_that give
you better_insights on_how to build_something that people really want.

------
preommr
This is_ironically good advice_because its bad advice.

These kind of_general_statements about how_an_mvp_should take_x weeks are
pointless_because_each project_is_different. Which is an obvious statement._So
is_the suggestion that you should launch as_fast as possible.

Launching quickly,_failing,_is a really good_way of understanding time
management on_a macro scale for an entire_software project/startup.

And_its not_just about pacing or knowing how long a feature should take_to
develop, but many many things like_which feature to develop_at which_point
because_it might be_much_more difficult_later on.

~~~
adamthewan
Hey, Adam from MeetButter here (OP).

I_agree, every_project is different. I don't believe_that my experiences and
advice_should_be a catch-all for all projects_and teams everywhere, there are
too many_permutations.

Without defining the variable X_(for_X_amount of weeks) that you_should take
for an MVP, the general_advice for MVP_is to build as little as possible,
launch_fast,_fail fast, and reiterate.

There are industries_where_the barriers of building an MVP_are_much_higher.
For example, in ML you_need to train your algo huge_amounts of data. In the
automotive industry