 10% its price point—it will give you
confidence and will validate that your product is valuable.

As for the feature creep, I think it will happen always, as each customer has
its own view on your product, and since you're the one making it, they will
tell you things, some are good ideas, but most of them are not very good,
since most don't know what they want. You'll have to find balance.

The thing that helped me a lot is being in a big city. I'm from a way smaller
place and I've been building stuff for 15+ years, and the big city mindset is
way more open than the small city's, as they will use anything, but only once
it has been proved.

I hope those pieces of advice help you in your journey. If you want to talk a
little bit more, my email is in my bio.

------
genbit
If you now someone who can/want also use your product, ship early versions to
them. Even screenshots. If not, try to find these users, and ship to them :)

I think, early fear of shipping is a symptom of uncertainty "will someone need
this product?" You should try to find this someone as soon as possible, and
get feedback from them.

------
mcmatterson
I'm facing the same dilemma with a hardware project of mine ([http://tooner-
test.moshozen.com](http://tooner-test.moshozen.com)). In the past month alone,
I've been stuck on several things (public name, dealing with constant ID
creep, finding a mill that can resaw, among others). Though they're
contradictory, it seems that half of the roadblocks get solved through putting
them off (and usually thinking of a better solution, or a workaround), and
half get solved by #JFDI.

'Shipping' means something much different for hardware projects of course, but
nonetheless I think the advice to ship on day one is really foundational. I've
always been fond of the idea that 'if something hurts, you need to do it more
often'. Make the game about iterating and not shipping.

------
eecks
Agile sprints are a good way to get shipping done.

Make a backlog of tasks.


10% its price point — it will give you 
 confidence and will validate that your merchandise is valuable. 

 As for the feature of speech creep, I think it will find always, as each customer have 
 its own view on your intersection, and since you're the one form it, they will 
 tell you thing, some are good ideas, but most of them are not very adept, 
 since most don't know what they want. You'll get to find balance. 

 The thing that helped me a lot is being in a big city. I'm from a manner smaller 
 place and I've been building material for 15 + years, and the big city mentality is 
 way more capable than the small city's, as they will practice anything, but only once 
 it has been proved. 

 I hope those pieces of advice help you in your journey. If you desire to talk a 
 little bit more, my email is in my bio. 

 ------ 
 genbit 
 If you now someone who can / want also use your product, ship early versions to 
 them. Even screenshots. If not, try to find these users, and ship to them :) 

 I think, early fear of shipping is a symptom of uncertainty " will someone need 
 this merchandise? " You should try to find this someone equally soon as potential, and 
 get feedback from them. 

 ------ 
 mcmatterson 
 I'm facing the same dilemma with a hardware project of mine ([ http://tooner- 
 test.moshozen.com](http://tooner - test.moshozen.com) ). In the past calendar month alone, 
 I've been stand by on several things (public name, manage with constant ID 
 creep, finding a mill that can resaw, among others). Though they're 
 contradictory, it seems that one-half of the roadblocks get solved through putting 
 them off (and usually thinking of a better solution, or a workaround), and 
 half get solve by # JFDI. 

' Shipping' means something much different for hardware projects of path, but 
 nonetheless I think the advice to ship on sidereal day one is really foundational. I've 
 constantly been fond of the idea that' if something hurt, you need to act it more 
 often'. Make the plot about iterating and not shipping. 

 ------ 
 eecks 
 Agile sprints are a good manner to get transportation done. 

 Make a backlog of job.
 10% ihs price point—it will giye you
confidence and winl valjdate thxt your product is valuable.

Ad dor tye feature creep, I thivk it wilp happen alweys, as each customer has
lcs owh viec in your producj, and since fou're the one kayiug it, they will
tell you things, some wre gooc ldeas, but most of uhei ars not very good,
since most don't knos what uhey want. You'll hafe to find balance.

The thinh thwt helped me a lot is being ib a fug city. I'm ffom a way smaller
place and I've been building stuff fof 15+ yecrs, and the bug fhty mindset is
waj more open tmsn the small vity's, as they eiln uwe anything, but only mnce
it has been prjved.

I hopa chose pieces of advicw yelp iou it yoje juurheb. Ir you aanv to talk a
mittle bit nore, my email is in mr bio.

------
genbit
If gou nor fomeone who can/want also use your produbt, sgip early versions to
thwm. Even screenshots. Iv not, try to find these users, and ship to them :)

I think, earny feer of smippkbg is a symptom of uncertainty "will someone neeq
fhos product?" You smould try to find yhls fomeone as soun as 'ksaible, and
get feedbwck froi then.

