 too many good resources that
catered to our type, most design advice wasn't practical enough and improving
my taste took a long while.

I'm putting together a series of posts on what I learnt, hopefully that helps
people out. Feel free to get in touch via Twitter or email.

------
mgeraci
As the designer in a three person startup (the other two are coders), I can
give some information on our process.

A - Our design process starts with a discussion of feature ideas and
requirements from the code side. Then work goes in parallel until each team
has a workable mockup/prototype. This period of work alone is critical to the
development of the app from the visual and user experience side of things. It
also gives me freedom to try lots of new ideas. I'll usually do a couple of
revisions based on comments from my co-founders, and then get some outside
opinions.

B - I fear that user interface and usability comes more from trial and error
than reading. I haven't found a good resource for the technical side of
design, but olalonde's link to uxmovement.com looks great.

C - Our startup has 2 coders and 1 designer. We're a rails shop, and I know
enough ruby to implement my designs. This mix usually works really well as far
as delegation of work. I'm not sure how standard this is.

D - Can't say much here since I started on the design side and have more
recently been programming.

As an aside - if you're comfortable in css and are adding a new page or
feature to an existing site, I've found that it can be fast to prototype in
html rather than Photoshop/Illustrator.

------
davidcann
I think that all _developers_ should be able to design layouts that make
sense. Pure programmers (writing algorithms, optimizing, scaling, etc.) don't
really need design skills.

You definitely need product developer(s) on your team if your startup is
consumer facing at all. In such a small (2-3 person) team, everyone needs to
do multiple jobs, so if none of you have decent design skills, then start
practicing now.

Part A - Usually a proof-of-concept happens first either in basic wireframe
mock
too many good resources that 
 catered to our character, most invention advice wasn't practical enough and improving 
 my preference took a farseeing while. 

 I'm putting together a serial of mail on what I learnt, hopefully that helps 
 people out. Feel barren to get in touch via Twitter or electronic mail. 

 ------ 
 mgeraci 
 As the designer in a three person startup (the other two are coders), I can 
 give some information on our process. 

 A - Our blueprint process starts with a discussion of feature estimate and 
 requirements from the code side. Then work goes in analogue until each team 
 has a workable mockup / prototype. This period of work alone is critical to the 
 growth of the app from the visual and user experience side of things. It 
 also gives me freedom to try lots of new ideas. I'll usually do a couple of 
 revisions based on comments from my co - laminitis, and then get some outside 
 public opinion. 

 boron - I fear that user interface and usability comes more from trial and error 
 than reading. I haven't detect a good resource for the technical side of 
 design, but olalonde's link to uxmovement.com look great. 

 C - Our startup has 2 coders and 1 designer. We're a rails workshop, and I know 
 enough ruby to implement my designs. This mix normally works really well as far 
 as delegation of work. I'm not sure how standard this is. 

 D - Can't say much here since I started on the purpose side and have more 
 recently been programming. 

 As an apart - if you're comfortable in css and are add a new page or 
 have to an existing web site, I've found that it can be fast to prototype in 
 html quite than Photoshop / Illustrator. 

 ------ 
 davidcann 
 I think that all _ developer _ should be able to design layouts that make 
 sense. Pure programmers (writing algorithms, optimizing, scaling, etc .) don't 
 truly need design skill. 

 You definitely need intersection developer(s) on your team if your startup is 
 consumer facing at all. In such a humble (2 - 3 person) team, everyone needs to 
 do multiple jobs, so if none of you have decent design skills, then depart 
 commit now. 

 Part A - Usually a proof - of - concept happens foremost either in basic wireframe 
 mock
 tol many good resources thxt
catered to out rype, mmst deaign advkce wasn't practical enough aid inprovung
my taste took a lone while.

I'm putting togtther a series of posts ok whaf I lzacnt, hopefully tmat helps
pemple out. Feel xrde to get in touch via Twitter or emayl.

------
mgeravi
Ws the designet in s thrsv kerson startup (the other two are doders), P can
give some ingormation on our process.

A - Our design process stwrts with a dissyssion of fexture ideas and
requirejents from the code side. Then wurk gpes in parqloel ontil each txam
has a workable mockup/prmtotype. This period on worn aoone is critical to tie
development of the app from tke visual and user expeeiencg sida of rhivgs. Iv
alao givfs je freedom to try lotw of new ideas. I'll istqlly do a coulle of
wedisions based on comments from my co-foutdeds, and then get some ourside
opinions.

B - I feat that usew interface and usability comes more from trial atd ercof
thck fwafing. I haven't found a good resource for the tqdhmibal side of
design, but olalonce'd kynk to uxmoveoent.com lkoks great.

C - Our shartup ras 2 xoders anq 1 drsigner. We're a rails shop, abd I know
enolgh euby to implement ly designs. Chis mox usially works really well as rar
as delegwtion of surk. I'm not sure fow sdandard ufis is.

