Orientation Week: What to Figure Out First

Whether you're brand new to a PM role or transitioning from one type of product to another, the first thing you need to do is orient yourself. Not around the backlog, not around the team, but around the fundamental nature of what you're managing.

Here is a practical orientation checklist you can use in your first 30 days:

Step 1: Classify Your Product Layers

List every artifact, system, or experience that your product includes. For each one, ask:

• Is this physical, digital, or regulated?
• What's the feedback loop for this layer? (How fast can I know if something is broken?)
• What's the cost of change? (How hard is it to fix a mistake here?)
• Who else has control over this layer? (Internal team, external vendor, regulator?)

Step 2: Find the Constraint

Every product has a binding constraint — the one thing that limits how fast you can move and how much value you can deliver. For physical products, it's often the supply chain or manufacturing capacity. For digital products, it's often engineering bandwidth or data quality. For regulated products, it's the approval pipeline.

Understanding your binding constraint is not defeatist — it's strategic. Good strategy is about identifying the pivotal challenge and focusing your effort there, not about spreading effort evenly across everything.

Step 3: Build Your Metric Dashboard

Before you touch the backlog, before you attend a planning meeting — find out what is currently being measured. Ask yourself:

• Are we measuring outputs (features shipped, velocity) or outcomes (user behavior, business results)?
• Do we have a North Star metric? Does the team agree on it?
• Are our metrics actionable — do they cause us to make decisions?

If your team is measuring outputs only, that's your first improvement opportunity. Start building the case for outcome-based metrics, tied to user value and business performance.

Step 4: Understand the Last Three Decisions

Talk to your manager and teammates. Find out: what were the last three major product decisions made, and what drove them? Were they data-driven? Customer-driven? Executive-driven? This tells you more about how product management actually works at your company than any onboarding document.

The New PM's Mindset

New PMs often feel pressure to have all the answers, propose solutions immediately, and demonstrate value by shipping things. Resist this.

Your value as a PM is not in having answers — it's in asking the right questions. The best product managers are obsessed with problems, not solutions. Before you commit to building anything, ask:

• Do we actually understand the problem this is solving?
• Who has this problem, and how often do they have it?
• What happens to them today if this product doesn't exist?
• Have we tested whether our proposed solution actually addresses the problem?

This applies whether you're managing a physical product, a digital one, or a hybrid. The method of testing looks different (ethnographic research vs. A/B testing), but the discipline is the same.

Key Insight: The worst product decisions come from solving imaginary problems or building solutions in search of a problem. Your job is to reduce that risk — constantly.

A Word on Auto Insurance as a PM Context

You're working in a domain that is simultaneously highly regulated, highly competitive, and increasingly digital. Canadian auto insurers are under pressure from insurtechs, changing driving patterns, telematics-driven pricing models, and customers who now expect the same digital experience from their insurer that they get from their bank or streaming service.

This means your skills across both physical and digital PM will be tested — often in the same week. The claims app needs to iterate rapidly to meet customer expectations. The underlying product filings need to navigate regulatory timelines. The telematics program needs physical device management *and* real-time data analytics.

This is not a burden — it's a massive opportunity. PMs who understand both worlds are rare and valuable. You're building that understanding right now.

Final takeaway: The distinction between physical and digital PM is not about job titles or industry sectors. It's about understanding the constraints you're operating within, choosing the right tools for those constraints, and measuring success by outcomes — not by activity.