Jadi Product Manager: Skill, Gaji, dan Kesehariannya | #KarierTalk with Gurun Nevada Dharan

Presenters & Backgrounds

• Bang Gurun Nevada Dharan — Founder; previously Head of Product at Dana Indonesia; earlier experience in logistics.
• Meta — Host; works on the Product Team at “Glees/Glean(s)” (name unclear from subtitles).

---

1) Product Manager’s Core Responsibility & Daily Workflow

Core mission

“Discover what product to build” by solving real problems and ensuring the solution is effective.

Typical daily rhythm (Bang Gurun’s workflow)

• Morning (before 9 AM): open laptop → check dashboards to understand the current product/business state.
• Customer discovery: build problem understanding through:
  • direct customer chats
  • market research
  • collaboration with sales (collect data)
  • field visits / “spend a day in the field”
• Hypothesis + documentation (often PRD day):
  • document hypotheses
  • align with design on design direction
  • align with tech for rough technical design
• Stakeholder management dominates time:
  • frequent meetings with sales, marketing, management/executives to secure vision & buy-in, and resources/time
  • some collaboration after office hours is common, but asynchronous collaboration is preferred where possible

Dashboard mindset

Dashboards are not “passive monitoring”—they’re meant to trigger investigation and follow-up actions.

---

2) Frameworks & Playbooks for Monitoring Product Health

UX/Customer metrics lens: AARRR-style journey + UX signals

Two broad categories are referenced:

1. UX problem perspective metrics (user behavior & satisfaction)
2. Business number perspective metrics (growth, activation, monetization, retention)

Explicit frameworks mentioned

• Google “HEART” framework (UX/success signals)
  • Happiness (e.g., CSAT, NPS)
  • Engagement
  • Acquisition
  • Retention
  • related success signals
• AARRR / PIRATES framework
  • Pirates = Acquisition → Activation → Retention → Revenue (referral/re-engagement implied by “AARRR”)
  • used to measure conversion and monetization impact across the funnel

Why retention is emphasized

Retention is described as the most crucial product management signal because it indicates whether users continue to find value.

---

3) Concrete KPI Examples & Business Outcomes

Marketplace / offline transaction example (Dana Indonesia context)

Track:

• # of offline transactions
• # of users who do those transactions (not only transaction volume)
• # of active merchants

Hypothesis:

• More active merchants/users → more transactions → higher profits

Logistics / shipment example

Track multi-level success:

• successful shipments
• on-time rate
• customer satisfaction

Rationale:

• value is achieved only when outcomes include both operational success and customer happiness.

Common “PM KPI set” (industry-agnostic)

• User growth
• Retention
• Engagement
• Revenue-driven outcomes (ultimately tied to business performance)

---

4) How PMs Diagnose KPI Drops (Signal → Validation → Research)

Key idea: dashboard drop is a signal, not the root cause

When a metric drops:

• PMs either:
  • validate quickly using a data deep-dive, or
  • run direct user interviews / qualitative research when the root cause isn’t obvious

Subtitles emphasize:

• opinions can be biased, so user evidence is important when validating.

Operational principle

Dashboard checks should be short—they provide signals; deeper understanding requires follow-up research.

---

5) Skills, Responsibilities, and “Title Confusion” (PM vs Designer vs Developer vs PM)

PM vs UX Designer

• PM: discovery and often delivery involvement (varies by company); focuses on end-to-end product ownership.
• UX Designer: focuses on usability and design execution (not just UI aesthetics).
• Collaboration: both can brainstorm solutions; PM often facilitates and gathers.

PM vs Developer

• Developers: coding and technical execution.
• PM involvement: not required to code, but basic technical understanding helps:
  • faster ideation
  • stronger conversations with tech
  • better comprehension of constraints (e.g., APIs/logic at a high level)

PM vs Project Manager

Not explicitly separated in the subtitles, but implied:

• PM ownership is product outcome-focused, while company-specific title meanings can vary.

---

6) Hiring / Learning Paths & Training Reality (Bootcamps vs Real Execution)

• Bootcamp is optional, not required; useful mainly for hard skills.
• Bootcamp often lacks:
  • real stakeholder negotiation
  • real high-pressure meetings (sales/ops/management/design interactions)
• Practical advice:
  • build soft skills via participation in organizations/committees, networking, and repeatedly handling collaboration scenarios.

---

7) PM Salary Ranges (Career Mapping)

Subtitles provide a “research-style” range by title (numbers are approximate due to auto-captioning):

• Product Analyst: up to ~10M
• APM: up to ~15M
• PM: up to ~25M
• SPM: up to ~40M
• GPM: up to ~60M
• (FV/VP-level): up to ~85M
• (PV/very senior): up to ~100–115M

Also stated:

• Career branches:
  • Specialist / Individual Contributor track
  • People Manager track (requires duplicating quality through coaching/leadership)
• Emphasis: titles vary; value/experience matters more than the label.

---

8) Leadership & Team Operating Rhythm (WFH Example)

Cadence (similar to Agile)

• Daily stand-up: each person shares today’s focus
• Weekly planning / sprint
• Retrospective
• planning done ahead (e.g., Monday planning)

Delegation as a leadership skill

PMs may struggle to delegate if they feel they’re the “best contributor.” Suggested approach:

• delegate gradually
  • reduce meeting presence over time
  • let others run sessions
  • move from direct control to empowerment
• Shadowing is mentioned, but framed as not ideal if rigid—real responsibility transfer matters.

---

9) Actionable Recommendations Implied by the Talk

• Make monitoring part of the routine:
  • Check dashboard → detect signal → validate with users/data
• Use frameworks as lenses, not just dashboards:
  • HEART for UX signals
  • AARRR/PIRATES for funnel progression
• Align early with stakeholders:
  • design/tech for feasibility & PRD
  • sales/marketing for GTM alignment
  • management for vision/resources/buy-in
• Don’t over-index on tooling:
  • asynchronous collaboration can improve throughput
• Build broad product intuition:
  • understand enough about SDLC/tech to collaborate effectively, even without coding.

---

Presenters / Sources (As Mentioned in Subtitles)

• Meta — Product Team host (name shown as “Meta” in subtitles)
• Bang Gurun Nevada Dharan — Founder; ex Head of Product at Dana Indonesia; logistics background