The document discusses transitioning from a business analyst to a product manager role. It outlines the key similarities and differences between the two roles. Both business analysts and product managers solve problems, but product managers own metrics and focus on designing for the user experience, while embracing uncertainty. The document recommends choosing a product manager career if you enjoy solving user problems, driving execution, and are comfortable with uncertainty. It suggests ways to transition such as identifying strengths and weaknesses, building products, and talking to users.

1. Business Analyst
To Product Management
Why, where and how to start
Phuong Nguyen
Senior Product, Zalo
Twitter: @NguyenJackson

2. Disclaimer
The knowledge shared in this presentation is solely my own point
of view, which doesn’t necessarily represent my employer’s.

3. Let’s start with a
business

4. CustomerAgency
Insurance company XYZ

5. CustomerAgencyNew BusinessUnderwriting
Customer
Service
Agency
Admin
IT
Insurance company XYZ

6. CustomerWebsiteNew BusinessUnderwriting
Customer
Service
Agency
Admin
IT
IT
Insurance company XYZ

7. CustomerWebsiteNew BusinessUnderwriting
Customer
Service
Agency
Admin
Product Manager
Business Analyst
Insurance company XYZ

8. Business Analyst
Solve ..… problem by designing better …..

9. Business Analyst
Solve business problem by designing better process

10. Product Manager
Solve ..… problem by designing better …..

11. Product Manager
Solve user problem by designing better experience

12. Similarities?

13. 1. We solve problems

15. Solving prob means:
breakdown use cases
eliciting insights across sources
focus on most important bottleneck
design solution

17. 2. We execute

20. Execution means:
comfortable with conflicts
empower our team
and do whatever it takes to win

22. Differences?

23. 3. We own the metric,
not process

25. Metric
metric quantifies how delightful your users are
your success as PM = metric achievement
usually takes multiple projects

26. 4. We embrace
the uncertainty

28. Uncertainty
A to B vs. A to A’ / A’’ / A’’’
Constant listening to feedback & iterating
Take calculated risk and learn from failure

31. 5. We design for user,
not business

32. Design for user
zoom in touchpoints, not only process
remove friction
make users excited

35. Summary

36. Choose PM
path if you:
• Like solving problems
• Are hustling executioner
• Want to own the outcome
regardless solutions
• Are comfortable with uncertainty
and lack of direction
• Design with user in mind

37. Transit to
PM by:
• Identify your strengths & weakness
• Weakness: Learn from reading &
talking to seniors
• Strength: Develop your own
opinions
• Build real products & talk to real
users

38. Welcome to
Product Management

39. Questions?
Phuong Nguyen
Senior Product, Zalo
Twitter: @NguyenJackson

40. Additional
resources:
• Problem solving: Design sprint
• Project mgmt: Roadmapping,
Prioritisation, Working with dev,
designer
• Growth: Product-market fit, Growth
accounting framework
• CEO mindset: Good Product
Manager/Bad Product Manager
• UX Design: principles, platform
guidelines (iOS, Android)