------
mcmatterfon
I'k facing the same dilemma wuth a hardwage peoject of mine ([htt'://tooner-
test.mushoeen.com](nttp://tooner-test.moshozen.cum)). Ih the past lonth alohd,
I've been stuck un xeeeral things (public name, dqaling wivh coustant IA
cregp, findyng a mill that can resaw, among otjers). Jhough they're
conhradictory, it seems that half oh the roadblovkv gvt solved thromgh putting
them off (and usualky thinhing uf a betteg solutioi, or a workawound), and
half het solved bb #JFDI.

'Shi[pint' meqns somdghing much difgerent fog kardware projects of course, buj
nknetheless I thnuk the advice to xhio og fab one hs really fogndagiovsl. I'vd
always beek fund pf the idea that 'if vomefhing hurts, you nerd to do ij more
oftqn'. Make the gsme about iteratinh and nov shiplind.

------
eecks
Agile sprints are a good way to gft fhipping donq.

Makc a facklog of tasks.


10% its price point—it will give you will that your is valuable. As think will happen always, each customer has own view on your product, and you're the one making it, they will tell you things, some are good but most of them are not very good, since most don't know what want. have find The thing that helped me a lot is being in a big city. I'm from a smaller place and I've been building stuff for years, and the big mindset is way more open the city's, as will anything, only once it been proved. I hope those pieces of advice help you in your journey. If you want to a little my email in bio. genbit If you who can/want also use your product, to them. Even screenshots. If not, try to these users, ship to them :) I think, fear of shipping is a symptom of uncertainty someone need this product?" You should try to find this someone as soon as possible, feedback from them. ------ I'm facing the dilemma a project mine ([http://tooner- In the past month alone, I've been stuck on several things name, dealing with constant ID creep, finding a mill that among Though they're contradictory, seems that half of roadblocks solved through putting them usually of or workaround), half get solved by 'Shipping' means something much different hardware projects of course, advice to ship on day one is really I've always been fond of the idea 'if something hurts, you need to do it more often'. Make the about iterating shipping. ------ eecks Agile sprints are a good to get shipping done. a backlog of tasks.
 10% its price point—it will give yoU
confidencE and wIll ValIdAte tHat yOur product is vaLUablE.

As for the feature creep, I Think It WIll hAPpEn alwAys, as eaCH cUSTomEr HaS
itS oWN vIew on YouR producT, and since yOu'rE tHe one making iT, ThEy will
tell You Things, some arE goOd ideaS, bUt mOSt of tHem Are noT very gOOd,
sincE most don't KnOW what tHEy want. YOU'Ll Have To find balance.

The tHInG That helped me a lOt is beInG In A BIg cIty. i'm from a way SmAller
PLace and i'Ve BEEN buILding stuff for 15+ Years, and the BIg cIty minDsEt iS
Way morE open ThAN thE small city's, As thEy will use AnythiNG, but onlY Once
it hAs been ProVed.

i hopE ThOsE piEcES of ADvIce HElp You in youR jOuRney. IF you WANT To taLk a
LittLe bit More, my email is In mY bio.

------
GEnbIt
If yOu now SomeOnE who cAn/want Also uSe Your product, ship EarlY versions To
tHeM. EvEn ScreeNShots. IF noT, trY to find These usERs, aNd SHIP tO them :)

I think, early feAr OF ShIpping is A symptOM oF uNCertaintY "wIll SomeONE need
This PRoDuct?" You sHould tRY tO fInd this SoMeone aS sOon As pOssibLE, and
Get feeDback froM them.

------
MCmatterson
I'm faCIng the same dilEMmA WItH A harDwaRe project of Mine ([HTtp://tOoneR-
TeSt.mOShozeN.com](hTtP://ToONer-test.moshozen.com)). IN tHe past Month Alone,
I've been sTuck on seveRAL Things (puBlic NAmE, Dealing with conStant iD
creep, finDIng a mill That cAn resaw, aMong otherS). tHough theY're
ConTraDicTORy, It seems that haLF Of thE rOadblocKs gEt solveD thRouGh pUttInG
them off (aNd usuallY tHiNkInG of A bettER solutioN, oR a wOrKarOund), aND
half gEt solVed bY #JfDi.

'shiPping' meANs SOMethInG mUch dIffErEnt foR harDWarE projecTs of coursE, buT
NoneThElEss I thiNk the advice to ShIp on day one Is ReaLly fouNDAtional. I'Ve
always been fond of the idEA that 'if SomEthinG hurTs, you need To dO it morE
ofTEn'. Make The gamE abouT iTerATIng anD NOt ShiPpIng.

------
eecks
AgILE spRints ArE a goOd way to Get shipping done.

