A framework for PM skill development | Vikrama Dhiman (Gojek)
Executive Summary
Vikrama Dhiman describes useful outputs, outcomes, four PM skill pillars, the operating model and collaboration across disciplines. Selected third-party transcript coverage excludes promotion promises, financial figures, mental-health interpretations, product recommendations and sponsor reads. Company and career examples are his views, unverified here. Untimed editorial topics are not video chapters.
Key Takeaways
Produce something tangible while learning the role
Dhiman describes output as a concrete contribution that the team can use, including a draft, analysis or launched feature. Early work need not begin with owning the entire strategy. A useful piece of work can help the team while giving the person practice in the craft.
Keep execution skills as responsibility grows
He says moving toward outcomes does not remove the need to produce good outputs. Senior work still benefits from understanding how artifacts are made and how they help the team. Leadership and hands-on craft are connected rather than mutually exclusive.
Develop across four skill pillars
Dhiman names data and metrics, design and research, technology skills, and strategy. The pillars help identify where practice is broad or narrow. They are his development lens, not an official certification or a guarantee that mastery leads to promotion.
Turn questions into usable choices
He distinguishes bringing only arguments and pushback from turning input into strategic choices that shape discussion. The value is in helping the team move from an unresolved question toward a decision. A PM's contribution is more than the number of documents created.
Include the operating model in development
Dhiman describes communication, collaboration, organizational skills and community as part of how a PM works. Better analysis alone does not cover all the role's demands. Look at how the person helps other people coordinate and contribute.
Practice work that is within your control
He recommends focusing on craft, outputs and collaboration rather than spending all attention on decisions made elsewhere. The practical distinction is between an action one can take and a condition one cannot change directly. This is career advice from the guest, not a claim that every career obstacle is personal.
Connect disciplines rather than standing apart
Dhiman describes PM work as pairing with data, design, technology and strategy. That position can help someone see connections across the team. The role is useful when it increases the team's ability to work together, not when it claims sole ownership of everyone else's expertise.
The Conversation Breakdown
Produce something tangible while learning the role
⏱ Untimed topicDhiman describes output as a concrete contribution that the team can use, including a draft, analysis or launched feature. Early work need not begin with owning the entire strategy. A useful piece of work can help the team while giving the person practice in the craft.
Keep execution skills as responsibility grows
⏱ Untimed topicHe says moving toward outcomes does not remove the need to produce good outputs. Senior work still benefits from understanding how artifacts are made and how they help the team. Leadership and hands-on craft are connected rather than mutually exclusive.
Develop across four skill pillars
⏱ Untimed topicDhiman names data and metrics, design and research, technology skills, and strategy. The pillars help identify where practice is broad or narrow. They are his development lens, not an official certification or a guarantee that mastery leads to promotion.
Turn questions into usable choices
⏱ Untimed topicHe distinguishes bringing only arguments and pushback from turning input into strategic choices that shape discussion. The value is in helping the team move from an unresolved question toward a decision. A PM's contribution is more than the number of documents created.
Include the operating model in development
⏱ Untimed topicDhiman describes communication, collaboration, organizational skills and community as part of how a PM works. Better analysis alone does not cover all the role's demands. Look at how the person helps other people coordinate and contribute.
Practice work that is within your control
⏱ Untimed topicHe recommends focusing on craft, outputs and collaboration rather than spending all attention on decisions made elsewhere. The practical distinction is between an action one can take and a condition one cannot change directly. This is career advice from the guest, not a claim that every career obstacle is personal.
Connect disciplines rather than standing apart
⏱ Untimed topicDhiman describes PM work as pairing with data, design, technology and strategy. That position can help someone see connections across the team. The role is useful when it increases the team's ability to work together, not when it claims sole ownership of everyone else's expertise.
Core Frameworks & Ideas
Output and outcome
Deliver useful artifacts while learning which outcomes those artifacts support.
Four skill pillars
Review development in data and metrics, design and research, technology, and strategy.
Operating model
Assess communication, collaboration, organization and community alongside technical product work.
Actionable Next Steps
- ✓Choose a concrete draft or analysis that unblocks the team.
- ✓Map a current contribution to the outcome it supports.
- ✓Identify one skill pillar that needs more practice.
- ✓Pair with another discipline to turn a question into usable choices.
Notable Quotes
“Absolutely. So focus on outputs at the start of your careers and don't forget outputs even when you grow in your career.”
“These things are important to show you are progressing on four pillars, which is data and metrics, design and research, technology skills, and strategy.”
“So it's not about you standing alone, it's you always collaborating and pairing with someone else.”
The One Thing to Remember
Make a useful contribution while continuing to build the craft and collaboration that make outcomes possible.