Re:Engineered

Chris Stasiuk
  • 0.0 (0)
  • Careers
  • Updated Weekly

Re:Engineered is a podcast for engineers and technical professionals who've realized that being great at the technical work isn't enough anymore. Hosted by Chris Stasiuk, an engineer turned coach who spent 25 years growing from project engineer to shareholder at an engineering consulting firm, and now coaches technical professionals on the leadership skills no one taught them. The show treats communication, leadership, and influence as systems. Not personality traits. Not corporate theater. Skills you can learn and apply without pretending to be someone you're not. Episodes include solo takes, newsletter riffs, and conversations with engineers and experts in areas technical professionals often overlook. No theory. Real frameworks from real engineering environments, with direct guidance on managing up, leading without authority, and navigating difficult conversations. No buzzwords. No corporate platitudes. No advice from consultants who've never built anything. If you're the one who actually solves the problems but keep getting passed over for people who talk more than they contribute, this podcast was built for you. Because being a great engineer isn't enough anymore.

  1. 2d ago

    You Pre-Mortem the Project. You Don't Pre-Mortem the Contract.

    A non-compete signed in good faith does not care about good faith when conditions change. Engineers know this. They build redundant pumps before commissioning starts because hindsight is expensive and foresight is cheap. The same engineers will sign contracts that constrain their future on the assumption that the relationship lasts, the business holds shape, and the timeline cooperates. None of those are guaranteed. Episode 027 is about the pre-mortem you skip when the runway looks long, and what it costs when the runway shortens. What You Will Take Away The pre-mortem engineers run on projects, and the one they skip on their own careerThe contractual equivalent of a redundant pump: sunset clauses, carve-outs, mutual termination triggersWhy pre-mortems are insurance, and why insurance gets skipped when the basement has never floodedThe failure mode in a souring agreement: optimism on all sides, and a missed pre-mortemThe selective rigor that engineers apply on projects but skip on their own commitmentsA simple question to run before signing: imagine this is binding me in a situation neither of us anticipated. What would have to be true for that to happen?Who This Is For Engineers about to sign a non-compete, non-solicit, or equity agreement they have not stress-testedEngineers who have accepted a role on the assumption of a long runway nobody has actually guaranteedEngineers who run failure-mode analysis on every project and have never run one on a contractEngineers who feel a clause is restrictive but are not sure what to ask forFollow Re:Engineered wherever you get your podcasts. Re:Engineered is a podcast for engineers and technical professionals navigating the shift from technical excellence to leadership responsibility. Hosted by Chris Stasiuk, a professional engineer with over 25 years in engineering consulting and leadership roles, the show treats leadership, communication, and decision-making as systems to understand — not personality traits to fake. No buzzwords. No corporate theater. Just clear thinking about how technical people actually lead. Explore episodes, transcripts, and related resources at https://chrisstasiuk.com/podcast/.

    7 min

  2. Jun 17

    3 Signs You Never Renamed the Relationship With Your Former Peer

    When you get promoted over a former peer, your structural authority changes on a specific date. The relationship does not. Most engineers assume it self-adjusts, or they avoid naming the shift because the conversation feels awkward. It does not self-adjust. And the longer you wait, the more expensive the gap becomes, because the friend card only gets played once the structural reality and the relational contract are running on different settings. What You Will Take Away Why the managing-former-peers failure modes all trace back to a single skipped conversation, not a lack of communication skillThe three-piece structure of a renaming conversation: what stays, what doesn’t, and how to handle the collisionWhat that conversation actually sounds like in plain language, not HR-speakWhy the renaming is a recurring calibration, not a one-time event at the promotion pointThree observable signs the old contract is still running your work relationshipWho This Is For Engineers who were recently promoted to manage someone they used to work alongsideTechnical leaders who sense friction with a former peer but haven’t named what is driving itManagers who have been in the role for a while and suspect some peer-era dynamics never got addressedFollow Re:Engineered wherever you get your podcasts.  Re:Engineered is a podcast for engineers and technical professionals navigating the shift from technical excellence to leadership responsibility. Hosted by Chris Stasiuk, a professional engineer with over 25 years in engineering consulting and leadership roles, the show treats leadership, communication, and decision-making as systems to understand — not personality traits to fake. No buzzwords. No corporate theater. Just clear thinking about how technical people actually lead. Explore episodes, transcripts, and related resources at https://chrisstasiuk.com/podcast/.

    10 min

  3. Jun 10

    You Delegated the Work and Kept the Part That Mattered

    The work you handed off came back half done, so you figured the person wasn’t ready or you delegated too soon. Wrong read. The work didn’t bounce because they failed. It bounced because you handed over the easy part and kept the part that mattered. Delegation isn’t one move. It’s three transfers at the handoff, then a hold afterward, and most engineers do the first transfer and skip everything else.  Chris walks through a project where he handed the project management work to an internal PM but quietly kept the client relationship, the day-to-day context, the gotchas, the trade-offs. When he had to step away, the team was left deciding blind on the part he never transferred. They did the best they could with the information they had. The problem was the rest of it was sitting with him. This episode is the mechanics behind that failure and how to avoid it: the outcome, the authority, the context, and why taking the work back the moment it comes back at 80 percent is where the whole thing collapses.   What You Will Take Away Why “I need to trust my team more” is the wrong diagnosis. The mechanism isn’t how controlling you are, it’s what you actually transferred at the handoff.The difference between transferring a task and transferring an outcome. Task assignment keeps the definition of done in your head, so every judgment call routes back to you.The three-decision test for authority. If you can’t name three calls the person can make without checking with you, you transferred labor, not authority, and you’re still the bottleneck.Why authority without context sets someone up to fail with full permission. Judgment runs on the why, the constraints, and the trade-offs you already rejected, and if you keep those, they decide blind.The third path on check-ins, between swooping in when you’re nervous and going dark until something breaks. Pre-scheduled and structured, so your nerves don’t drive it and their silence doesn’t hide a problem until it’s expensive.Why holding the line at 80 percent is part of the mechanism, not a personality trait. The moment you take the work back, authority snaps to you and the person learns not to fully commit. Who This Is For Engineers who delegated something and watched it bounce straight back, then assumed the person wasn’t readyNew leads who feel busier after handing work off than they did beforeAnyone who’s said “I’ll just handle this one” and meant it as a fix rather than a relapseEngineers who heard episode four on the indispensability trap and want the actual mechanics for getting outTechnical leads who keep getting pulled back into work they thought they’d already delegated  Follow Re:Engineered wherever you get your podcasts. Re:Engineered is a podcast for engineers and technical professionals navigating the shift from technical excellence to leadership responsibility. Hosted by Chris Stasiuk, a professional engineer with over 25 years in engineering consulting and leadership roles, the show treats leadership, communication, and decision-making as systems to understand — not personality traits to fake. No buzzwords. No corporate theater. Just clear thinking about how technical people actually lead. Explore episodes, transcripts, and related resources at https://chrisstasiuk.com/podcast/.

    11 min

  4. Jun 3

    Engineering Judgment Isn’t Innate. It’s Built From Three Inputs.

    Engineering judgment gets treated as something mysterious. A gift. Something senior engineers have and junior ones don’t, with no clear path between them. That framing is convenient for the senior engineers and useless for everyone else. Judgment is good decision-making folded together with technical knowledge, lived experience, and consideration of who comes after you. Each input is learnable, each one alone produces something worse than judgment, and bad judgment persists because it still looks like rigor from the outside.   What You Will Take Away Engineering judgment isn’t a special category. It’s good judgment applied to engineering work, built from technical knowledge, lived experience, and consideration of who builds, operates, and maintains the design after you.Each component matters on its own. Technical knowledge alone gets you correct but useless. Lived experience alone gets you a gut call without rigor. Downstream consideration alone gets you good intentions without competence.Bad judgment doesn’t look like incompetence from the outside. It looks like rigor. That’s why it persists, and why nobody catches it until the operator is the one paying for it.When the three inputs are working, judgment doesn’t show up as heroics. It shows up as a hatch nobody argued about.Lived experience doesn’t respect discipline boundaries. The electrical engineer made a structural call because the input was there.Credentials get you the title. Judgment is what you build from there, by asking, listening, staying curious, and integrating what you can’t calculate.  Who This Is For Engineers who have been told to “use judgment” but never given a definition that holds up.Engineers who have watched senior colleagues make calls they couldn’t explain and want to know how that gets built.New engineers being graded on judgment in performance reviews with no visible criteria.Engineers who have taken the technically correct path and been overruled by an operator’s gripe, and wondered why.Senior engineers who want to teach judgment to their teams but don’t have a way to break it down.  Follow Re:Engineered wherever you get your podcasts. Re:Engineered is a podcast for engineers and technical professionals navigating the shift from technical excellence to leadership responsibility. Hosted by Chris Stasiuk, a professional engineer with over 25 years in engineering consulting and leadership roles, the show treats leadership, communication, and decision-making as systems to understand — not personality traits to fake. No buzzwords. No corporate theater. Just clear thinking about how technical people actually lead. Explore episodes, transcripts, and related resources at https://chrisstasiuk.com/podcast/.

    7 min

  5. May 27

    The Day One Mistake: Why Promoted Engineers Confuse What Was Given with What Has to Be Earned

    Most engineers stepping into leadership have the credentials. The degree, the certification, the years on the job. What they don’t have yet is earned credibility, and that gap is real whether they acknowledge it or not. There are two ways to handle it: assert your way across it, or learn your way across it. The first closes the gap on paper. The second closes it in reality. This episode draws on a conversation with a retired Canadian Armed Forces lieutenant colonel whose first six months in command maps almost perfectly onto what happens when engineers get their first leadership role. What You Will Take Away The gap between your title and your earned credibility is real on day one. Asserting your way across it makes it invisible. Learning your way across it makes it temporary.Two failure modes show up when engineers step into leadership: assertion mode, where the team learns to wait you out, and the disappearing act, where you defer to everyone and show up with no point of view.The third path is holding the role clearly: make decisions, stay responsible, and be honest about what you don’t know while staying genuinely curious about what the people around you do.Your credentials got you in the room. They don’t get you the room. That part is earned through actual work and actual conversations, not through asserting it away.Military colleges have a reputation for producing officers who arrive knowing everything. Engineering has the same problem. The iron ring does not confer credibility. It starts the clock on earning it.The engineers who build credibility fastest treat the people around them as the resource, not as the problem.One question worth sitting with: who around you actually knows things you don’t yet? Name them. Then figure out how you’re using that resource.  Who This Is For Engineers who just got promoted and are trying to prove they deserve it.New managers who feel the pull to over-explain and over-certify every decision.Engineers who have gone quiet in a leadership role because they don’t feel ready.Anyone who has watched a new leader assert authority and seen the team tune them out.Engineers who know the gap is real but haven’t named it yet.  Follow Re:Engineered wherever you get your podcasts. Re:Engineered is a podcast for engineers and technical professionals navigating the shift from technical excellence to leadership responsibility. Hosted by Chris Stasiuk, a professional engineer with over 25 years in engineering consulting and leadership roles, the show treats leadership, communication, and decision-making as systems to understand — not personality traits to fake. No buzzwords. No corporate theater. Just clear thinking about how technical people actually lead. Explore episodes, transcripts, and related resources at https://chrisstasiuk.com/podcast/.

    11 min

  6. May 20

    Someone’s Running a Model of You

    Engineers think they have a communication problem. They have a system problem. Every individual communication failure compounds into a predictive model that other people run of you, and that model is what gets used in rooms you’re not in. Chris tells the story of being told over beers that some of his clients thought he was a real piece of work, then unpacks how he’d been counting only the deliberate signals while ignoring the noise. The capstone of the Communication System arc, this episode names the cumulative effect of every communication act and gives engineers an audit for predicting and adjusting the model their decision surface is running of them. Re:Engineered is a podcast for engineers and technical professionals navigating the shift from technical excellence to leadership responsibility. Hosted by Chris Stasiuk, a professional engineer with over 25 years in engineering consulting and leadership roles, the show treats leadership, communication, and decision-making as systems to understand — not personality traits to fake. No buzzwords. No corporate theater. Just clear thinking about how technical people actually lead. Explore episodes, transcripts, and related resources at https://chrisstasiuk.com/podcast/.

    8 min

  7. May 13

    The Room Changed. Did You?

    Engineers don’t fail in high-stakes rooms because their analysis is wrong. They fail because they’re answering in the wrong unit. A project manager walks a client through a scope change in hours; the client asks for dollars; the PM keeps giving hours. The problem isn’t accuracy — it’s currency. Every room runs on a different one: internally it’s hours and feasibility, for clients it’s cost and timeline, for senior leadership it’s exposure and consequence. When you force the other person to do the conversion, you’re making them do your job. This episode introduces a single pre-meeting question and a three-part structure — impact, exposure, recommendation — that compresses technical analysis into something decision-ready without losing the rigor underneath. Re:Engineered is a podcast for engineers and technical professionals navigating the shift from technical excellence to leadership responsibility. Hosted by Chris Stasiuk, a professional engineer with over 25 years in engineering consulting and leadership roles, the show treats leadership, communication, and decision-making as systems to understand — not personality traits to fake. No buzzwords. No corporate theater. Just clear thinking about how technical people actually lead. Explore episodes, transcripts, and related resources at https://chrisstasiuk.com/podcast/.

    11 min

  8. May 6

    You Went Quiet. They Filled in the Gap.

    Engineers don't lie about what they don't know. They go quiet. That instinct is correct in technical work, where you don't sign off on a calc you haven't verified. It backfires in leadership, where silence isn't neutral and the room fills it in with whatever leaks through. This episode names the three failure modes that look like professionalism from the inside and ghosting from the outside, and gives the three-part pattern engineers can use instead: what you know, what you don't, and when you'll know more. Re:Engineered is a podcast for engineers and technical professionals navigating the shift from technical excellence to leadership responsibility. Hosted by Chris Stasiuk, a professional engineer with over 25 years in engineering consulting and leadership roles, the show treats leadership, communication, and decision-making as systems to understand — not personality traits to fake. No buzzwords. No corporate theater. Just clear thinking about how technical people actually lead. Explore episodes, transcripts, and related resources at https://chrisstasiuk.com/podcast/.

    8 min
See All (27)

About

Re:Engineered is a podcast for engineers and technical professionals who've realized that being great at the technical work isn't enough anymore. Hosted by Chris Stasiuk, an engineer turned coach who spent 25 years growing from project engineer to shareholder at an engineering consulting firm, and now coaches technical professionals on the leadership skills no one taught them. The show treats communication, leadership, and influence as systems. Not personality traits. Not corporate theater. Skills you can learn and apply without pretending to be someone you're not. Episodes include solo takes, newsletter riffs, and conversations with engineers and experts in areas technical professionals often overlook. No theory. Real frameworks from real engineering environments, with direct guidance on managing up, leading without authority, and navigating difficult conversations. No buzzwords. No corporate platitudes. No advice from consultants who've never built anything. If you're the one who actually solves the problems but keep getting passed over for people who talk more than they contribute, this podcast was built for you. Because being a great engineer isn't enough anymore.

Information

  • Creator
    Chris Stasiuk
  • Years Active
    2K
  • Episodes
    27
  • Rating
    Explicit
  • Copyright
    © 2026 Re:Engineered
  • Show Website
    Re:Engineered