Hello, Here's task 1: I have 1 year of experience and I am working to solidify my skills. I excel in terms of communication and working in remote settings, but I still need the background work and knowledge to then produce ideas that will bring value to the customer and influence others. One of my challenges is understanding how the product works “underneath the hood” as there are multiple systems in place when proposing new functionality. I still need to not jump straight to development and ask questions about the context of the project and understand how all the pieces will work in the backend. I am excited to pause more, ask questions about the context, really understand the user side, identify the problem we are trying to solve and work on it.

@Rasa Kulvietiene hey Rasa thank you for sharing. In terms of effective communication, to make messages shorter, one suggestion is to take your time to review the message before sending and edit fearlessly. To make it shorter, try to remove repetitions and use a format that allows you to condense info, like bullet points. Hope these suggestion can help you!

Startup I’ve worked in a startup for 3 years and the major skills of a PM is to act and adapt quickly. As you have less resources and thrive for velocity, you need to put hypothesis in the roadmap and then iterate from that. You will need some negotiating with other departments, but the product is leading with the expertise they have. You will need to be attentive that the plan may change and you will need to adapt the roadmap quickly, but don’t lose sight of the end goal. Be flexible on the process. When it comes to prioritise the roadmap, you are looking for quick wins and the 80/20 rule: look for the initiatives that will bring the most results. Presenting to a larger team can be done in a more workshop-like way and you can receive inputs from different teams and iterate. When a bug paralyses the whole company, come together to fix the bug and once it is fixed, make a retrospective on how to improve in the future. The thought process is more loose as you can look at the product and see a lot that can be improved, but keep your approach lean. Focus on achieving great results with less process and always get feedback to improve in the right direction. --------------------------------------------------------------------------- Big company In a bigger company, there is a lot more negotiating and politics, and it may not be a bad thing. Building a roadmap is a process that can be very well documented. It will require multiple sessions with different internal stakeholders to come up with a plan. You need to prepare this in advanced as it will need rounds of approval. When you are prioritising, you may need to win some and lose some, focus on the big bets projects and in the long-term strategy, and don’t discard initiatives promoted by key stakeholders. Bring everyone to the conversation and make the final decision. When it comes to pitch your idea, you need a solid project plan, where you may need to attach budgets. The good news is you have a lot of data to showcase why you want to pursue different projects.

@Sid Arora I work in credit and I create products for the organisation to accept more credit processes digitally. My current product is an interface to the customer to be able to manage their own processes of credit

@Sid Arora my product is focused on end user, other products of the companies are more to a business side

Some key learnings: - The PM job is hard to define and it depends on the business and the company you are working on - PMs should take time to develop their skills - The 3 main skills when starting the job is own the execution, improve your communication skills and start using data