Product Management
How to Get into Product Management: A 90-Day Guide
Kumar Abhijeet · · 5 min read
What Product Management is, and why it matters now
Product Management is the discipline of finding meaningful customer problems, shaping solutions, and working with different teams to build products that create value for users and for the business. A Product Manager (PM) sits where business, technology and user experience meet.
The role matters more in uncertain times. Customer expectations shift quickly, technology keeps evolving and AI is changing how organisations work. Companies need people who can make sense of that uncertainty, pick the right problems and align teams around outcomes rather than long task lists.
- Understand customers, markets and unmet needs.
- Set direction, define priorities and make trade-offs.
- Connect business goals with technology and user experience.
- Use research and data to decide, and to measure whether it worked.
You can arrive from many backgrounds
PM is not reserved for software engineers or MBA graduates. Your current role has probably already given you some of the building blocks. Your job is to translate them into product language.
| Your background | Strengths that transfer |
|---|---|
| Engineering / IT | Technical understanding, systems thinking, structured problem solving. |
| Sales / Marketing | Customer conversations, market insight, positioning and communication. |
| Operations | Process improvement, execution, coordination and stakeholder management. |
| Business / Finance | Commercial awareness, analytical thinking and business strategy. |
| Design / UX | User research, usability, interaction design and customer experience. |
Choose your pathway: tech or non-tech?
Both routes reach the same destination. They differ in the gap you need to close. Start with the one nearest to your experience.
If you come from engineering or IT
You already understand how products get built. The gap is usually business thinking and customer discovery.
Leverage your technical skills
Use your credibility with engineers as an asset.
Learn strategy and business basics
Markets, pricing, revenue and competition.
Build discovery, UX and prioritisation skills
Talk to users and learn to say no.
Create a teardown and a case study
Show your thinking in writing.
- Target roles: Technical PM, Associate PM (APM), Product Manager.
If you come from business, operations, sales or design
You understand customers and the domain. The gap is usually technology fluency and product craft.
Leverage your domain and customer knowledge
You know real problems that engineers may not.
Learn technology and product basics
How software gets built, shipped and measured.
Build PRD, UX and metrics skills
Write clearly and define success.
Create a teardown and a case study
Show your thinking in writing.
- Target roles: Associate PM (APM), Domain PM, Product Manager.
Build evidence
Practise interviews
Apply
The 90-day transition framework
Use this alongside your current job. Each month mixes learning with doing and ends with something you can show. The goal is not to collect certificates. It is to build evidence that you can do the work.
Month 1 · Learn
Think like a PM
Learn
- Product lifecycle and discovery
- Strategy, roadmaps and prioritisation
- Agile, Scrum, user stories and PRDs
- RICE, MoSCoW and Jobs-to-be-Done
Practise
- Pick a product you know well, such as a maps app or a food-delivery app
- Identify its users, needs and pain points
- Analyse features and the experience
- Recommend three improvements with reasons
You finish with
A product teardown document
Month 2 · Build
Do the work
Learn
- User research and UX basics
- Wireframing and prototyping
- Product analytics: activation, conversion, retention
- APIs, databases and AI concepts at a basic level
Practise
- Interview 5 to 10 potential users
- Choose one meaningful problem
- Map the user journey and sketch wireframes
- Write a concise PRD with success metrics
You finish with
A mini case study with wireframes and a PRD
Month 3 · Get ready
Show it and apply
Learn
- Product sense and execution interviews
- Prioritisation, estimation and trade-offs
- Stakeholder management and communication
- Research target companies and role expectations
Practise
- Polish two or three case studies
- Prepare stories from your work history
- Practise mock interviews
- Update your resume and LinkedIn, then start networking and applying
You finish with
A PM portfolio, an interview-ready profile and a live job pipeline
How to write a case study people actually read
Hiring managers see many portfolios. The ones that stand out are short, honest and clear about the thinking behind each decision. Use this structure:
- The problem: who is struggling, with what, and how do you know?
- The evidence: a few quotes or numbers from your user interviews.
- The options: two or three ideas you considered, and why you chose one.
- The solution: a simple wireframe and a one-page PRD.
- The measure: how you would know it worked, such as activation or retention.
Common mistakes to avoid
- Collecting certificates instead of building something you can show.
- Jumping to solutions before talking to real users.
- Hiding your past experience. Your previous career is your edge, so explain how it applies.
- Waiting until you feel ready. Start the teardown this week.
Where to begin
Choose one product you use every day and write down three things that frustrate you about it. That small step is the start of your teardown, and the start of thinking like a Product Manager.
Want to talk about this?
Questions about your career or your business? Let's start a conversation.
Get in touch