🎯 First-Day Diagnostic

First-14-Days Diagnostic: Head of Product at Lumen Health

The Real Situation (honest read)

You weren't hired to 'bring rigor.' You were hired because the board lost confidence in the product org after a 22% revenue miss, and your CEO needs a visible signal to both the board and the new CRO that the problem is being addressed. That's a very different job than the one in the offer letter. The hinted-at underperforming PM is probably already a foregone conclusion in her head — she wants you to validate and execute, not decide. And the fact that Raj found out about your hire the same day you did means someone in that process was careless with him, and he is almost certainly updating his LinkedIn right now. Your hardest problem in week one isn't healthcare domain knowledge. It's that you're inheriting a grieving team with a live flight risk.

The Three Relationships That Matter Most

1. The CEO (your boss)

• What she can make or break: Whether you get the runway to actually diagnose before acting. If she pushes you to fire the underperformer in week three, you lose the team forever.
• First 1:1 question: *'If I told you in 60 days that the underperforming PM is actually one of our strongest and someone else is the real problem, how would you react?'* Her answer tells you whether she wants a partner or an executioner.
• Relationship-poisoning mistake: Agreeing with her read of the team before you've formed your own. She'll respect you less, not more, for it.

2. The new CRO

• What he can make or break: Every deal you lose in the next two quarters will be attributed to product unless you've built a direct line to him. He's also two months in and looking for allies — you have a 30-day window to be one.
• First 1:1 question: *'Walk me through the last three deals we lost. Not the CRM reason — the real reason.'* Then shut up for 20 minutes.
• Relationship-poisoning mistake: Defending the existing roadmap. You didn't build it. Let him vent. Your credibility comes from listening, not from owning Marcus's decisions.

3. Raj (the internal candidate who didn't get the job)

• What he can make or break: The loyalty of the other three PMs. If Raj leaves in month two, at least one other PM will follow within 90 days. If Raj stays and becomes your ally, the team is yours.
• First 1:1 question: *'I know the timing of my hire wasn't handled well for you. Before we talk about anything else — what would have to be true for you to want to stay and do the best work of your career here?'* Do not fill the silence after he answers.
• Relationship-poisoning mistake: Over-promising him a path to Director. Promise him nothing except honesty and a real seat at the table on the next six weeks of decisions.

Observations to Make (Days 1-7)

• Notice which PM the others look at before answering in your first team meeting. That's the informal leader, regardless of title.
• Watch who Slack-DMs you proactively in the first 72 hours vs who waits for you to reach out. The eager ones usually have an agenda; the quiet ones usually have the real information.
• In your first roadmap review, count how many features trace back to a named customer vs a named executive. The ratio tells you how captured the roadmap is.
• Note whether the designer is treated as a peer to PMs or as a resource. In a 140-person B2B company, this tells you how mature the product culture actually is.
• Watch the CEO's body language when Marcus's name comes up. If she flinches, he was fired for cause. If she sighs, he was fired for politics. The two require different recovery plans.
• Notice who on the sales team reaches out to you unprompted in week one. Those are your future roadmap informants.
• Observe whether PM 1:1s with engineering leads happen on calendar or ad-hoc. Ad-hoc means the org runs on hallway conversations you're not in yet.

Questions to Ask (and who to ask them)

• To each PM, separately: 'What's the one decision Marcus made that you disagreed with but didn't push back on?' (This surfaces both their judgment and the team's conflict culture.)
• To the CEO: 'What would you have done differently in the last six months of Marcus's tenure?' (Tests whether she takes any ownership.)
• To the CRO: 'If you could kill one thing on our roadmap tomorrow, what would it be?'
• To the Head of Engineering: 'Where does product and engineering fight, and who usually wins?'
• To the designer: 'When was the last time a design decision changed a PM's mind?' (If the answer is 'never,' you have a bigger problem than the roadmap.)
• To 2-3 account executives: 'Walk me through the last deal you lost. What did the customer say they wanted that we didn't have?'
• To Raj specifically: 'If you had gotten this role, what would your first 30 days have looked like?' (Listen for the parts that are better than yours.)
• To the CEO, in week two: 'Who on the exec team do you trust least right now?' (Uncomfortable, but she'll tell you — and it's critical intel.)
• To HR/People: 'Has anyone on the product team had a retention conversation in the last 90 days?'
• To a board member, if you can get 20 minutes: 'What would make you feel confident about product by the end of Q1?'

What NOT to Do in the First 14 Days

• Do not fire the underperforming PM, even if you agree with the CEO by day 10. The team needs to see you gather evidence, not execute a predetermined verdict. You can always fire someone in week eight; you cannot un-fire them in week one.
• Do not commit to a new roadmap, framework, or operating rhythm. Every 'bring rigor' hire fails by importing their last company's playbook in month one. Your fintech discovery framework will not map cleanly onto hospital procurement cycles. Learn the domain before you prescribe.
• Do not tell the team you 'don't know healthcare yet' more than once. Saying it once is humble. Saying it twice is a license for them to dismiss your judgment for six months.
• Do not accept any meeting Marcus set up that you don't understand the purpose of. Cancel or reschedule. His calendar is not your calendar.
• Do not Slack the CEO with questions you could ask your peers. She's watching whether you generate signal or consume her time.
• Do not present anything to the board in your first 30 days, even if invited. Ask to attend and observe. 'I'd like to listen first' is the most senior thing you can say.
• Do not let the CRO put you on a customer call in week one as the 'new product leader.' You'll get asked roadmap questions you shouldn't be answering yet.

The Quick-Win Trap

The obvious quick win here is announcing a new prioritization framework — RICE, weighted shortest job first, whatever — within the first three weeks. It would feel like 'bringing rigor,' it would please the CEO, and it would give you something to point to. Don't. Marcus almost certainly had a framework. The problem wasn't the absence of a framework; it was that the framework was overridden by whoever yelled loudest in exec meetings. If you install a new framework before you've fixed the override problem, you will be the third Head of Product to fail at Lumen in four years.

Day 14 Checkpoint

By end of day 14, you should be able to answer:

1. Which PM is the underperformer in the CEO's head, and do you agree with her read? (You don't have to act — just know.)

2. Is Raj a flight risk in the next 60 days, and what would keep him?

3. What are the top three reasons Lumen is losing deals, according to sales — not according to product?

4. Who on the exec team will resist whatever product changes you make, and why?

5. What is the one thing you'd change tomorrow if you had full authority — and what is the one thing you'd wait six months to change even if you could do it tomorrow?

If you can't answer any of these by day 14, don't make any strategic moves in day 15-30. Keep listening.