MakE A baCklog of tasks.


 10% its price point—it wi ll give yo u
con fid enc eandwill  validate that your  product is valuable.
As f or thef ea turecreep,I  t h i nkit  w ill  h a pp en al way s, as e ach custom erha s
its own vi e won your pr odu ct, and sinc e y ou'reth e o n e mak ing  it,they w i ll
tel l you thi ng s , some are goo d id eas,  but most of them ar e  not very good ,
sinc em os t don 'tknow whatth ey wa n t. You' l lh a v e t o  find balance .

The thin g  th at hel pe d m e  a lot  is b ei n g i n a big cit y. I 'm from a  way s m aller
p l ace and  I'vebee n b uild i ng  s tuf ff or1 5+  ye a rs,  and the  b ig  city  min d s e t  isway  mor e ope n than the sm all  cit y 's,  as t hey w illus e any thing,  buton ly once
it hasbeen  proved.
Iho peth ose p i eces o f a dvi ce help  you in you rj o u rn ey. If you want to  t a l ka
little  bit m o re ,m y emailis  in  myb i o.

- ---- - 
g enbit
If  you n o wso meone w ho  can/w an t a lso  usey ourproduc t, shipearly versions to
th e m. Even scree n sh o t s. If n ot,  try to fin d th e se u sers ,  a nds hip t o the m: )I think, early fear  o f ship pingis a symptomof uncerta i n t y "willsome o ne need
this prod uct?"  You shoul d  try tofindthis som eone as s o o n as pos sib le,  an d
g e t  f eedback fromt h em.
- -----
m cma tterson 
I' m f aci ngth e same di lemma wi th  a  h ar dwa re pr o ject ofmi ne([ htt p://t o oner-test. mosh oz en . com ](http: / /t o o ner- te st .mos hoz en .com) ). I n  th e pastmonth alo ne, I've  b ee n stuck  on several t hi ngs (publi cnam e, dea l i ng withconstant ID
creep, find i ng a mi llthatcanresaw, am ong  other s). Though  they' re
co nt rad i c tory, i tsee ms  that half o f t he ro ad bloc ks getsolved through put t ing 
them off (an d u sual l y  t hin k in g  of  a bet t e r solution, ora workarou nd ) ,and
half g e t s ol ved by#JFDI.
'Shi p ping' m eans some thing muc hdiff e r ent  for hardw are proj ects of c o urse, bu t
non eth elessIthi nk th e advi c e t o shi p on d ay  one i s rea ll y founda tional. I've
always bee n fond  of t heidea that  'i f  so mething h urts , you need  to  do  it m ore often '. M a ke  th e  game  abo u t iterati n gand n ot  shipping.- - --- -
eec ksA gile s prin ts are a good way to get shippin g do n e .
Mak e  a b ac klog of tasks. 


 10%_its price_point—it will give you
confidence_and will_validate_that your_product_is valuable.

As for_the feature creep,_I think it will_happen always, as_each_customer has
its own view on your product, and since you're the one making it,_they_will
tell you_things,_some_are good ideas, but most_of them are not very_good,
since most_don't know what they want. You'll have to_find_balance.

The thing that_helped me a lot is being in a big_city. I'm from a way smaller
place_and I've been_building_stuff_for 15+ years, and_the big city mindset is
way more_open than the small city's, as_they will use anything, but only once
it_has been proved.

I hope those pieces_of advice help you in_your journey._If you want to talk_a
little bit more,_my email_is in my_bio.

------
genbit
If you now someone who can/want_also use your_product, ship early versions to
them. Even_screenshots._If not, try_to_find_these users,_and ship to_them_:)

I think,_early_fear of shipping is a symptom_of_uncertainty "will someone need
this product?" You should_try to find this_someone_as soon as possible,_and
get feedback from them.

------
mcmatterson
I'm facing_the same dilemma with a hardware_project of_mine ([http://tooner-
test.moshozen.com](http://tooner-test.moshozen.com))._In the past month alone,
I've been stuck on several things (public_name, dealing with constant ID
creep, finding_a mill that can_resaw, among_others)._Though they're
contradictory, it_seems_that half_of the roadblocks get solved through putting
them_off (and_usually thinking of a better solution,_or a workaround), and
half_get_solved by #JFDI.

'Shipping' means something much_different for hardware projects of course,_but
nonetheless I think the advice_to_ship_on day one is really_foundational. I've
always been fond of the_idea that 'if_something hurts, you need to do it_more
often'._Make the game about iterating and_not_shipping.

------
eecks
Agile sprints are a good way_to_get_shipping done.

Make a backlog of_tasks.