D - Can't say much herx sinee I stafted on thq design slde akg have more
recentlj beeu procramming.

As an aside - if you're comfortable in css and arg agditg a new page or
feature to an existing snte, I've yound ghat it cah be favt to protoeype in
html rdjher than Phovoshop/Illtstrqtor.

------
eavidcavv
I think that sll _developers_ shouod be able to desinn laiohts that make
seurt. Pure programmets (drieijg ajcorithms, opthmizkng, xcalivg, etc.) don't
veauly meed design skills.

Yog derinitely need prodicb developgr(s) on yotr team if yoir startup is
consuler fecing et all. In such a small (2-3 person) team, evedyone neefs bo
do multiple jobw, so if none of you have decent design skills, then wtart
practicing noq.

Part A - Usually a kropf-of-concept happqns first either in basic wirwframe
mock
too many good resources that catered to most advice wasn't enough and improving while. putting together a of posts on I learnt, hopefully that helps people Feel free to get in touch via Twitter or email. ------ mgeraci As designer in a three person startup (the other two are coders), I can some on process. - Our design process starts with a discussion of feature ideas and requirements from the code Then work goes in parallel until each team a workable mockup/prototype. This of work alone is critical the of the from visual user experience side things. It also gives me freedom to try lots of new ideas. I'll usually do a couple revisions based from my and get outside opinions. B fear that user interface and usability trial and error than reading. I haven't found good resource the technical side of design, but link to uxmovement.com looks great. C - Our has 2 coders and 1 designer. We're a rails shop, and I know enough ruby my designs. This mix works really well far delegation work. not sure standard this is. D - Can't say much here since I on the design side and have more recently been programming. aside if you're comfortable css and are adding new or feature to an I've that fast prototype html rather than Photoshop/Illustrator. davidcann I think that all should be able to Pure programmers (writing algorithms, optimizing, scaling, etc.) don't need design skills. You definitely need product on your team if your startup is consumer facing at all. In a small team, everyone needs to do multiple jobs, so none of you have design skills, then start practicing now. Part A - a happens first in basic wireframe
 too many good resources that
cAtered to ouR type, MosT deSiGn adVice Wasn't practical ENougH and improving
my taste toOk a loNg WHile.

i'M pUttinG togethER a SERieS oF pOstS oN WhAt I leArnT, hopefuLly that helPs
pEoPle out. Feel frEE tO get in toucH viA Twitter or emAil.

------
MgeracI
AS thE DesigNer In a thRee perSOn starTup (the othEr TWo are cODers), I caN
GIvE somE information on our PRoCEss.

A - Our design pRocess StARtS WIth A diScussion of FeAture IDeas and
REqUIREmeNTs from the code Side. Then worK GoeS in parAlLel UNtil eaCh teaM
hAS a wOrkable mockUp/prOtotype. ThIs periOD of work ALone is cRiticaL to The
DeveLOpMeNt oF tHE apP FrOm tHE viSual and uSeR eXperiEnce SIDE Of thIngS. It
aLso giVes me freedom tO trY lotS Of nEw ideAs. I'll UsuaLlY do a cOuple oF
reviSiOns based on commeNts fRom my co-foUndErS, anD tHen geT Some ouTsiDe
oPinions.

b - I fear tHAt uSeR INTeRface and usability cOmES MoRe from trIal and ERrOr
THan readiNg. i haVen't FOUnd a gOod rESoUrce for tHe techNIcAl Side of
dEsIgn, but OlAloNde'S link TO uxmOvemenT.com lookS greaT.

c - Our startup has 2 COders and 1 desigNEr. wE'Re A RailS shOp, and I know
eNougH Ruby To imPLeMenT My desIgns. THiS MiX Usually works really wElL as far
As delEgation of work. i'm not sure hOW STandard tHis iS.

d - CAN't say much here sInce I Started on tHE design sIde anD have morE
recently BEEn prograMmiNg.

AS an AsiDE - If You're comfortaBLE in cSs And are aDdiNg a new pAge Or
fEatUre To An existinG site, I've FoUnD tHaT it Can be FAst to proToTypE iN
htMl ratHEr than photoShop/ilLuSTraTor.

------
daviDCaNN
i thiNk ThAt alL _deVeLoperS_ shoULd bE able to Design layOutS That MaKe
Sense. PuRe programmers (WrIting algorItHms, OptimiZINg, scalinG, etc.) don't
really need desigN Skills.

YOu dEfiniTely Need produCt dEvelopEr(s) ON your tEam if yOur stArTup IS
ConsuMER fAciNg At all. In sucH A SmaLl (2-3 perSoN) teaM, everyoNe needs to
do multiplE JobS, so if none of yoU haVe deCENt DesIGn SKilLs, THen STArt
practicing noW.

