- The Analytics Ladder
- Posts
- The Courage to Be Wrong: How Strategic Vulnerability Gets You Promoted
The Courage to Be Wrong: How Strategic Vulnerability Gets You Promoted
The no-fluff playbook for turning analytics pros into strategic leaders. Every Wednesday.
Why admitting uncertainty is the one leadership skill AI can’t copy.
You've been there. Standing in front of executives, armed with perfect data and bulletproof analysis, only to watch your recommendations get politely ignored.
Again.
Meanwhile, that smooth talking consultant who barely knows Excel just got the green light for their "strategic initiative." What's the difference? They understand something you don't—yet.
With ChatGPT writing SQL and AutoML building models, your technical skills are becoming table stakes.
But here's what AI can't do—it can't read the room when a CFO's budget concerns are really about job security. It can't sense when a product manager's pushback on your analysis stems from political pressure from their boss.
These human dynamics? That's your moat.
Leadership Leverage
Here's the counterintuitive truth: showing you don't have all the answers actually makes stakeholders trust you more.
Dare to Lead by Brené Brown reveals why vulnerability isn't weakness—it's your secret weapon for building the trust that gets you promoted while AI handles the technical grunt work.
Playbook
Ever feel like your data insights are undervalued by stakeholders who just don't get it? You spend weeks perfecting your analysis, only to have it dismissed in a 10-minute meeting. It's soul-crushing when your hard work gets sidelined, leading to stalled projects and those 2 AM doubts about whether you'll ever break into leadership.
This matters because influence over non-technical leaders is your ticket to promotion and staying relevant in an AI-driven world.
Let's fix it with a proven approach from Dare to Lead—using vulnerability and empathy to build unshakeable trust.
Picture Sarah, a senior analyst at a healthcare startup, learning this the hard way. She spent three weeks building a perfect patient retention model, presented it with technical precision, and watched the CMO's eyes glaze over. The project dies in committee. Six months later, she tries again—same data, different approach. This time, she starts with: "I'm seeing something in our patient data that could save us $2M in acquisition costs, but I need to understand your biggest retention challenges first." Same analysis, different framing. The CMO not only approves the project but asks Sarah to present to the board.
The Six Trust-Building Levers for Analytics Leaders
Lever 1: Strategic Vulnerability
Here's what most analytics pros get wrong about vulnerability—they think it means admitting failure. Wrong. It means admitting uncertainty while positioning yourself as the person who can navigate it.
A data scientist at a Fortune 500 retail company tells her VP: "Our churn model is showing conflicting signals, and I need your input on which customer segments matter most to the business strategy." Instead of losing credibility, she gained a seat at the strategy table. Why? Because she framed her uncertainty as a collaboration opportunity, not a technical limitation.
Inside-Org Example: During a quarterly review, admit that your predictive model has a 15% uncertainty range, then ask: "Given our Q4 priorities, should I optimise for precision or speed of insights?"
Translate It to the Org Chart: You become the analyst who thinks strategically, not just technically—exactly what executives want in their next promotion decision.
Lever 2: Stop Talking About Data. Start Talking About What Keeps Them Up at Night
When a business leader says "the data doesn't support this," they're rarely questioning your analysis. They're usually saying one of three things: 1) I don't understand how this helps me hit my goals, 2) I'm worried about the political implications, or 3) I need cover to make a decision I already want to make. Your job isn't to defend the data—it's to decode what they really need.
A healthcare analytics manager noticed her hospital exec kept pushing back on cost-reduction insights. Instead of showing more charts, she asked: "What would happen to patient satisfaction if we implemented these changes?" Turns out, the exec's real concern was maintaining care quality during budget cuts. Once she reframed her analysis around "cost-effective care optimization," the project got full support.
Inside-Org Example: Before your next presentation, spend 10 minutes researching what KPIs your audience is measured on. Lead with how your insights impact their success metrics.
Translate It to the Org Chart: You become the person who "gets the business," not just the numbers—the #1 trait executives look for in leadership candidates.
Lever 3: The Strategic Uncertainty Email
Most analytics pros avoid admitting when they need business context. Leaders embrace it as a collaboration opportunity.
Here's the template that's working: "I'm analyzing [specific data/project], and the results could go in two directions depending on [business priority]. I'd value 10 minutes of your time to ensure I'm solving the right problem. Given [current business context], should I prioritize [Option A] or [Option B]?"
Imagine a fintech analyst used this approach when building a fraud detection model. Instead of guessing at thresholds, she asked the risk team: "Should I optimize for catching more fraud (higher false positives) or reducing customer friction (some fraud slips through)?" That 10-minute conversation leads to a model that actually got implemented—and maybe a promotion to Senior Analyst??
Inside-Org Example: Identify one current project where you're genuinely uncertain about business priorities. Collaborate. ASk. Send that email this week.
Translate It to the Org Chart: You demonstrate strategic thinking and stakeholder management—two core leadership competencies.
Lever 4: Micro-Promises That Build Macro-Trust
Trust isn't built in grand gestures. It's built in small, consistent actions that prove reliability.
How ab out this: A retail analytics team leader makes this work by committing to "48-hour insights"—whenever a business unit had an urgent question, she provides initial findings within two days, even if the full analysis takes longer. This simple promise transforms her from "the data person we wait for" to "the person who always has our back."
Inside-Org Example: Pick one small commitment you can consistently deliver on—weekly dashboard updates, same-day responses to urgent requests, or 24-hour turnaround on data pulls.
Translate It to the Org Chart: Reliability is the foundation of executive presence. You become someone leadership can count on.
Lever 5: Expectation Clarity That Prevents Project Death
Most analytics projects fail not because of bad data, but because of misaligned expectations. Leaders get ahead of this.
When leading a customer segmentation project for a marketing team, spell out exactly what you need: "I'll deliver three customer segments with targeting recommendations by [date]. To make this actionable, I need your input on campaign budget constraints and channel preferences by [date]." Then add: "If priorities shift, let me know 48 hours before the deadline so we can adjust scope."
Inside-Org Example: For your next project kickoff, create a one-page "project charter" that outlines deliverables, timelines, and what you need from stakeholders.
Translate It to the Org Chart: Project management skills separate individual contributors from leaders. You show you can drive outcomes, not just deliver outputs.
Lever 6: The Strategic Confrontation
When stakeholders dispute your findings, most analysts get defensive. Leaders get curious.
A sales analytics manager at ACME faces pushback when her churn analysis contradicted the sales team's intuition. Instead of defending her methodology, she says: "Help me understand what you're seeing in the field that might not show up in the data." This leads to discovering a data quality issue that, once fixed, aligns the analysis with ground truth—and earns her respect from the sales team.
Inside-Org Example: Next time someone challenges your analysis, respond with: "That's interesting—what are you seeing that might explain this difference?" Then actually listen. Work together. Listen.
Translate It to the Org Chart: Conflict resolution and intellectual humility are executive-level skills. You show you can handle disagreement without ego.
What's Really Happening Behind the Scenes
This approach works because it addresses the real reason analytics pros struggle with influence: you're solving technical problems while stakeholders have business problems. When you bridge that gap through vulnerability and empathy, you become indispensable.
How do I know it works? Ive lived it. Ive built my career on it.
I have countless times approached stakeholders from a position of uncertainty, with genuine will to reach out and collaborate. To understand. To listen.
To adapt.
I have been wrong many many times - especially at the start of a piece of work. The initial hypothesis falls flat on its face and we have a moment where we need to eat humble pie and re-adjust. (An initial hypotheses is meant to be tested, not defended to the death).
This is normal. It is expected.
The biggest shift in my own journey from analyst to leader wasn’t getting better at being right—it was getting better at being wrong, early. Its almost a superpower.
The six levers teaches you some simple techniques on how to show leadership quality in these sort of situations.
Promotion Fast-Track: The "Strategic Uncertainty" Sprint (20 Minutes)
0-5 Minutes: Identify one current project where you're genuinely uncertain about business priorities or stakeholder needs
5-10 Minutes: Draft an email using this template: "I'm analyzing [specific project], and the results could go in two directions depending on [business priority]. I'd value 10 minutes of your time to ensure I'm solving the right problem."
10-15 Minutes: Add one specific question that shows you understand their world: "Given [current constraint/goal], should I prioritize [Option A] or [Option B]?"
15-20 Minutes: Send it and note their response time—faster replies indicate higher engagement and trust
Outcome: You've initiated a trust-building moment that positions you as a strategic partner, not just a data provider.
Your Next Move
Which lever will you test this week, and with which stakeholder? Reply with your plan—I'll feature anonymised success stories next issue. Share your experiment or win on social with #WednesdayLadderWin for a chance to be spotlighted.
The best part? You don't need to master all six levers at once. Pick one, try it this week, and watch how differently people respond when you lead with curiosity instead of certainty.
Parting Wisdom
"Courage starts with showing up and letting ourselves be seen."
– Brené Brown
But here's what Brené doesn't tell you: in analytics, showing up means admitting when you need business context to make your technical work matter.
That's not weakness—that's leadership.
Micro-Tool Drop
The Strategic Uncertainty Email Template
This PDF gives you five proven email templates for turning analytical uncertainty into collaboration opportunities. Each template is designed for different scenarios—project kickoffs, stakeholder pushback, scope changes, and urgent requests. Download it now to transform your next stakeholder interaction from defensive to strategic.
Remember: Your technical skills got you here. Your leadership skills will get you there.
Best,
Tom.
PS.. Forward this to one analytics teammate who worries AI is eating their lunch — and help them climb the Ladder.
Not a subscriber yet? Join us to get your weekly edition.
Disclaimer: Some of the articles and excerpts referenced in this issue may be copyrighted material. They are included here strictly for review, commentary and educational purposes. We believe this constitutes fair use (or “fair dealing” in some jurisdictions) under applicable copyright laws. If you wish to use any copyrighted material from this newsletter for purposes beyond your personal use, please obtain permission from the copyright owner.
The information in this newsletter is provided for general educational purposes only. It does not constitute professional, financial, or legal advice. You use this material entirely at your own risk. No guarantees, warranties, or representations are made about accuracy, completeness, or fitness for purpose. Always observe all laws, statutory obligations, and regulatory requirements in your jurisdiction. Neither the author nor EchelonIQ Pty Ltd accepts any liability for loss, damage, or consequences arising from reliance on this content.
Visit our website to see who we are, what we do. | |
Our blog covering the big issues in deploying analytics at scale in enterprises. |