Will AI replace PMs? Why do most projects really fail? And how do you win over executives who’ve seen it all before? Rahul has the answers. After 15 years of transformation leadership across finance, energy, health, government, and retail, he brings unfiltered lessons, practical playbooks, and hard truths every practitioner needs to hear.
Q1. 15 years, multiple continents, six different industries – you must have some interesting stories. When people ask ‘What do you do?’ at a dinner party, how do you explain transformation leadership in a way that gets people excited rather than confused?
At a dinner party, I say: I upgrade how organizations work, the way your phone gets a new OS. Same contacts and info, but new superpowers.
But the real excitement is what it feels like for people. A planner who used to wait days for a report now sees live data in the meeting and decides on the spot. A customer journey that crawled across five handoffs is done before the coffee cools. That’s transformation, less theater, more “wow, that was fast.”
How we get there comes down to three habits. First, outcomes over output: we stop celebrating “project delivered” and start measuring “problem solved,” fewer escalations, faster cycle times, happier customers. Second, build with people, not for them: execs, frontline teams, and tech sit at the same table. Co-design beats “ta-da!” launches every time. Third, prove small, scale smart: pilot, measure, iterate, then go wide. Evidence buys trust and budget.
Across mining, energy, finance, government, retail, and education, excitement isn’t a slide, it’s momentum. Once teams feel an hour replace a week, nobody wants to go back. My job is to make those wins inevitable, then make them repeatable.
Q2. As an Author and Instructor, what’s one PM truth every practitioner should know, and what would you tell your younger PM self to stop worrying about?
The truth: projects don’t fail because of Gantt charts, they fail because of narratives. If the problem statement, success metrics, and “why now” aren’t crystal clear, even the best plan turns into theater. The strongest PMs are part storyteller, part economist: translate strategy into two or three measurable outcomes, show the leading indicators weekly, and keep the story honest with evidence.
What I’d stop worrying about sooner: control. Early on, I tried to own every dependency, answer every question, and protect every date. It’s unsustainable and it slows teams down. What works is clarity over control. Set non-negotiables such as outcomes, guardrails, and decision cadence. Make work and risk visible through a single source of truth, weekly demos and insights, and red flags raised early. Share leadership by letting SMEs own solutions while you own the learning loop.
When I shifted from “how do I keep this on track?” to “how do we learn faster than the risk grows?”, delivery got lighter and results got bigger. Plans still matter, but feedback loops, value language, and stakeholder rituals matter more. That’s the craft I teach: less orchestration, more acceleration.
Q3. Is AI going to replace PMs? What’s the brutally honest answer, and what’s the one stakeholder conversation about AI every PM must master?
The honest answer: AI won’t replace great PMs, but it will replace PM tasks such as status synthesis, risk scanning, dependency mapping, schedule what-ifs, and even drafting comms. If your value is moving tickets and polishing decks, you’ll feel automated. If your value is framing problems, negotiating trade-offs, shaping outcomes, and building trust, AI becomes a force multiplier.
I tell teams: AI is the intern who never sleeps and the analyst who never blinks. Point it at the busywork and keep humans on judgment, sequence, and story.
The conversation to master is AI for outcomes, not theater. Five beats matter here: problem and outcome (what decision or delay are we fixing, and how will we know it worked?), data and constraints (what data exists, what’s missing, where are the quality and ownership gaps?), risk and guardrails (privacy, bias, IP, compliance, human-in-the-loop and rollback plans), operating model (who owns the model, who monitors drift, how roles change, what gets decommissioned?), and value cadence (a six to eight week pilot with clear KPIs, scale only if the evidence says so).
Use AI to shorten the distance from insight to decision. That’s how PMs stay indispensable.
Q5. How do you build stakeholder buy-in when a 25-year-old PM is managing 55-year-old executives who’ve “seen it all”?
You don’t out-experience them, you out-prepare and out-clarify.
Three moves work best. Lead with their scoreboard, not your plan. Start with the metric they care about such as cost-to-serve, time-to-decision, or regulatory exposure. Say, “We’re here to take 12 days to 48 hours without increasing risk.” Seasoned execs respect stewards of outcomes, not owners of tasks.
Second, borrow credibility, then earn it. Bring two assets to the first meeting: a one-page decision brief (problem, options, trade-offs, recommendation, risks) and a named SME coalition (“Security signed off on X, Ops will pilot, Finance confirmed ROI”). Anchor authority in the system, not your age.
Third, make progress visible, fast. Run a six-to-eight-week pilot with hard measures and a rollback plan. Book standing 15-minute exec demos with no slides, just the before and after metric. Evidence beats tenure.
Tactics and tone matter too: ask “older brain” questions such as “What failure pattern have you seen here?”, pre-wire big decisions one-on-one, and use stewardship language: “I’ll own the learning loop; you set the guardrails.” Respect, clarity, and evidence create buy-in.
Q6. After 15 years across industries, what are the two most common fatal mistakes PMs make, and the one executive mistake that kills projects? How can both sides fix them?
The first PM mistake is output over outcomes. Shipping features and hitting dates become the goal, value becomes accidental. The fix is to start with two or three measurable outcomes such as “cut cycle time by 40 percent” or “reduce rework by 30 percent.” Tie every milestone to a leading indicator and show the before and after trend weekly. If a deliverable can’t link to a metric, it’s theater.
The second PM mistake is managing to comfort, not risk. Status stays green while unknowns pile up offscreen. The fix is to run a risk-first cadence: top uncertainties, experiments in flight, decisions needed, and what changed since last week. Treat the plan as hypotheses with tests, not a script.
The executive mistake is funding ambition, not learning. Big-bang scope, vague success criteria, and “don’t come back without the whole thing” approaches kill projects. The fix is stage-gating by evidence: fund a six-to-eight-week pilot with hard KPIs, guardrails, and a rollback plan. Scale only when the metric moves and the operating model is ready with support, training, and decommissioning. Sponsor one scoreboard shared by PM, product, ops, and finance.
Bottom line: PMs lead with outcomes and risk, executives fund learning and scale by proof. Projects turn from bets into investments.
Q8 What’s your six-to-eight-week playbook for turning around a stuck program?
Week 0 to 1: Reset the problem. Kill the feature parade. Align on two outcomes and the leading indicators we’ll move first such as cycle time or cost-to-serve. Write a one-page decision brief: problem, options, trade-offs, guardrails.
Week 1 to 2: X-ray with data. Map how work actually flows: queue times, rework loops, approval latency. It’s rarely the Gantt, it’s the wait states. Surface the three biggest constraints to test fast.
Week 2 to 3: Rebuild the operating rhythm. Stand up a single source of truth with board and metrics, a 20-minute weekly risk huddle, and 15-minute exec demos. Reviews become navigation, not narration.
Week 3 to 5: Thin-slice value. Run a narrow pilot with hard measures in one region, product, or segment. Prove or disprove assumptions quickly, keep a rollback plan in the drawer.
Week 5 to 6: Decision and scale. If the metric moves and support is ready, scale deliberately with training, comms, and decommissioning old paths. If not, pivot with evidence.
Week 6 to 8: Lock in habits. Codify the operating model with roles, cadences, and dashboards. Celebrate names, not nouns, the people who moved the number.
The goal isn’t heroics, it’s repeatable momentum: clear outcomes, visible risks, tight feedback loops, and evidence-based scaling.
