Leadership Explored Podcast Por Ed Schaefer and Andy Siegmund arte de portada

Leadership Explored

Leadership Explored

De: Ed Schaefer and Andy Siegmund
Escúchala gratis

Leadership Explored is a podcast where Edward and Andy dive into what it means to lead. From practical strategies to deep insights, we explore leadership in all its forms—across industries and beyond. Join us for real conversations about how to lead with purpose.

www.leadershipexploredpod.comEd Schaefer and Andy Siegmund Economía Exito Profesional
Episodios
  • Reporting vs Owning

    Reporting vs Owning
    Mar 10 2026
    Reporting vs Owning (Weather Reports vs Action Plans)Hosts: Ed Schaefer and Andy SiegmundEpisode: 17 (Season 2, Episode 3)Runtime: Approximately 55 minutesRelease Date: March 10, 2026Website: leadershipexploredpod.comEpisode DescriptionIn this episode of Leadership Explored, Ed Schaefer and Andy Siegmund unpack a leadership tension most teams feel every week: when is it enough to “report the weather,” and when are you expected to own the outcome?They break down why “Don’t bring me problems, bring me solutions” can backfire, how psychological safety and decision rights shape what people share, and how to move from passive updates to high-value leadership communication—without overstepping your authority.Ed and Andy introduce a practical spectrum (Reporting → Recommending → Owning), share language shifts that make escalation safer, and offer a simple structure for upgrades to your status updates: What / So What / Now What—plus how to consistently coach teams into stronger ownership over time.What Ed & Andy Discuss* Why “weather reports” frustrate leaders (and how to fix them without shaming people)* The difference between owning the decision vs owning the recommendation* When “above my pay grade” is valid—and how to still add value* How fear, past reprimands, and unclear boundaries push people into “safe” reporting* The “recommendation bridge”: observation → implication → options → recommendation → ask* “Strong convictions, loosely held” as the best operating stance for growing leaders* How to coach ownership by being boringly consistent with your questions* Intention-based leadership (“I intend to…”) and why it changes team dynamicsEpisode Highlights⏳ [00:00] – The tension: problems vs solutions, reporting vs owning⏳ [01:02] – Andy’s “weather report” metaphor + the missing “So what / What now?”⏳ [03:34] – Ed’s spectrum: reporting → recommending → owning the outcome⏳ [09:54] – Why “don’t bring me problems” is a trap + “strong convictions, loosely held”⏳ [17:53] – Why smart people still default to weather-reporting (fear, safety, skills gaps)⏳ [23:00] – “Above my pay grade” is real—here’s how to escalate with value anyway⏳ [26:55] – The middle-ground challenge: too early, too much info, or the “wrong” initiative⏳ [34:30] – Intent-based leadership (“I intend to…”) as the ultimate ownership upgrade⏳ [40:06] – The replaceability problem: sensors are easy to find; owners are not⏳ [44:27] – Coaching move: be predictably consistent with the questions you ask⏳ [47:52] – Ed’s 3 tools: What/So What/Now What, recommendation language, clear boundaries⏳ [54:09] – Your challenge this week: how you communicate up and how safe it is to communicate downKey Quotes* “A bad weather report is observation without implication.”* “There’s a spectrum: reporting, recommending, and owning the outcome.”* “Strong convictions, loosely held—bring a point of view, but don’t pretend you know everything.”* “Recommendations give you an off-ramp. Plans imply ‘come hell or high water.’”* “As a leader, if you want people to stop reporting the weather, you have to make it safe to forecast.”* “Be boringly consistent—your team will learn what you’re looking for.”Practical Takeaways (Listener-Ready)1) Upgrade your update with: What / So What / Now What* What: What happened?* So what: Why does it matter? What’s the impact/risk?* Now what: What’s next? What do you recommend? What help do you need?2) Use “recommendations” to reduce fear and increase initiativeAsking for a recommendation invites thinking without forcing people to pretend they have full authority or complete context.3) Make boundaries explicitIf leaders want ownership, they need to define the sandbox:* “You own schedule decisions; I own budget decisions.”* “You can execute within these constraints without checking with me.”4) Coach ownership through predictable questionsWhen leaders ask the same 3–4 questions every time (“So what?” “What now?” “What do you need?”), people adapt fast—and it becomes a habit.Potentially Controversial / Spicy Moments* Calling “Don’t bring me problems, bring me solutions” a BS line (because it can suppress early warnings).* “If you’re afraid to share ideas because you’ll get steamrolled, go find somewhere else to work.”* The implied leadership critique: if teams only report, the environment may be training them to stay “safe,” not useful.Resources Mentioned* Intent-Based Leadership (“I intend to…”) — L. David Marquet* Delegation Poker — Management 3.0* Psychological Safety This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit www.leadershipexploredpod.com
    Más Menos
    55 m
  • Projects Always Start Red

    Projects Always Start Red
    Feb 24 2026
    Projects Always Start RedHosts: Ed Schaefer & Andy SiegmundEpisode: 16 (Season 2, Episode 2)Runtime: Approximately 52 minutesRelease Date: February 24, 2026Website: leadershipexploredpod.comEpisode DescriptionYou kick off a new project, nothing has slipped yet, and the first status report goes out… green. But should it? In this episode, Ed and Andy challenge a default that quietly fuels late-stage surprises: treating “not behind yet” as “on track.” They argue that projects don’t start green—they start uncertain, and uncertainty is risk.Ed introduces the idea that projects should “earn their way to green” by reducing unknowns over time, not by waiting until something breaks. Andy pushes on practicality: different project types, organizational culture, and the reality that RAG status is often an escalation trigger—not a learning tool. Together, they land on a more usable approach for real organizations: add trend and confidence signals (and separate “uncertainty” from “needs escalation”) so leaders can see what’s coming before it’s too late.What Ed & Andy discuss* Why “green at kickoff” often means optimism, not true status* The difference between measuring “have we failed yet?” vs. “how confident are we?”* How the cone of uncertainty shows up in real delivery work* Why dependency-heavy work creates an illusion of control* Andy’s “panic meter” analogy (and why it’s a surprisingly practical model)* How to make this usable without starting a culture war in your PMO* The role of psychological safety in honest, early reportingEpisode Highlights (Timestamps)* ⏳ [00:00] The kickoff status report problem: “green” as default* ⏳ [02:00] The core thesis: early projects are high-uncertainty—so why call them green?* ⏳ [05:12] Andy’s pushback: repeatable work vs. true uncertainty* ⏳ [08:23] Ed’s workaround: an “initialization phase” that’s off-RAG* ⏳ [20:25] The big question: if you start red, what’s the escalation mechanism?* ⏳ [28:27] The “panic meter” framing (and why it clicks)* ⏳ [35:11] Dependency math + complexity: why confidence collapses fast* ⏳ [44:03] The practical move: trends, confidence, and unknowns in reporting* ⏳ [51:40] Three tactical actions you can use tomorrowKey Takeaways* Status isn’t just color—it’s signal. Without trend and confidence, green can hide real risk.* Early honesty prevents late drama. If leadership only finds out at “red,” the system trained people to delay truth.* Separate uncertainty from escalation. Not every unknown requires executive intervention—but pretending unknowns don’t exist creates surprises.* Trend beats snapshot. “Amber trending green” is often healthier than “Green trending down.”* Culture is the real constraint. You don’t “implement” better reporting; you co-create it to fit how your organization reacts to bad news.“Your Move This Week” (Listener Challenge)Pick a project that’s early-stage and ask: Is our status green because we’re confident… or because we’re hopeful?Then try one of these:* Add a confidence score (1–5) next to status* Add a trend arrow (improving / flat / worsening)* List the top unknowns explicitly—and what it will take to turn them into knownsKey Quotes* “When we mark it green on week one, we’re not reporting status—we’re reporting optimism.”* “I don’t think it benefits us to manage decline.”* “When the vets start getting stressed out, treat that like a signal.”* “Real leadership isn’t pretending you know the future. It’s reducing what you don’t know—on purpose.”Potentially Spicy / Debate-Worthy Moments* Calling projects “red” at the start sounds like pessimism—Ed argues it’s just math and realism.* The idea that traditional RAG reporting is structurally designed to hide uncertainty until it becomes undeniable.* The critique that many dependency-heavy plans are basically “hope with slideware,” even when everyone reports green.Contact / FeedbackHave a story or a perspective you want to share? Connect with us on LinkedIn or email leadershipexplored@gmail.com This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit www.leadershipexploredpod.com
    Más Menos
    55 m
  • Watermelon Projects

    Watermelon Projects
    Feb 10 2026

    Watermelon Projects: Green on the Outside, Red on the Inside

    Hosts: Ed Schaefer and Andy Siegmund

    Episode: 15 (Season 2, Episode 1)

    Runtime: ~54 minutes

    Release Date: February 10, 2026

    Website: leadershipexploredpod.com

    Episode Description

    A watermelon project is green on the outside and red on the inside—everything looks “fine” on dashboards, but the people doing the work know the risks are stacking up. Ed and Andy explore why this happens across organizations of all sizes, why “more reporting” often makes the problem worse, and what actually works: psychological safety, incentives aligned to transparency, and leadership behavior that makes escalation feel like support—not punishment.

    They also dig into nuance: when does a risk warrant flipping to amber/red, and when does escalation become “crying wolf”? You’ll hear practical methods like pre-mortems, blameless postmortems, and “highlight + lowlight” reporting that forces reality into the open—without turning red status into a career-limiting move.

    Episode Highlights (with timestamps)

    ⏳ [00:00] – What a “watermelon project” is—and why it’s rarely a surprise to the team doing the work.⏳ [05:04] – A key smell: the absence of yellow (green → red whiplash).⏳ [05:41] – Andy’s caveat: shifting to amber/red should mean there’s something actionable you can do.⏳ [09:26] – ROAM risks (Resolve/Own/Accept/Mitigate) and why “accepted” risks shouldn’t become performative escalations.⏳ [10:32] – Ed’s real-world example: a major data risk called out early… and ignored anyway.⏳ [15:17] – Why this is everywhere (not just big companies)—but often worse in insecure, low-trust environments.⏳ [20:18] – The psychology and incentives: optimism, fear, and “we always pull out of the nosedive.”⏳ [24:42] – The “nobody wants to tell the boss” chain (plus the Toyota andon cord as the culture counter-example).⏳ [29:28] – Why escalation becomes punishment: meetings, extra reporting, and leaders “gumming up” the work.⏳ [31:12] – The hero trap: working nights/weekends to keep it green… until burnout + surprise red.⏳ [33:19] – Reporting to the plan vs. reporting reality—and why outcome-focus beats “build the widget.”⏳ [37:01] – The bureaucracy trap: “thicker rind” doesn’t fix a red interior; culture does.⏳ [39:47] – Blameless postmortems: system failure vs. people blame.⏳ [44:46] – What leaders should do when it turns red: calm, useful, and action-oriented.⏳ [46:03] – Concrete takeaways: questions to ask, pre-mortems, and rewarding early warning signals.⏳ [47:38] – A practical reporting mechanism: require highlights + lowlights—and block “weakness as a strength” spin.⏳ [53:20] – The challenge: are your projects green because they’re truly on track—or because they have to be?

    Key Takeaways for Leaders

    * Green status is not proof—it’s a signal. If you’ve been burned before, don’t accept green casually—ask one smart question that reveals reality.

    * Escalation must reduce pain, not add overhead. If “red” triggers 13 meetings and more forms, you’ve trained people to hide risk.

    * Reframe red as a request for support (not a verdict of failure). In healthy systems, raising the flag early is a competence move.

    * Stop “reporting to the plan.” Plans are hypotheses. Reality is the data. Strong leaders update plans—not narratives.

    * Culture beats bureaucracy. More process often just thickens the rind while the project stays red underneath.



    This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit www.leadershipexploredpod.com
    Más Menos
    54 m
Todavía no hay opiniones