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

> A discussion about building a specific feature can devolve into reevaluating the entire product roadmap if you let it.

Well, if the product roadmap doesn't hold up to scrutiny, it _should_ be reevaluated. Too often people commit to something, and then continue building it, despite the market realities having shifted underneath them. I see most teams not asking themselves often enough "should we still be doing what we're doing", than the opposite. The sunk cost fallacy is real.



Sometimes you can't get every staff engineer to agree to the plan, but you can't sit around forever unto someone caves.


No, but especially of staff+ engineers I'd expect that they know how to disagree and commit after a reasonable (not too long!) time.


It's called "thinking from the principle" for a reason.

You will have to re-invent the whole product from the start...




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

Search: