Table of Contents
What is Product Management?
Product Management is the function that guides a product from idea to delivery.
It sits at the intersection of business, users, and technology.
The goal: build products that solve real problems.
You don’t need to code. You need to think clearly, ask the right questions, and drive execution.
Understanding the Product Manager Role
A Product Manager (PM) owns the product’s success.
You don’t manage people. You manage the product.
You’re the link between:
- Customers (what do they need?)
- Business (what drives revenue?)
- Developers (what can be built?)
You prioritize what gets built, why, and when.
PMs make decisions with limited data and high stakes. You’re not the boss, but you set the direction.
Core Product Manager Responsibilities
Here’s what PMs actually do:
- Define product vision and goals
- Understand customer problems through research
- Write product specs and user stories
- Prioritize features in the backlog
- Collaborate with engineering and design teams
- Monitor product performance and usage
- Communicate with stakeholders
On a typical day, a product manager might:
- Run a standup with developers
- Review wireframes from design
- Interview a user
- Tweak a product roadmap
- Write a product brief
- Explain priorities to leadership
This is the real day-to-day of a product manager. Meetings. Decisions. Trade-offs. Communication.
Do You Need a Tech Background?
No. Many great PMs come from business, marketing, design, or operations.
You do need to understand how tech products work. But you don’t need to write code.
Focus on learning:
- How software is built
- How teams collaborate
- What users want
You’ll learn by doing. Start small. Build context.
PM Skills You Must Build
Here are the core PM skills that matter most:
- User empathy – Understand pain points
- Prioritization – Decide what matters most
- Communication – Share decisions clearly
- Problem-solving – Break down issues fast
- Execution – Get things shipped
- Data literacy – Read numbers, not just opinions
- Stakeholder management – Align different voices
No fluff. You don’t need to be a genius. You need to be curious, organized, and action-oriented.
How to Become a Product Manager (Step-by-Step)
Step 1: Learn the Basics
Start with the foundations. Read up on product management, agile, and product development.
Use these free resources:
- Atlassian Product Guide
- Product School’s blog
- Mind the Product articles
Know what a product manager really does.
Step 2: Pick a Simple Problem to Solve
Don’t wait for permission. Find a problem around you.
Examples:
- Your church scheduling system sucks?
- Your uncle’s bakery gets too many wrong orders?
Design a solution. Sketch the flow. List out features. Talk to users.
This is product thinking.
Step 3: Work on a Real Product
Volunteer. Intern. Freelance. Build something—even if it’s small.
Work with a developer or no-code tools like:
- Notion
- Glide
- Softr
- Webflow
Own the process from idea to launch. That’s what PMs do.
Step 4: Document Everything
Keep track of what you’re learning.
- Write user stories
- Map user journeys
- Prioritize features
- Track metrics
Build a portfolio. Show how you think. Explain your decisions.
No one hires PMs based on ideas. They hire based on judgment.
Step 5: Learn to Work with Developers
You don’t have to be a dev. But you must work well with them.
Understand:
- What front-end vs back-end means
- How APIs work
- What makes code slow or buggy
Use YouTube or freeCodeCamp to learn basics. Ask devs to explain things to you.
Respect their work. Speak their language.
Step 6: Apply for PM Roles or PM-like Roles
If you’re new, look for titles like:
- Associate Product Manager
- Product Analyst
- Project Coordinator
- Business Analyst
These roles build PM muscle. Don’t chase the title. Chase the experience.
Get in. Prove your thinking. Then grow fast.
What About Certifications?
Optional. Not mandatory.
If you want structure, consider:
- Google’s Product Management Certificate
- Product School certifications
- Reforge courses (advanced level)
But don’t overdo it. Execution > Certification.
Common Misconceptions
- PMs are CEOs of the product — False. You don’t have authority over others.
- You need an MBA — Not true. Results matter more.
- It’s all strategy — No, there’s a lot of coordination and grunt work.
- You must have a tech background — Wrong. You need product sense, not code.
Summary: Day-to-Day of a Product Manager
You’re not coding. You’re not designing.
You’re:
- Asking the right questions
- Listening to users
- Writing clear specs
- Aligning teams
- Prioritizing work
- Managing trade-offs
It’s not about perfection. It’s about progress.
Final Thoughts
Product management is one of the most impactful roles in tech.
You don’t need a tech degree. You need clarity, curiosity, and commitment.
If you’re serious: Start now. Build something. Solve a real problem.
That’s how you break into product management.
Dr. Oluwaseun Ogunmola
AI Evangelist | Product Manager | Project Manager
https://www.linkedin.com/in/seunogunmola
Sources:
- Atlassian: What is Product Management? — https://www.atlassian.com/product-guide/product-management
- Product School: What Does a Product Manager Do? — https://productschool.com/blog/product-management-2/what-does-a-product-manager-do
- Harvard Business Review: The Hardest Role in the C-Suite — https://hbr.org/2021/05/the-hardest-role-in-the-c-suite
- Mind the Product: What is a Product Manager? — https://www.mindtheproduct.com/what-is-a-product-manager/
- Roman Pichler: Product Management Guide — https://www.romanpichler.com/blog/product-management-guide/
