Hacker Newsnew | past | comments | ask | show | jobs | submit | rdpowers's commentslogin

I do hardware engineering work for hire and one of the things that always works is having some documentation ready at the first formal meeting.

Specifically, I have a skeleton requirements document that I put together from our previous correspondence (there's always a phone call, few emails, etc.) trying to flesh out their project needs. It doesn't matter if this is incomplete, inaccurate, or any other in-word. It shows that I'm a professional who has tried to understand the problem, the business case, possible solutions, will approach it methodically and like a real engineer, and that I know what I'm doing.

Those 10-15, printed, very real, pages, mostly just ?-marks, have written me more contracts than I can count. It takes about 1-2 hours of work to write things up, but I've never - not once -, had a potential client fail to notice and be impressed when I show up and have a presentable document already underway.


This is generally the way to win contracts, grants and impress people. Going over their requirements carefully, whether written or verbal, and gearing your proposal directly to what they say always impresses. That's why changing project managers at the beginning of or before a contract starts is a big problem.


So important to have requirements set up for the less "agile" world of hardware, but really like the idea of having a framework set to go. Have worked with a few contract agencies at past co's and that would have impressed the hell out of me.

This is always as a solo? Or as a small engineering firm?


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: