Below is a structured, teachable approach that you can execute within 48 hours and still show depth. Assumptions - Business is a two-sided travel marketplace. KPI definitions can vary by team. We need to recommend a decision framework and near-term KPI choice without boiling the ocean. - Data access is limited during the interview; focus on decision quality, alignment, and guardrails. Key KPI definitions (to anchor discussion) - Margin per search (MPS) = (Gross booking revenue − variable cost − marketing cost) / number of searches - Bookings per user (BPU) = bookings / active users in period - Attributed conversions (ACV) = conversions attributed to a given channel/model in period (model-dependent) A. Upfront alignment: decision, criteria, and acceptance thresholds 1) Prewire with a 1‑page written brief (circulate 24 hours ahead) - Decision statement: “Which primary KPI should govern the next 4 weeks of optimization for Search & Marketing experiments, with guardrails to protect long‑term health?” - Objective function: Maximize near-term unit economics without eroding user growth or overfitting attribution. - Options to evaluate: MPS, BPU, ACV, layered metric (primary + guardrails), or a hierarchical decision rule. - Constraints: 48 hours, limited data pulls, existing attribution model, no new instrumentation. - Roles/approval (DACI/RACI): D = GM/Director; A = VP Product; C = Product/Marketing; I = Finance/Analytics. - Success criteria (examples): - Primary KPI improves by ≥ X% (e.g., +2%) in A/B tests or backtests, with guardrails not breached. - Guardrail thresholds: - BPU decline ≤ 1% (user experience proxy) - ACV decline ≤ 1% per priority channel (demand proxy) - Refund rate/complaints unchanged (qualitative UX) - Decision timeline: 48 hours to framework + provisional recommendation; 2 weeks to validate in test. 2) Acceptance thresholds and tie‑breakers - Set ex‑ante: choose the KPI that best aligns to P&L for the next month, unless it causes a red‑flag breach on growth guardrails; if tie, pick the more causally reliable metric. - Define red/yellow/green: - Red: guardrail breach beyond thresholds → do not ship. - Yellow: within threshold but negative → escalate and timebox a follow‑up. - Green: thresholds cleared → proceed. 3) Meeting agenda to validate scope (30 minutes) - Confirm decision, objective, options, constraints, thresholds, and who decides. - Capture dissent and log in a decision doc. B. Managing ambiguity during interviews 1) Active summarization - Start each answer with a crisp paraphrase: “I hear the question as X. The goal is Y. I’ll address by A → B → C.” 2) Targeted clarifiers (examples) - Unit of analysis: user, session, search, or booking? - Time horizon: optimize weekly, monthly, or LTV? - Cost coverage: does MPS include CAC and variable costs? Any fixed cost allocation? - Attribution model: last‑click vs data‑driven? Lookback window? - Data quality: known seasonality, suppression, bots? 3) Document assumptions in real time - “Assuming MPS includes marketing cost; if not, I’ll show sensitivity.” - Maintain an “assumptions and implications” table; revisit at the end. 4) Timebox ambiguity - If unresolved in 2–3 minutes, propose two paths and continue: “If A holds we choose X; if B holds we choose Y.” C. Narrative structure and communicating trade‑offs 1) Use SCQA - Situation: Marketplace needs a KPI to steer short‑term optimization. - Complication: Stakeholders push different KPIs; each can mislead if used alone. - Question: Which KPI should be primary now, and what guardrails ensure we don’t regress on growth or misattribute impact? - Answer: Recommend a layered metric: Primary = Margin per Search; Guardrails = Bookings per User and Attributed Conversions, with pre‑set thresholds and a validation plan. 2) Show option analysis (succinct pros/cons) - MPS - Pros: Closest to unit economics; discourages low‑margin traffic. - Cons: Sensitive to cost allocation; may penalize early‑funnel growth. - BPU - Pros: Captures user value and UX; less cost‑model noise. - Cons: Ignores unit economics; can over‑reward low‑value bookings. - ACV - Pros: Marketing accountability; channel optimization. - Cons: Attribution bias; not a business outcome. - Layered/hierarchical approach - Pros: Balances P&L with growth; clear guardrails. - Cons: Requires governance and test discipline. 3) Guardrails and decision rule (example numbers) - Primary: Increase MPS by ≥ 2% (stat‑sig if testing) with: - BPU change ≥ −1% - ACV change ≥ −1% in top channels - Refund rate change ≤ +0.2 pp - If MPS +2% but BPU −3% → fail (risk to user health). - If MPS +1.8% (close) and BPU +0.5% → evaluate business lift (expected margin dollars) and decide via tie‑breaker. 4) Validation plan - Short‑run A/B test or backtest: - Power for primary KPI; monitor guardrails with sequential monitoring or pre‑registered thresholds. - Sensitivity analysis: MPS with/without certain costs; ACV under different attribution windows. D. Handling conflicting post‑presentation feedback 1) Listen, reflect, categorize - Bucket into factual (data), preference (metric philosophy), and policy (strategy) differences. - Reflect back: “I’m hearing concern that BPU is underweighted relative to MPS in the near term.” 2) Anchor to pre‑agreed criteria - “Per our acceptance thresholds, we optimize P&L with growth guardrails. Your suggestion to elevate BPU implies a strategy shift; shall we revisit the objective or treat this as a guardrail change?” 3) Negotiate scope/next steps - Offer testable increments: “We can run a 2‑cell test: MPS‑primary vs BPU‑primary with common guardrails; decide in 2 weeks.” - Log decisions and dissent in a decision doc; confirm owners and deadlines. 4) Disagree and commit - If leadership chooses a different path, summarize risks, add monitoring triggers, and commit: “We’ll implement, monitor BPU/MPS weekly, and auto‑revert if thresholds breach.” E. Professional pushback on constraints with principled alternatives 1) Timeline (48 hours vs depth) - Use the scope–time–quality trade‑off: “With 48 hours, we can deliver the framework, metric definitions, and a backtest on 1–2 cohorts. For causal validation across segments, we’d need an extra week or add an analyst. Which lever can we adjust?” - Offer a phased plan: - T+48h: Framework + provisional rec + guardrails - T+2 weeks: Experiment readout - T+4 weeks: KPI governance proposal 2) Relocation/working model - Interests not positions: “I value collaboration and family constraints limit relocation. Could we explore hybrid (X days/quarter on‑site) with defined on‑site rituals for planning and post‑mortems?” - Propose measurable alternatives: on‑site cadence, travel budget, core hours. 3) Compensation - Principle: market data and impact scope. “Given scope (owning KPI governance and experimentation), market data suggests range X–Y. If base is fixed, can we adjust sign‑on, equity refresh cadence, or a 6‑month performance review trigger?” Small numerical illustration (for clarity) - Baseline: MPS = $1.00/search; BPU = 0.050; ACV = 10,000/week - Variant A (MPS‑primary): MPS = $1.03 (+3%); BPU = 0.049 (−2%); ACV = 9,950 (−0.5%) - Guardrails: BPU −2% exceeds −1% threshold → do not ship; iterate to reduce UX friction. - Variant B (BPU‑primary): MPS = $0.99 (−1%); BPU = 0.052 (+4%); ACV = 10,050 (+0.5%) - Decision: violates P&L objective; acceptable only if strategy prioritizes growth. Otherwise, fail. - Iterated Variant C: MPS = $1.022 (+2.2%); BPU = 0.0505 (+1%); ACV = 10,010 (+0.1%) → ship. Common pitfalls and guardrails - Pitfall: Attributed conversions can rise due to model bias. Guardrail: report incrementality (geo‑experiment or PSA holdout) when feasible. - Pitfall: Optimizing MPS can starve upper funnel. Guardrail: cap bids and monitor new‑to‑file share. - Pitfall: KPI drift. Guardrail: quarterly KPI review with Finance/Product; version your definitions. Deliverables checklist for the onsite - 1‑page prewire: decision, options, criteria, thresholds, roles, timeline. - KPI spec sheet: definitions, formulas, edge cases, data sources. - Option matrix: pros/cons, risks, when to use. - Decision rule graphic: primary vs guardrails with thresholds. - Validation plan: experiment/backtest design, power, timelines. - Decision log template: feedback, owner, due date, status. Executive summary you can say in 60 seconds - We’ll use a layered KPI: primary = margin per search to align with unit economics. We protect growth with guardrails on bookings per user and attributed conversions, with pre‑set thresholds and revert triggers. We’ll validate via a short A/B or backtest, publish a decision log, and revisit quarterly. If we must move faster, we narrow scope or add resources; otherwise we phase delivery. This balances P&L accountability with user growth and reduces attribution risk.