Discussion about this post

User's avatar
Akos Komuves's avatar

> Don't be too attached to your proposal. If someone makes a valid suggestion, then take it. Your goal is to find a good solution, not to prove that your solution is good.

Step 0. In most of the software engineering in our world, whether it's feedback, PR reviews, proposals, or technical docs, is leaving the ego at the door. These are our systems, and we're responsible for building them to the best of our knowledge.

Also, good tips on making proposals that people will actually read by using clear titles and sharing them early.

Great stuff, Raviraj!

Expand full comment
Fran Soto's avatar

I couldn't help but relate to a situation I'm living in right now.

We are making changes in our team dynamics, from agile ceremonies to technical procedures of operational excellence.

Trying to put it all at once because "it's a best practice" would only create resistance.

I was super delighted with my manager making every week one little change. All of them fell into a larger vision, but in an approachable way that left nobody behind.

These tips apply to any change we try to introduce in any group of people. Thanks for sharing them, Raviraj!

Expand full comment
6 more comments...

No posts