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

Isn't what you're describing autonomy of team members?

Some team members go on their own path-finding journey and can make the decisions on their own on where to take it.

I believe a team effort also involves a transfer of knowledge. I know some companies are disfunctional regarding this. Some companies aren't and while you are working on something, you can invite others to comment and give suggestions while you present your current progress.

I would present during team meetings what I was doing and why and sometimes got great feedback which helped me. If what I was working on affected many teams or wasn't interesting to my own team, I would send an optional meeting invite. Two kinds of people accepted it. The ones who were interested and the ones who had experience in that particular sub-topic.

Generally, the ones with experience asked questions during the meeting and the ones without sometimes asked questions afterwards. Both were helpful. Those with experience sometimes made me pivot. And those without, I flagged as someone I would like to include now or at some point in the project.

I don't think what I said was contradicting what you said.



Consider applying for YC's Summer 2026 batch! Applications are open till May 4

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

Search: