Hacker News new | past | comments | ask | show | jobs | submit login

The trick is to make the "right" decision yourself while helping people feel like they were heard and had a chance to give their input.

From my experience, people don't actually want to control the output of everything, they just want the opportunity to be heard. What you do with it from there doesn't matter as much, so long as the desired outcome is "correct". If the desired outcome is not correct however... then you have to justify all of the input that you didn't act on.




The tricky part for me is that sometimes I did actually need that input from others on the team. Sometimes it's all just bikeshedding and a waste of time, but sometimes it does help me from going down a rabbit hole that might have wasted weeks of development.

But regardless, I find that whole process exhausting and disempowering, even if there is sometimes a benefit from it.




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

Search: