Open this lesson in your favourite AI. It'll walk you through the why, explain the demo, and quiz you on the try-it list.
Course 1 covered hardware-PM extensively. Software-PM (this course) has its own rhythm. Hybrid teams (hardware + companion software) live in both worlds. Understanding the differences — and similarities — clarifies what's universal vs. what's context-specific.
PM by product type.
Use these three in order. Each builds on the one before.
Explain in one paragraph the difference between hardware PM and software PM.
Walk me through a typical day for a hardware PM vs. a software PM.
Given a PM transitioning from software to hybrid (hardware + software), what new disciplines must they pick up?
HARDWARE PM:
Constraints:
- BOM cost (every dollar matters at scale).
- Manufacturing lead times (8-26 weeks).
- Regulatory cert (FCC, CE, UL).
- Physical inventory + logistics.
- Long product cycles (1-3 years).
- Customer support is expensive (RMA, repairs).
Daily work:
- Reviewing CAD designs.
- Approving BOM revisions.
- Tracking yield + reliability.
- Coordinating cross-team (firmware, EE, ME).
- Managing CM relationship.
Pace:
- Slower deliberation.
- Once shipped, hard to change.
- Each major decision = $$$.
SOFTWARE PM (this course's focus):
Constraints:
- Engineering time (the scarce resource).
- Cloud cost (matters but secondary).
- Compliance (GDPR, SOC2, etc.).
- No physical inventory.
- Short product cycles (weeks-months).
- Customer support is software (chat, KB, easier).
Daily work:
- Customer interviews + analytics.
- PRDs and design reviews.
- Sprint planning + standups.
- Metrics analysis.
- Stakeholder management.
Pace:
- Fast iteration.
- Ship and revise constantly.
- Each decision = engineering time (the constraint).
HYBRID PM (hardware + companion software):
Combines both worlds. Common in:
- Wearables (device + app).
- Smart home (device + cloud).
- Connected vehicles.
- Medical devices (device + companion app).
Specific challenges:
- Two cadences (hardware annual, software weekly).
- Cross-stack integration testing.
- Two compliance regimes.
PM job:
- Decide which workstream gates the release.
- Manage handoffs between worlds.
- Often: hardware-PM and software-PM are different people on same product.
OPENPED + RUNCOACH AS HYBRID:
Original OpenPed: device only. Cohen's framing.
In reality: most modern hardware = hardware + companion app.
RunCoach: software only.
Hybrid version: OpenPed device + RunCoach companion.
- Device PM: hardware lifecycle (1-2 year cycle).
- Software PM (you): companion app (weekly iteration).
- Combined: product strategy unifies both.
WHAT TRANSFERS:
All Cohen's discipline transfers to software:
- Customer obsession (Sins #2-3).
- Specs and requirements (Ch. 5, 11).
- Reality checks and gates.
- Document control.
Plus modern software-specific layer:
- Continuous delivery.
- A/B testing.
- Analytics-driven iteration.
THIS MODULE'S FOCUS:
Identify your PM type. Identify what's specific to your type vs.
what's universal.