A Day in the Life of a Head of Product at Postal
A Head of Product's day at Postal involves deeply analyzing data to understand "how the product is functioning" and customer sentiment, then synthesizing this information with direct customer interaction – "being in a customer call" – to prioritize the product development team's backlog and shape future product development. This approach highlights the importance of data-driven decision-making coupled with a strong customer-centric focus.
Data Analysis, Project Management, Communication, Problem-Solving, Leadership
Advizer Information
Name
Job Title
Company
Undergrad
Grad Programs
Majors
Industries
Job Functions
Traits
Shadi Majzoub
Head of Product
Postal
Cal Poly
N/A
Business Management & Admin
Technology
Product / Service / Software Development and Management
First Generation College Student
Video Highlights
1. Shadi's day involves analyzing data dashboards to understand product performance and customer sentiment.
2. A key aspect of her role is direct customer interaction, including feedback gathering and participating in sales calls.
3. Shadi translates customer insights and data into product requirements, prioritizes development tasks, and communicates them effectively to the development team.
Transcript
What does a day in the life of a head of product look like?
It can look like a number of things. There are many areas where we can spend our time.
Often, it starts with looking at data. This means having a dashboard for data tracking to get a lay of the land on how the product is functioning, customer sentiment, and perhaps key areas to focus on.
I usually use the data example to highlight how customer input is crucial. You want to fill your day with a handful of customer inputs, whether that's data, talking to internal teams, or speaking directly with customers.
Being on customer calls is often the best way to gather feedback. This can be for feedback calls or sales calls where the sales team wants me to help close a deal or explain product features.
Staying really close to the customer is one of the first things to do, whether it's looking at data or being directly involved with them.
From there, it's about synthesizing those different inputs into product requirements. This involves documenting what should be on the backlog, prioritizing it, and figuring out what the development team will work on next to solve problems.
So, it's about taking all those inputs, synthesizing them, explaining them, and then getting them to the development team.