Communication and Stakeholders Flashcards
What should the project manager do after a meeting?
Send a recap email or notes, make sure that action items are followed up on.
What is always a good idea when pitching a feature for a software engineer?
Explain also how it might look down the road so technical dept can be avoided.
Is it a good idea to bring in engineers to provide ideas or opinions on the product side (not only technical)?
Yes. Of course.
Designers are very creative. What is therefore important?
Ensure constraints and limitations are clearly commincatied. For example, we cannot get information X easily from the database.
When you share a decision with a team, what must you remember.
Explain the rationale. Maybe the data.
What, why, how… as a product manager, what is your responsiblity?
What and why. Not how.
When talking to designer, what should you focus on? Problems or solutions?
Problems to be solved.
When sending an email to an executive, why is it important to add all the relevant information?
Trick question. It is not. Keep things very short. Focus on business effect (metrics, revenue). If they want more information, they know who to ask - you.
It is important that other teams know that you understand the A, B, C well because X.
It is important that other teams know that you understand the user base, technology and business well because it will make them confident in the decisions you make.
What is smart to keep in mind when frequently communicating updates?
Make it clear whether or not you want them to reply or if you just wanted to send an update.
When updating someone on the completion of feature, what must you remember to include?
Why is the feature as it is? What alternatives did you consider - why where those not ideal?