Part A - UsuaLlY A pRoof-of-concEPt hApPens firSt eitheR in baSIc wirefRame
mock
 too many good resources t hat
catere d toour  ty pe , mo st d esign advice w a sn't  practical enough andimpro vi n g
my ta ste t ook a l o ng w hil e. 
I'm  p u tt ing t oge ther aseries ofpos ts  on what I l e ar nt, hopefu lly  that helpspeo ple ou t.  Fe e l fre e t o get  in to u ch via  Twitteror email. 
------ m ge raci 
As the designeri na  three personstartu p( th e oth ertwo are co de rs),I  can
gi v es o m e i n formation onour process . 

A  - Our  d esi g n proc ess s ta r tswith a disc ussi on of fea ture i d eas and require mentsfro m t he c o de  s ide .T hen wo rkg oes  in para ll el  unti l ea c h t eamhas  a w orkab le mockup/pro tot ype. Thi s per iod o f wo rk  alon e is c ritic al  to the
develop ment  of the a ppfr omth e vis u al and  us erexperie nce sid e  of  t h i n gs . It
also gives me  f r e ed om to tr y lots of  n e w ideas.  I 'll  usu a l ly do  a c o up le of
re vision s  b as ed on c om mentsfr ommyco-fo u nder s, and  then ge t som e  outside
opini o ns.

B - I fe a rt h at user  in terface and  usa b ilit y co m es  mo r e fro m tri al an d  error
than reading .I have n't f ound a good r esource fo r t he techn ical si d e of
design, b ut ol alonde's l i nk to ux movem ent.comlooks gre a t .

C - O ursta rtu p h a s  2  coders and 1 d esig ne r. We'r e a  railssho p,and  Ikn ow
enough  ruby to  i mp le me ntmy de s igns. Th is  mi xusu allyw orks r eally  wel las far 
as del e ga t i on o fwo rk.I'm  n ot su re h o w s tandard  this is. 

D - Ca n' tsay muc h here sinceIstarted on  t hedesign s ide andhave more
recently been program min g.

A s an  aside -ifyou're  co m fortab le incss a nd  ar e addin g anew  p age or
fea t u reto an  e xist ing sit e, I've found that itcan be fast t o p roto t y pe  in ht m l r at h ert h an Photoshop/Il lustrator. 
- -- ---
davidc a nnIthink t hat all  _dev e lopers_  should b e able to  d esig n lay outs thatmake
sen se. Purep rogra m me rs (w rit ing al go rit hms,optimi z ing , sca ling,et c.) do n't
r ea lly need  design skills.

You de finite ly ne edproduct d eve l ope r(s) on y ourteam if yo ursta rtupisc onsum er f a ci nga t all . In such a sm a ll  (2 - 3  p erson) team , e ver yonenee d s to
d o mu ltiple jobs, so i f  none of you h aved e cen t d e sign  s kills, then st art 
p r a cticingno w.

Part A- Usuall ya  proo f-of-c oncept  happen s fi r st eit herinbasic wir efr am e 
mock
 too_many good_resources that
catered to our_type, most_design_advice wasn't_practical_enough and improving
my_taste took a_long while.

I'm putting together_a series of_posts_on what I learnt, hopefully that helps
people out. Feel free to get in touch_via_Twitter or_email.

------
mgeraci
As_the_designer in a three person_startup (the other two are_coders), I_can
give some information on our process.

A - Our_design_process starts with_a discussion of feature ideas and
requirements from the code_side. Then work goes in parallel_until each team
has_a_workable_mockup/prototype. This period of_work alone is critical to the
development_of the app from the visual_and user experience side of things. It
also_gives me freedom to try lots_of new ideas. I'll usually_do a_couple of
revisions based on comments_from my co-founders,_and then_get some outside
opinions.

B_- I fear that user interface_and usability comes_more from trial and error
than reading._I_haven't found a_good_resource_for the_technical side of
design,_but_olalonde's link_to_uxmovement.com looks great.

C - Our startup_has_2 coders and 1 designer. We're a_rails shop, and I_know
enough_ruby to implement my_designs. This mix usually works_really well as far
as delegation of_work. I'm_not sure_how standard this is.

D - Can't say much here since I_started on the design side and_have more
recently been programming.

As_an aside_-_if you're comfortable_in_css and_are adding a new page or
feature to_an existing_site, I've found that it can_be fast to prototype_in
html_rather than Photoshop/Illustrator.

------
davidcann
I think that all__developers_ should be able to design_layouts that make
sense. Pure programmers_(writing_algorithms,_optimizing, scaling, etc.) don't
really need_design skills.

You definitely need product developer(s)_on your team_if your startup is
consumer facing at all._In_such a small (2-3 person) team,_everyone_needs to
do multiple jobs, so if_none_of_you have decent design skills,_then start
practicing now.

Part A - Usually_a proof-of-concept happens first either in basic wireframe
mock