Leadership Priorities - Quick Reference
Keep this open during meetings to stay aligned
The One Thing Leadership Wants
“You’re a thought leader. Tell us the story with data. Don’t just be an inbox.”
Translation: Proactively drive decisions, don’t reactively build reports.
Top 5 Priorities (Jan 2026)
1. Tell the Affiliate Win Story 🏆
- Why: They’re at conferences RIGHT NOW recruiting partners
- What: 15% approval rate lift, $500K+ overpayment stopped, affiliates outperform all channels
- Deliverable: 5-slide deck they can share externally
2. Support 4 Experiments/Month
- Why: How they’ll hit 2x revenue growth
- What: Help Ryan test pricing, landing pages, intake flows
- Deliverable: Intake form CVR analysis + testing framework
3. Enable Self-Service (Stop Being an Inbox)
- Why: Can’t scale if team builds every report
- What: Train teams to use Mixpanel themselves
- Deliverable: Training materials + request triage process
4. Build Ecommerce Best Practices (Not Bask Limitations)
- Why: EdenOS is foundation for unified healthcare platform
- What: Shopify-level data standards
- Deliverable: Reference architecture + gap analysis
5. Prove Channel ROI (LTV:CAC)
- Why: Need to shift budget to best-performing channels
- What: Payback periods, retention curves, affiliate vs. Meta comparison
- Deliverable: Dashboard showing where to invest
Business Goals (Context)
| Goal | Data Implication |
|---|---|
| 2x revenue growth | Need strong attribution + experimentation |
| 3 new channels | Repeatable onboarding playbook |
| Marketing team scale (3 → 10+) | Self-service becomes critical |
| Product relaunches (not new launches) | Optimization > innovation |
| Pharmacy integration | Unified patient journey data |
| Telehealth + Health Clubs | Cross-business reporting |
What to STOP Doing
| ❌ STOP | ✅ START |
|---|---|
| Being an inbox for ad hoc requests | Teaching teams to fish |
| Building reports no one uses | Understanding stakeholder workflows first |
| Proposing measurement-heavy roadmaps | Leading with insights + recommendations |
| Product-specific deep dives | Building repeatable systems |
| Over-automating dashboards | Building in manual accountability |
Meeting Quick Checks
Before Any Stakeholder Meeting:
- What’s their #1 goal this quarter?
- How does this request tie to that goal?
- Can they do this themselves in Mixpanel? (If yes, teach them)
- Will this lead to a decision? (If no, don’t build it)
Before ELT Calls:
- Lead with wins, not roadmaps
- Show $ impact (saved or earned)
- Connect to 2x growth goal
- Ask for confirmation on priorities
When Someone Asks for a Report:
- “What decision does this inform?”
- “Have you tried building this in Mixpanel?”
- “When do you need this by?”
- “If I build this, will you use it?”
Red Flags (We’re Off Track If…)
- ❌ Spending >20% time on ad hoc requests
- ❌ Building dashboards stakeholders don’t use (Monday.com problem)
- ❌ Missing ELT commitments
- ❌ Getting surprised by priorities (not talking to stakeholders enough)
- ❌ Proposing analyses without tying to 2x growth goal
Key Phrases to Use
When Pushing Back on Low-Value Work:
“I want to make sure we’re focused on what moves the needle. How does this tie to your Q1 goals?”
When Teaching Self-Service:
“Let me show you how to build this yourself in Mixpanel. It’ll be faster next time.”
When Presenting to Leadership:
“Here’s the business impact: We saved $X / increased conversion Y% / proved affiliates outperform by Z%.”
When Clarifying Priorities:
“Based on our last call, I’ve prioritized [X, Y, Z]. Does this align with where you want us focused?”
Stakeholder Cheat Sheet
| Person | Role | What They Care About | How to Help Them |
|---|---|---|---|
| Mitesh | Marketing GM | 2x growth, channel ROI, team efficiency | LTV:CAC models, self-service enablement |
| Ryan | Experimentation Lead | 4 tests/month, clear measurement | Intake CVR analysis, testing framework |
| Judd | Lifecycle Marketing | Win-back campaigns, reactivation | Segment definitions, cohort analysis |
| Brad | Ops Lead | SLA tracking, operational metrics | Data reconciliation, trust building |
| Surf | EdenOS Lead | Ecommerce data model, scalability | Best practices, requirements clarity |
| Zoran | Martech Lead | Attribution, affiliate tracking, automation | Channel performance, cost upload verification |
ELT Call Preparation Template
1. Lead with Wins (60 seconds)
- Affiliate: “$500K saved, 15% approval rate increase”
- Experimentation: “Intake CVR analysis shows 4% improvement opportunity”
- Self-Service: “5 new Mixpanel users, 40% drop in ad hoc requests”
2. Show What’s Next (30 seconds)
- “Next 2 weeks: LTV:CAC model, 3 experiments launching, training 5 more users”
3. Ask for Alignment (30 seconds)
- “Does this align with where you want us focused?”
- “What should we prioritize next?”
4. Have Backup Slides Ready (Don’t Present Unless Asked)
- EdenOS progress
- Detailed roadmap
- Technical deep dives
Decision Framework
Should We Do This Work?
┌─────────────────────────────────────────────┐
│ Does it tie to 2x growth goal? │
│ ├─ No → Deprioritize │
│ └─ Yes ↓ │
│ │
│ Does it require a custom build? │
│ ├─ No → Teach them to self-serve │
│ └─ Yes ↓ │
│ │
│ Will it lead to a decision? │
│ ├─ No → Don't build it │
│ └─ Yes ↓ │
│ │
│ Can we build a system vs. one-off? │
│ ├─ No → Push back or simplify │
│ └─ Yes → Prioritize it │
└─────────────────────────────────────────────┘
Metrics to Track Weekly
Team Effectiveness
- % time on ad hoc requests (Target: <20%)
-
self-service Mixpanel users (Target: 10+)
-
experiments supported (Target: 4/month)
Business Impact
- Affiliate $ saved + earned (quantify monthly)
- Experiment win rate (% that improve metrics)
- LTV:CAC improvement (by channel)
Stakeholder Trust
- Are they using our dashboards? (vs. building their own)
- Do they invite us to strategic meetings? (vs. just execution)
- Do they ask for insights? (vs. reports)
Common Traps to Avoid
| Trap | Why It’s Bad | How to Avoid |
|---|---|---|
| ”They asked for it, so I built it” | Becomes an inbox | Ask: “What decision does this inform?" |
| "I’ll automate everything” | Removes accountability | Build in manual check-ins |
| ”Let me show you the full roadmap” | Leadership doesn’t care about plans | Lead with wins, not roadmaps |
| ”This analysis is interesting” | Interesting ≠ actionable | Tie every analysis to a decision |
| ”I don’t want to push back” | Low-value work crowds out high-impact work | Use decision framework above |
Emergency Reset Questions
If you’re feeling overwhelmed or off-track, ask yourself:
-
Am I telling stories or building reports?
- Reports = low value, Stories = high value
-
Am I teaching teams to fish or catching fish for them?
- Catching fish = doesn’t scale, Teaching = scales
-
Can I tie my current work to the 2x growth goal?
- If no, why am I doing it?
-
Would leadership share this work externally?
- If no, it’s probably not strategic enough
-
Am I building systems or solving one-off problems?
- One-offs = patchwork, Systems = mature
Print this out and keep it visible during meetings Update after each ELT call based on new feedback