If you want to lead, manage, or grow into higher-impact work, you have to stop doing everything yourself. In this episode, Steve and Jake break down one of the hardest transitions for engineers: letting go of direct control, delegating real work, teaching others, and accepting that people will not do it exactly the way you would. Not theory, practical, tactical advice for engineers who want to stop being the bottleneck and start building capacity.

Key Topics Covered
• Why technical skill alone will not move you into leadership
• The real reason many engineers resist delegation
• Why “they can’t do it as well as me” becomes a career trap
• How taking work back prevents your team from learning
• Why your frustration may be creating the exact problem you complain about
• How to review poor work without destroying confidence
• Why teaching is part of leadership, not an interruption from it
• How to know when someone needs coaching versus when a harder decision is required
• Why making yourself less needed in your current role creates room to grow
• How delegation applies to managers, project leaders, and senior technical experts

Actionable Steps
• Identify the work you keep taking back and ask why you will not let it go
• Delegate with clear expectations, deadlines, and quality standards
• Review work like a coach, not like an angry critic
• Ask whether the miss came from skill, effort, tools, priority confusion, or poor instruction
• Teach through questions instead of immediately showing the answer
• Let people use a different method when the outcome still meets the need
• Build review cycles into the process instead of expecting perfection on the first pass
• Debrief after repeated corrections and ask how to reduce future rework
• Give people the chance to improve before deciding they cannot
• Make it your goal to build people who can eventually outperform you

Who This Episode Is For
• Engineers who want to move into management but struggle to delegate
• Senior individual contributors who are overloaded because they keep owning every detail
• New managers learning how to teach without taking over
• High performers frustrated by the quality of other people’s work
• Engineers who feel stuck and cannot see how their own control habits are part of the problem

Why It Matters
The work you refuse to let go does not prove your value. It limits it. If every task still depends on you, your team stays underdeveloped and your career stays pinned to the same level. Leadership requires capacity. Capacity comes from teaching, delegating, reviewing, and letting other people build skill through real ownership. That is how you create room for bigger problems, higher visibility, and more meaningful impact.

Where to Listen
Spotify
Apple Podcasts
Google Podcasts
Or wherever you get your podcasts

Share
If this episode hit home, send it to someone. The Impactful Engineer grows by word of mouth, just like the best careers do.

Too many engineers wait for the full picture before they act. They want every variable defined, every risk eliminated, and every decision defended before they take the first step. That sounds responsible, but often it is just fear wearing a professional disguise. In this episode, Steve and Jake break down why clarity comes from movement, not overthinking. Using the idea of “fog of war,” they unpack how engineers can move faster, learn sooner, and make better decisions through action, feedback, and iteration. Not theory, practical, tactical advice for engineers who want to lead instead of stall.

Key Topics Covered
• Why unknowns should not stop you from starting
• How the “fog of war” applies to engineering, product development, and business
• The difference between knowns, known unknowns, and unknown unknowns
• Why waiting for perfect information creates delay, not excellence
• How fast iteration reveals problems you could never predict upfront
• Why customer feedback often only becomes useful after you show them something
• How fear of judgment slows engineering decisions
• Why “wasted effort” is often the price of finding the right answer
• How prototypes, prints, drafts, and early layouts pull the future forward
• Why action creates better strategy than endless analysis

Actionable Steps
• Start with what you know, even if the full path is unclear
• Identify the next move instead of trying to solve the entire project at once
• Build the first version sooner so feedback has something to react to
• Treat early mistakes as information, not personal failure
• Use iteration to expose what you could not see from the starting line
• Stop trying to defend every decision before you make progress
• Listen to criticism, extract the useful input, and keep moving
• Don’t confuse rework with wasted effort when the rework creates clarity
• Create tangible outputs that help you think better, such as prototypes, layouts, drawings, or mockups
• Measure progress by learning speed, not by how perfect your first attempt looks

Who This Episode Is For
• Engineers who feel stuck because they do not have every answer yet
• Early-career engineers learning how to make decisions with incomplete information
• Product development engineers trying to move faster without being reckless
• Individual contributors who overthink because they fear being judged
• Engineering leaders who need their teams to act, learn, and adapt faster

Why It Matters
Your career will not grow from waiting until everything is safe, clean, and obvious. The engineers who build influence are the ones who move, learn, adjust, and keep going while others are still trying to protect themselves from being wrong. Energy creates visibility. Iteration creates clarity. Ownership creates momentum. If you want more responsibility, you have to prove you can move through uncertainty without freezing.

Where to Listen
Spotify
Apple Podcasts
Google Podcasts
Or wherever you get your podcasts

Share
If this episode hit home, send it to someone. The Impactful Engineer grows by word of mouth, just like the best careers do.