How I work
Ever wondered what a day in the life of a product manager looks like? It's not all about flashy presentations and big decisions. In this blog post, we'll take a simple and straightforward peek into my typical day as a product manager, I'm breaking it down my tasks into easily understandable chunks.
PRODUCT MANAGEMENT
Tasnim
1/7/20232 min read


Introduction
Ever wondered what a day in the life of a product manager looks like? It's not all about flashy presentations and big decisions. In this blog post, we'll take a simple and straightforward peek into my typical day as a product manager, I'm breaking it down my tasks into easily understandable chunks.
Morning: Planning and Prioritizing
Check Emails and Team messages: The day often starts with checking emails and team messages. Usually, I receive messages from team members, stakeholders, and customers, all needing attention or some action.
Review Metrics: I look at important numbers, like how many people are using the product and what features are popular. This helps me to understand what's working and what needs improvement.
Daily Standup: I often have a quick morning meeting with the team to discuss progress and any roadblocks. It's like a huddle before the big game. Had a quick chat with scrum master and architect.
CI/CD pipeline: I look at the CI/CD pipeline to see things are in place, no failing integration test.
Midday: Meetings and Collaboration
User Feedback: I listen to feedback from users. This could be from customer support, surveys, or social media. I take notes to understand what people like and dislike.
Meetings: I spend a lot of time in meetings. I meet with designers, engineers, marketers, and others to make sure everyone is on the same page.
Decision Making: Sometimes, I have to make tough decisions about what features to work on next. This involves weighing the needs of customers and the goals of the company.
Stakeholder Management: Talk to stakeholders, to understand what is coming next. I often give brief overview what is happening and show them different metrics.
Afternoon: Execution and Adaptation
Write User Stories: I create user stories, which are like mini-plans for building a big features. These stories explain what the feature should do from a user's perspective.
Review Designs: I look at designs for new features. I tried to make sure the designs match the user stories and the overall vision.
Problem Solving: When issues or unexpected challenges arise, I work with the team to find solutions. It's like being a curious listener for the product problems.
Evening: Wrapping Up and Future Planning
Emails and Updates: Before calling it a day, I respond to any remaining emails and provide updates to the team.
Future Planning: I spend time thinking about the long-term roadmap for the product. What should be built next increment, next month or next year?
Reflection: I reflect on what went well and what could have been done better during the day. This helps me to be more productive.
Conclusion
My typical day is a mix of planning, meetings, collaboration, and problem-solving. It's about understanding what users want, working with the team to make it happen, and always thinking about the future. While it may not always be glamorous, but I enjoy the work.