Your First Week as a PM

Starting a New PM Role

Your first weeks as a PM are about learning, listening and building trust, not about shipping big changes. You will be tempted to prove yourself quickly. Resist that. A PM who makes changes before understanding the product, the users and the people usually makes avoidable mistakes.

Imagine you have just joined a fintech in Lagos, Nairobi, or London as the PM for its bill-payment product (airtime, data, electricity and cable TV). Here is how to make the most of your start.

---

Week 1: Learn the Landscape

1. Understand the product as a user

• Use the product daily. Buy airtime, pay an electricity bill, and note every point of friction.
• Read app store reviews and social media complaints. What do people love? What makes them angry?
• Try the main competitors. How does their flow compare?

2. Read what already exists

• Product documents, past PRDs and roadmaps.
• Dashboards: key metrics, trends, and any recent dips.
• Post-mortems from past incidents, which reveal how the company handles problems.

3. Meet your team

Have one-to-one conversations with your engineers, designer, QA and data analyst. Useful questions:

• What is going well? What is frustrating?
• What should I know that is not written down anywhere?
• If you were in my seat, what would you look at first?
• How do you like to work with a PM?

4. Take notes

Keep a running document of what you learn, especially questions that you cannot yet answer. In a few months, those early observations, seen with fresh eyes, will be very valuable.

---

Stakeholder Mapping

A stakeholder is anyone who is affected by your product or can influence its success. Product managers succeed through other people, so you must know who they are.

Who are typical stakeholders?

• Engineering, design, QA, data (your core team)
• Customer support (they hear complaints daily)
• Sales and partnerships (for example, relationships with telecom operators and utility companies)
• Compliance, legal and risk (crucial in fintech, given regulations from bodies such as the Central Bank of Nigeria, the UK's FCA, and standards like PCI-DSS and GDPR)
• Finance and leadership
• Customers and external partners

The Power/Interest grid

Plot each stakeholder by how much power they have over your product and how interested they are in it.

For example, the Head of Compliance may have high power and moderate interest: they can block a launch, so you should involve them early. Customer support has lower formal power but high interest and rich insight, so you should keep them close.

Build relationships early

For each key stakeholder, find out:

1. What do they care about most?
2. How do they prefer to communicate?
3. What do they need from you?
4. What can you do for them?

---

The First 30-60-90 Days

A 30-60-90 day plan gives structure to your onboarding and shows your manager that you have a plan. Share a draft in your first week and ask for feedback.

Days 1-30: Learn

• Understand the product, users, market and metrics.
• Meet all core stakeholders and your team.
• Read documentation and past decisions.
• Talk to at least 5-10 customers.
• Deliver a small quick win, such as fixing a confusing error message or writing a clearer ticket template.

Goal: Be able to explain the product, its users and its biggest problems clearly.

Days 31-60: Contribute

• Take ownership of a defined piece of work, such as a feature or improvement.
• Write your first PRD and run the planning meeting.
• Set up or refine the metrics for your area.
• Identify two or three opportunities based on your research.

Goal: Ship something small and show you can work well with the team.

Days 61-90: Lead

• Propose a roadmap or a clear priority list, supported by evidence.
• Lead a full cycle from problem to launch to measurement.
• Share what you have learned with leadership.
• Agree goals for the next quarter with your manager.

Goal: Be recognised as the owner of the product area, trusted to make decisions.

---

Common Mistakes to Avoid

• Changing too much too fast. You do not yet know why things are the way they are.
• Pretending to know everything. Saying "I don't know, let me find out" builds more trust than bluffing.
• Skipping the engineers. Building respect with your engineering team is one of the best investments you can make.
• Working in isolation. Share early, ask for feedback, and avoid surprises.
• Ignoring the numbers. Learn your key metrics in the first week and keep checking them.
• Not asking for help. A good manager expects questions and wants you to ask them.

---

Habits That Last

• Keep a weekly update for your stakeholders: what happened, what is next, what is blocked.
• Schedule regular customer conversations and never stop.
• Keep a decision log so you can remember why choices were made.
• Ask for feedback from your manager and peers every month.

Being a PM is a craft that you improve with practice. Start with curiosity and humility, and the rest will follow.