Hire a PM

To: Rosa Lindqvist, VP Product From: Director of Product Date: [Current Date] Subject: Recommendation: Group PM, Patient Payments

---

Recommendation

Hire Joy Adeyemi. Do not hire Dev Malhotra.

While the post-debrief scores show Dev at straight 4s and Joy at straight 3s, the underlying interview notes tell the opposite story. Dev embodies a classic “style over substance” trap that poses severe risks to our culture and business metrics. Joy is an evidence-driven, outcome-oriented product leader whose track record directly maps to our core objective: moving our online payment rate from 41%.

Before extending an offer by Friday, we need to complete one targeted reference check on Joy’s executive influence with Finance.

---

Debrief Context & Scorecard Calibration

The debrief scores were distorted by presentation polish and group dynamics: * Anchoring: The Head of Design spoke first, captivated by Dev’s live wireframing and presentation deck. * VP Engineering flip: Before the group discussion, the VP of Engineering wrote in his private notes: “Joy: 4, strongest leader we’ve seen.” He only downgraded her to a 3 after the room leaned into Dev’s charisma. * Scorecard alignment: Our mandate is lifting payment conversion, leading three PMs, and collaborating with Compliance and Finance. When evaluated against our weighted scorecard, Joy clearly outperforms Dev.

---

The Evidence: Why Joy

#### 1. Analytics (20%) & Product Sense (25%) * Joy delivers outcomes; Dev counts outputs. Joy grew payment completion from 33% to 47% over 18 months at her prior company—almost the exact challenge we face with our 41% baseline. She demonstrated authentic experimentation rigor by walking through a failed test and the specific learnings extracted. * Methodology vs. guesswork: In product sense, Dev generated six feature ideas in five minutes without asking a single question about our users. Joy spent the first 15 minutes diagnosing who pays and why they do not pay online. Only then did she offer a targeted solution: text-to-pay targeting the 58% of patients who pay by phone, accompanied by nuanced trade-offs. * In contrast, when pressed on metrics, Dev claimed he “grew the platform massively,” pointing solely to shipping “40+ features.” He showed zero metric accountability.

#### 2. People Leadership (20%) * Retention vs. Turnover: Joy demonstrated servant leadership—she credited her engineers, coached a struggling PM into a better-fitting role, and promoted another. * Dev spoke entirely in the first person (“I”) and remarked that his past PM team “struggled to keep up with me.” Critically, your backchannel reference confirmed: “great in front of execs; his team turned over a lot.” * Bringing Dev in to manage three PMs is an unacceptable retention risk. Joy will develop and retain our talent.

#### 3. Execution & Influence (35%) * Dev’s influence relies on performative deck-building. While impressive on the surface, feature-heavy roadmaps disconnected from metrics collapse when scrutinized by cross-functional peers. * Joy influences with data, structural diagnosis, and trade-offs. In a domain governed by Compliance and Finance, rigorous substance will earn far more durable trust than slick slides.

---

Key Risks & Mitigation

Risk 1: Joy’s perceived “lack of presence” with the CFO. * The concern: Debrief feedback questioned whether she can “command the room” with Finance. * The reality: Introversion or deliberate pacing is often misread as a lack of authority. CFOs in healthcare payments do not want flash; they want airtight unit economics, regulatory awareness, and defensible data. Joy’s structured, trade-off-led approach is well-suited to Finance, but we must verify this. * Mitigation: We will run a targeted reference check specifically addressing her relationship with senior finance stakeholders (detailed below).

Risk 2: Dev’s counter-risk (The Cost of the Alternative). * Hiring Dev risks churn across all three PM reports within 12 months, feature bloat that fails to budge our 41% rate, and friction with Compliance when rapid-fire feature shipping bypasses regulatory rigor.

---

What to Check Before Making the Offer

We can resolve remaining questions and finalize an offer before Friday’s deadline:

1. Targeted Reference Check (Finance/CFO Influence): Neither candidate had their references asked about working with Finance. Today, I will call Joy’s former manager and peer to ask: * “How did Joy manage pushback from Finance, Legal, or Compliance?” * “Describe a time Joy had to present a high-stakes proposal or trade-off to the CFO/executive team. How was it received?” 2. Optional 30-Minute Touchpoint with our CFO (Thursday): If the reference leaves any ambiguity, set up an informal 30-minute working chat between Joy and our CFO focused on a single payment reconciliation scenario. This will give our CFO direct input and dispel presence-based bias.

---

Compensation

• Band: $220,000 – $250,000
• Joy’s Ask: $230,000
• Dev’s Ask: $245,000

Joy’s ask sits comfortably near the midpoint of our band, leaving room for merit increases while saving $15,000 in baseline compensation compared to Dev.

Next Steps

With your sign-off, I will conduct Joy’s targeted Finance reference check this afternoon, brief the VP of Engineering on our rationale, and have an offer letter ready for Joy at $230k by Thursday morning to meet the CEO’s Friday deadline.

To: Rosa Lindqvist, VP Product Subject: Group PM, Patient Payments — recommend Joy, subject to targeted checks by Friday

Rosa,

I recommend hiring Joy Adeyemi, contingent on validating her ability to set strategy and influence Finance and Compliance. The interview evidence is stronger for Joy on the work this role requires: improving payment outcomes, making customer-grounded product decisions, and developing PMs. Dev’s presentation strength is clear, but the evidence does not support his uniformly exceptional scores.

We should complete focused checks before Friday rather than let either the debrief’s consensus or the deadline substitute for evidence.

Why Joy

Our agreed scorecard—not presentation polish—should drive the decision.

Why I would not rely on the recorded scores

The 4s for Dev and 3s for Joy were entered after the discussion, so they are not independent assessments. The VP Engineering’s contemporaneous note—“Joy: 4, strongest leader we’ve seen”—conflicts with the submitted 3. Combined with the Head of Design speaking first and enthusiasm about Dev’s deck, this creates a credible risk of anchoring and presentation halo.

“Not much presence” and “command the room” are not sufficiently specific hiring criteria. We need evidence of gaining alignment, handling disagreement, and changing consequential decisions—not a proxy based on communication style. This does not prove bias or invalidate every judgment; it means the scores need reconciliation with observed behavior.

I would ask each interviewer to independently reassess their dimension against the original rubric, cite evidence, and explain any change from their pre-debrief assessment. I would not manufacture replacement scores from these notes.

Risks in hiring Joy

• Executive and cross-functional influence is unproven. Strong product judgment will not be enough if she cannot resolve disagreements with Finance and Compliance.
• Group-level strategy remains under-tested. One well-reasoned product proposal does not establish an ability to set a portfolio strategy or allocate work across three PMs.
• Her reported impact needs attribution. We need to understand what she owned, what other changes contributed, and whether the gains were durable.

Dev’s executive presentation skill is a genuine strength. However, selecting him now would require overlooking gaps in measurable outcomes and substantial unanswered leadership questions. His current direct-report references offer a limited perspective; the informal turnover report is also insufficiently substantiated.

Checks before an offer

1. Focused, structured working session with Finance and Compliance. Ask Joy to outline a patient-payments strategy from our 41% online payment baseline, identify missing data, prioritize opportunities, and explain how she would organize three PMs. Introduce a realistic conflict involving collections, patient experience, cost, and compliance constraints. Assess decision quality, listening, trade-off handling, and ability to reach a workable decision—not performance style. A CFO or senior Finance delegate and Compliance partner should score independently before discussing.

2. Targeted reference follow-ups, with Joy’s consent. Ask her former manager and peer for concrete examples of disagreement with a CFO or Finance leader, work with Compliance, strategy ownership, and developing PMs. Verify the 33%–47% result, her contribution, and measurement. Seek an additional relevant cross-functional reference if those references lack direct visibility.

3. Reconcile the interview record. Complete the independent score review and explicitly resolve the leadership-score discrepancy. Document remaining uncertainty rather than forcing consensus.

Friday decision: If these checks substantiate Joy’s strategy and influence capabilities, proceed with her offer. If they reveal a material gap—or cannot establish the essential evidence—I recommend neither, not defaulting to Dev.

Joy’s $230k request and Dev’s $245k request are both within the $220k–$250k band. Compensation should not decide this choice; set Joy’s offer based on scope and internal equity, not simply her lower ask.