Manage promotions and project portfolio tradeoffs

# Overview Below is an end-to-end operating plan that (1) defines a Staff promotion philosophy with evidence thresholds, (2) builds a next-quarter portfolio that maximizes expected value and creates Staff-scope, (3) shows how to decline low-EV high-visibility work while protecting the team, and (4) installs mechanisms to reduce bias and ensure equitable access to scope across locations/time zones. --- ## (a) Promotion Philosophy and Evidence Thresholds Principles - Promotion-earning impact is repeatable, organization-level, and achieved in ambiguous environments. - Staff DS is a force-multiplier: sets strategy, shapes roadmaps, elevates decision quality, and raises the bar for others. - Evidence > narrative. Multiple independent artifacts and cross-functional signals over time. Staff Expectations (4 pillars) and Evidence Thresholds 1) Business Impact at Org Level - What: Measurable, durable impact on north-star and/or P0 business objectives; not just feature-level wins. - Threshold: Two or more multi-quarter outcomes with clear causal attribution (e.g., multiple product lines, or company-wide measurement uplift). Each outcome has quantified effect sizes and decision logs. - Evidence: Experiment/causal analyses with MDE/power documented; counterfactuals considered; metric move consistency across segments; postmortems. 2) Scope and Ambiguity Handling - What: Problem-finding and solution definition across teams; resolves ambiguous, cross-functional problems. - Threshold: Led ≥2 cross-org initiatives from problem framing to steady state; established standards or frameworks adopted by ≥2 partner teams. - Evidence: PRDs with SDRs, design docs, cross-functional sign-offs, adoption metrics. 3) Technical Judgment and Decision Quality - What: High-quality modeling, measurement, and experimentation decisions under constraints; sets technical bar. - Threshold: Track record of correct calls on trade-offs (e.g., causal vs. correlational methods, power, metric design) with observable downstream wins; authored/maintained team standards. - Evidence: Design reviews, ADRs (architecture/analysis decision records), reproducible notebooks/pipelines, incident-prevention via guardrails. 4) Org Leadership and Multiplication - What: Mentors, unblocks teams, and institutionalizes better ways of working. - Threshold: Demonstrated uplift of others (mentees promoted or independently delivering), introduced practices that stick (e.g., SDR templates), and improved hiring/calibration. - Evidence: Mentorship logs, peer feedback, hiring loop outcomes, documentation adoption rates. Rubric (used in calibration) - Scale: 0 = not demonstrated, 1 = emerging, 2 = solid senior, 3 = Staff-level, 4 = exceeds Staff. - Score each pillar with evidence links; promotion readiness requires no pillar below 3 and total pattern of 3s/4s across ≥2 cycles. Artifacts Required for Case - Portfolio doc mapping initiatives to north-star, with expected value (EV) calculations. - For each initiative: PRD with SDRs, experiment/causal design, decision log, and postmortem. - Sponsorship/mentorship records and adoption metrics for standards. Calibration Cadence - Quarterly talent calibration with cross-team panel; evidence-based review against rubric; normalize expectations across locations/time zones. --- ## (b) Next-Quarter Portfolio: Pursue/Pause/Kill and Staffing Decision Framework - Expected Value (EV): EV = Impact × Probability of Success. Rank by EV per unit effort (ROI). - Alternative: RICE = (Reach × Impact × Confidence) / Effort. - Guardrails: Must align to top-level goals; hit minimum power/MDE for experiments; have SDRs before build. - Capacity: 10-person team, assume 8 ICs available for projects, ~10 person-weeks per IC per quarter → ~80 person-weeks. Allocate 60% to high-ROI bets, 20% to platform/measurement, 20% to exploration/EA (early analysis). Candidate Initiatives (illustrative) 1) Causal Measurement Standardization (cross-product) - Goal: Standard metrics/experimentation guardrails to cut decision latency and reduce false positives. - Staff-scope: Cross-org standards; rollout across 3 product areas. - Effort: 20 pw; Impact: Enable +0.2–0.5 pp uplift across multiple surfaces; Confidence: 0.7. 2) Notifications Ranking Uplift via Causal ML - Goal: Replace proxy CTR metric with long-term retention-aware objective; run bandits/stratified experiments. - Staff-scope: Multi-team alignment, advanced methodology, metric redefinition. - Effort: 24 pw; Impact: +0.3% weekly active days; Confidence: 0.6. 3) Data Reliability and Observability (P0 metrics) - Goal: Data contracts, anomaly detection, backfills automation; reduce incidents and unlock faster iteration. - Staff-scope: Platformized solution adopted by ≥4 teams. - Effort: 16 pw; Impact: Reduce incident time by 50%, +10% experimentation throughput; Confidence: 0.8. 4) Creator Monetization Cohort Deep-Dive - Goal: Find levers for top-creator growth; exploratory. - Effort: 10 pw; Impact: Uncertain; Confidence: 0.3 (exploration). 5) Vanity Dashboard Refresh - Goal: UI improvements for existing dashboards. - Effort: 6 pw; Impact: Low on outcomes; Confidence: 0.9. 6) High-Visibility “Moment” Feature Analysis (exec interest) - Goal: Quick win for a seasonal feature; TAM limited; weak historical ROI. - Effort: 12 pw; Impact: Small, decays fast; Confidence: 0.4. Ranking (example using simplified ROI = (Impact × Confidence) / Effort) - 1) Measurement Standardization: High ROI and unlocks others. - 2) Data Reliability: High ROI, platform benefit. - 3) Notifications Uplift: Medium-high ROI, direct metric move. - 4) Creator Deep-Dive: Exploration bucket (keep small). - 5) Moment Feature: Low ROI; 6) Vanity Dashboard: Lowest ROI. Decision - Pursue: (1), (2), (3). Staff-scope built in via cross-org alignment, standards, metric redesign. - Pause: (4) keep as 5 pw discovery with clear kill gates; (5) defer unless bundled with adoption OKRs; (6) kill unless a tiny pilot meets SDRs. Staffing and Scope-Shaping - Lead A (senior IC): DRI for (1); co-sponsor in adjacent teams; success = standards adopted by ≥3 teams; artifacts = RFC, migration plan, training. - Lead B (senior IC): DRI for (2); partners with Eng/PM/Applied Research; success = retention-aware offline/online metric parity and ≥0.2% lift in holdout. - Lead C (senior IC): DRI for (3); success = on-call incident reduction 50%, time-to-detect <15 min, data contracts for 10 critical tables. - Remaining ICs split: 10 pw exploration for (4) with clear SDRs; 6 pw reserved for urgent EA and hygiene. Gates and Validation - PRD+SDR required before build. Example SDRs: target effect size, MDE/power calcs, adoption targets, guardrails (no decline in core engagement by >0.05 pp), and decision owners. - Mid-quarter review: if SDRs not met, reallocate. --- ## (c) Declining a High-Visibility Low-EV Project Intake and Evaluation - Require a 1-page PRD with SDRs within 48 hours: problem statement, TAM, historical benchmarks, expected lift, costs, opportunity cost, and decision deadline. - Quantify EV quickly: EV = proposed metric delta × baseline × probability of success. Compare ROI to top items. - Example: Feature expected +0.03% weekly activity, p=0.4, Effort=12 pw → ROI far below top projects. Exec Communication (concise, data-forward) - Narrative: “We evaluated X with the same bar we use for P0 goals. Its expected value is ~4–6× lower than our top three initiatives, and it carries higher downside risk (fragmentation, distraction). To preserve speed on P0s, we propose a low-cost signal check and revisit when trigger conditions are met.” - Offer alternatives: - Run a 1-week, <2 pw pilot with clear SDRs (e.g., MDE feasible, no guardrail breach). - Instrumentation-only this quarter to keep optionality; re-evaluate after we ship Notifications and Measurement. - Define trigger metrics (e.g., if segment adoption >X%, or partner team unlock occurs) to auto-reconsider. Protecting the Team - Intake policy: All new work goes through triage with ROI table and opportunity cost side-by-side. - Capacity guardrail: Keep a 10–15% buffer only for P0 incidents; no ad-hoc pulls without deprioritizing something explicitly. - Decision log: Publish decline rationale, SDRs for revisit, and owner. Socialize in staff meeting and an exec Slack note. Template: Exec Note (100–150 words) - Context → EV/ROI comparison → Risks/guardrails → Proposed low-cost alternative → Revisit date/trigger. --- ## (d) Bias Mitigation and Equitable Access to Scope Risks - Proximity/time-zone bias; sponsorship bias (same people get stretch work); unequal credit for invisible “glue work.” Mechanisms (concrete and auditable) 1) Opportunity Board and Staffing Rubric - Public board of scoped initiatives with role expectations, SDRs, and required competencies. - Rubric aligns skills to opportunities; candidates self-nominate asynchronously. - Staffing decision recorded with rationale; reviewed in calibration. 2) Sponsorship Rotation - Quarterly rotation among senior leaders to sponsor high-scope initiatives; each sponsor accountable for exposure, feedback, and unblock. - Track sponsor-mentee pairs across locations; ensure each senior IC gets ≥1 Staff-scope opportunity per 2 quarters. 3) Calibration and Evidence-First Reviews - Quarterly calibration across sites; same rubric and artifacts; blind pre-reads of impact where feasible (remove names in first pass). - Include adoption metrics and standards work in the promotion packet; assign explicit credit for glue work. 4) Async-First, Time-Zone Friendly Practices - Written PRDs/RFCs with 48–72 hours for async comments; rotate meeting times; record and summarize decisions. - Co-lead patterns across sites (e.g., A leads design, B leads rollout) to share scope and visibility. 5) Metrics and Audits - Track scope distribution (share of Staff-scope work by location/gender/URM), meeting speaking time, doc authorship, and sponsorship coverage. - Quarterly audit: if skew >20% from team composition, adjust assignments and sponsors. --- ## Practical Tools and Templates PRD with SDRs (1–2 pages) - Objective and Link to North-Star - Users/Segments and TAM - Success Metrics: primary, secondary, guardrails; target deltas; MDE/power calc and sample size - Design/Method: experiment or causal approach; assumptions - Risks/Dependencies; Data/Privacy constraints - Effort Estimate (pw) and Timeline; DRI and XFN partners - SDRs: adoption criteria, effect size thresholds, guardrails, decision date and owners Lightweight Scoring - EV = Impact × Probability of Success - ROI = EV / Effort (person-weeks) - RICE = (Reach × Impact × Confidence) / Effort Small Numeric Example - Project A: EV = 0.5% lift × 0.6 = 0.3; Effort = 20 pw → ROI = 0.015 per pw - Project B: EV = 0.3% × 0.8 = 0.24; Effort = 12 pw → ROI = 0.020 per pw (rank higher) Cadences - Weekly: Triage and ROI review; unblock list. - Biweekly: Project reviews against SDRs; go/no-go gates. - Quarterly: Portfolio reset; calibration and scope audit. Pitfalls and Guardrails - Promotion-driven projects that don’t map to goals: require explicit link to OKRs and SDRs. - Over-indexing on one “big win”: require repeated impact and cross-org adoption. - Ignoring platform/measurement: reserve capacity for enablers; they create Staff-scope and compound ROI. Outcome - Clear, fair bar for Staff promotion; a high-ROI, Staff-scope-rich portfolio; principled declines of low-EV work; and mechanisms that make access to scope equitable across locations and time zones.