Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

This is good advice.

Another thing to consider is cost-to-benefit ratio.

If you don’t know cost, first look at:

Product costs: free < one-time cost < recurring cost or recurring “one-time” costs

Resource alignment costs: (Re-)hiring + severance + knowledge lost or transferred to competitors

Refitting and development costs: converting or re-writing code + (re-)training + architectural changes + design changes

Time + impact to other initiatives and maintenance

Don’t stop after costing!

Then listen to the perceived benefits or need again, being careful to communicate and discuss the perceived costs, so that those selling the idea within the company understand, because if they don’t, their good idea will be poor morale fodder later.

This is much quicker and easier than it seems. If you still haven’t convinced the elements within the company to back down on their idea, and you’ve done a good job listening and considering their points, then either those elements are onto something or they’re “on something” (drinking the kool-aid).

Make your decision.



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

Search: