Most advice about leadership transitions is sugarcoated: “Trust the process, be patient, focus on people.”

While that’s not wrong, it’s not the whole story. In this candid episode, Duncan Mapes and Jason Ehmke break through the noise to talk about what actually matters when you step into a new role: defining success metrics, proving yourself with early wins, and building credibility fast.

Leadership transitions are less about theory and more about execution, and the way you handle those first 90 days can set the tone for years to come.

Top Takeaways:

• Transitioning from a large enterprise to a smaller organization can be intimidating.
• In smaller companies, accountability is more direct and personal.
• The first few months in a new role should focus on learning and absorbing information.
• Assessing team dynamics and architecture is crucial for effective leadership.
• Early wins are important for building credibility and trust.
• Defining success criteria is essential for aligning team goals with organizational objectives.
• Fresh eyes can provide valuable insights into existing processes and team dynamics.
• Avoid making snap judgments about team members; assess their skills fairly.
• Planning should be done in phases, focusing on short-term and long-term goals.
• Continuous self-improvement is vital for effective leadership.

Mentioned in the Episode:

• Extreme Ownership: How U.S. Navy SEALs Lead and Win by Jocko Willink and Leif Babin
• The Dichotomy of Leadership: Balancing the Challenges of Extreme Ownership to Lead and Win by Jocko Willink and Leif Babin
• 7 Habits Of Highly Effective People by Stephen Covey
• High Output Management by Andy Grove

Connect with us:

Duncan Mapes

Jason Ehmke

DevGrid.io

DevGrid on LinkedIn

DevGrid on X

Metrics aren’t the problem. You are.

For years, engineers have hated metrics, but what if the real issue isn’t the numbers… it’s how they’re used?

In this episode, Duncan Mapes and Jason Ehmke dig into why many engineers roll their eyes at metrics, the traps leaders fall into when measuring productivity, and how to shift the conversation toward continuous improvement.

They challenge conventional thinking, arguing that metrics can transform engineering culture if leaders stop using them as surveillance tools. They break down how to measure without micromanaging, why team-level data beats individual stats, and how metrics can expose, not punish, weak spots in your delivery process.

Top Takeaways:

• Metrics in software engineering are often misunderstood and misused.
• Engineers typically resist being measured due to a fear of scrutiny.
• Effective metrics should focus on outcomes, not just activity.
• Continuous improvement is essential for enhancing team performance.
• Team-level metrics are more valuable than individual metrics.
• Data should be used to identify bottlenecks and improve processes.
• Transparency in metrics fosters trust and collaboration within teams.
• Asking the right questions can uncover valuable insights.
• Metrics should drive conversations about improvement, not blame.
• A culture of measurement can lead to better outcomes and happier customers.

Connect with us:

Duncan Mapes

Jason Ehmke

DevGrid.io

DevGrid on LinkedIn

DevGrid on X

“Should junior devs still learn the fundamentals if AI can write the code for them?”

That’s one of the real questions Duncan and Jason tackle in this episode of Tech Council. They get honest about what AI is actually changing in engineering management, and what’s just hype.

They dive into how teams are adapting, what mentorship looks like when everyone has an AI assistant, and why outcomes matter way more than implementations.

If you manage a team or work on one, this episode will shift how you think about leading in a tech space that’s moving fast.

Top Takeaways:

• AI tools are changing the expectations for junior developers
• Mentorship remains crucial in developing good habits in junior developers
• Effective communication is key in managing teams
• Evaluating work now requires deeper understanding beyond surface-level quality
• The importance of outcomes is heightened in the age of AI
• Setting clear expectations is more challenging yet essential
• Junior developers can now contribute to higher-level discussions
• Documentation and formal practices are becoming more important
• The role of a manager is to guide teams towards achieving outcomes
• Technical skills can be taught, but attitude and engagement are critical

Connect with us:

Duncan Mapes

Jason Ehmke

DevGrid.io

DevGrid on LinkedIn

DevGrid on X