Here's how you can effectively receive feedback as a system architect.

Regardless of role and title the first step to receiving feedback is having a desire to understand your interactions with others, the quality of the work you led/produced, and wanting to grow. I use "grow" instead of "improve" because the latter assumes you're starting from a place of not being good enough and needing to get better. One thing I always tell others whom I mentor is always to be open to feedback. You might not agree with it but you should listen with an open mind.

Always have the mindset to embrace feedback with a neutral and unbiased state of mind. This helps to eliminate all the emotional aspects of receiving feedback. Try all the feedbacks with either supporting data or POC's. If the results are positive then its a great experience, if not, still a great experience you learned "what not to do"

To receive feedback effectively as a system architect, cultivate openness. View feedback not as criticism but as a chance to improve. Approach it with curiosity and a readiness to learn, fostering an environment where colleagues freely share insights. This approach allows you to gain valuable perspectives to enhance your system designs.

Always seek clarity , The person who gave you feedback might not very well understand your requirement or intention. So its better you take them through time travel of your journey till here and your future thought process. But during all these have your end goal crisp and clear. Make sure all your questions are based on your requirement rather than generic.

When receiving feedback, aim to comprehend the points thoroughly. Ask questions to clarify ambiguities and grasp the essence of suggestions. For feedback on specific components or processes in your architecture, seek examples or a deeper explanation to understand practical implications and application to your work effectively.

After understanding feedback, analyze its impact on the system architecture. Evaluate potential benefits and drawbacks of implementing changes. Will they enhance scalability, efficiency, or maintainability? Consider these factors carefully as they directly influence system performance and client satisfaction.

1) Make sure you know what to measure after implementation and do you have the right tools to measure. 2) Make sure you take baseline numbers before implementing it so that you can compare it post implementation. 3) If the function is very critical make sure you wrap it around a feature flag so that you can turn on / off OR Leverage A/B testing to see which variant is yielding a better result. If you cant measure it, you are shooting in the dark.

Always spend some time with people who has gone through a similar journey. Practical experience always triumphs theoretical knowledge. I always love to listen where they failed and how did they overcome it. These stories always inspire me and I learn a lot on what you should not do . Remember, you alone cant do all the mistakes ! you have to learn some from others !