A framework for PM skill development | Vikrama Dhiman (Gojek) — Lenny's Podcast: Product | Career | Growth Summary

A framework for PM skill development | Vikrama Dhiman (Gojek) — Lenny's Podcast: Product | Career | Growth Summary | Galaxy of Podcasts

The Conversation Breakdown

Produce something tangible while learning the role

⏱ Untimed topic

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

⏱ Untimed topic

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

⏱ Untimed topic

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

⏱ Untimed topic

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

⏱ Untimed topic

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

⏱ Untimed topic

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

⏱ Untimed topic

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.

A framework for PM skill development | Vikrama Dhiman (Gojek)

Executive Summary (TL;DR)

Key Takeaways

Produce something tangible while learning the role

Keep execution skills as responsibility grows

Develop across four skill pillars

Turn questions into usable choices

Include the operating model in development

Practice work that is within your control

Connect disciplines rather than standing apart

The Conversation Breakdown

Produce something tangible while learning the role

Keep execution skills as responsibility grows

Develop across four skill pillars

Turn questions into usable choices

Include the operating model in development

Practice work that is within your control

Connect disciplines rather than standing apart

Core Frameworks & Ideas

Output and outcome

Four skill pillars

Operating model

Actionable Next Steps

Notable Quotes

The One Thing to Remember