Hey Prasad, thanks again for the good session. As mentioned I had a few key take aways: - more often than not, conflicts arise due to misalignment on the goals - situations should be approached with sympathy for the other party - it is good to find a way to look onto a problem from a different angle Thank you! Georgi

Yes, the session was helpful, Prasad told me about his experience of building product organizations and this was exactly what I was looking for.

Speaking with Prasad was really insightful. He has a way of communicating his thoughts at a level at which the listener can understand, which I feel is great! His feedback and response in general to my questions was decomposed into bite-sized actionable pieces, which really helped me think beyond the point at which I was stuck at.

Hey Prasad, thanks again for the nice session. The session was helpful in the way that you are able to structure the discussion and point to a problem. I appreciated this a lot as often, we ourselves are unable to really figure out the issue itself, before taking any steps to improving the situation. The framework you shared is a very good start as it really gives a plan to work with. On a more overall perspective, I feel you take the time to listen to the issue and sympathise. I like your structure and clear thinking and find it very helpful. Thanks!

We had a short session and not a lot of time to explain the context and its additional challenges but I felt we managed to jump right into the problem and make the most out of the time available. I did walk out with raised awareness about what are the pitfalls of the organizational strategy I was planning to propose and this pushed me to rethink it and improve it (hopefully ). So yes, the session was helpful for me. A big thank you!

The session was helpful, helped me get a better feel for what to focus on, as well as some creative ideas that came up during brainstorming. Prasad was very friendly and communicative, understood the problem space very quickly and gave good input. The format of 30-minute session might be a bit too short though, as I feel like we had to rush through a lot.

Yes, The session was absolutely helpful for me to empower myself transitioning to Product management. We discussed a lot about product management and I took a lot of information to build a career around products.

Really appreciated the frank conversation and the ability to bounce ideas off another person.

- 10 principle of software engineering - still-will matrix - How to structure my thoughts on my message to leadership about building a culture that is outcome vs output focussed.

1. Defining the top priorities for each week - and limiting this to not more than 3 items - forces one to prioritize and helps to remain focused on the right topics (additionally it can help to align team members). 2. Improving tech skills should be an ongoing project and be guided by personal interest and currently relevant topics at work. A good way for continuous learning is to schedule weeky/bi-weekly 15-min sessions with a developer and each time bring a new question. 3. Taking a deep interest in bugs and talking to developers who solve them is another good way to improve tech skills. Ask questions up to the point that you don't understand it anymore. Maybe google this part to understand. Don't get too caught up in details and don't spend too much time on a single bug, but rather do it continuously, a bit.

1. Adapt and improve on journey from PM to PO 2. Understand and learn cultural differences 3. Overcome remote working challenges. Got some really great tips and tricks

1. Having an experienced person is incredibly valuable as a different perspective on things 2. Try approaching difficult conversations with colleagues/leads with understanding first the background and proceed with empathy and collaboration mindset in proposing your ideas. 3. Always think about "slicing the beast" before jumping into work mode.

Building team culture, building autonomous teams

Prasad did an excellent job sharing his insights. He gave me valuable feedback on changes needed on my Linkedin profile/Resume, he also guided me on how to create more impactful portfolio pieces. We also talk about interviewing for different positions, where Prasad gave me very useful tips on how to better answer crucial questions.

Your resume should tell your story, overseas job opportunities, realism, patience and hardwork pays off.

1) Gain clarity on why PM, 2) Talk to more PMs within and outside the organization, 3) Put into perspective what you read in books and other articles

1. As a platform PM for logistics I have a great advantage because of the direct access to users. This sounds simple and obvious but it didnt strike me as something that I could use to my advantage 2. Dont dump information; make it visual and easy to consume but have a toolkit and a set of docs that as a PM you need not expose but pull them up when required

1. Giving best, to signal within organisation, which increases the chance of getting into product role. 2. How to bypass the political constraints of organization, while connecting to other teams. 3. The timeline for which I should keep on signalling things internally, before signalling to outside world.

- Driven metrics - Who else is your competitor? - B2C versus B2B products

1. How could we position our current product for Product Managers/Leaders? 2. What would be the ideal messaging? 3. What would be an ideal funnel to test?

- clarity on the metric why people pay for a service/product - drive engagement not just through optimizing how user behave, but also through learning theories - elevate understanding of all team members to get them aligned