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

Monoliths or microservices?

It’s one of the most hotly debated decisions in software engineering, and in this episode of Tech Council, Duncan and Jason lay it all out.

They challenge the hype around microservices and explain why monoliths should be the default starting point for most teams. With Conway’s Law as a backdrop, they show how internal team communication patterns shape your system’s architecture, whether you like it or not.

You'll also hear when it's actually time to break things up, and why Service-Oriented Architecture deserves a second look. It’s a must-listen for anyone scaling tech systems while trying to keep complexity under control.

Top Takeaways:

• Context Matters: The decision between microservices and monoliths depends heavily on the organizational context and size.
• Microservices Complexity: While microservices offer flexibility, they can introduce significant maintenance overhead and complexity.
• Monoliths' Simplicity: Monoliths can be simpler to manage, especially for smaller teams or when local installations are required.
• Scalability Considerations: Both approaches have their scalability challenges, with microservices offering more granular control.
• AI and Future Trends: AI advancements may influence the balance between microservices and monoliths, potentially leading to more consolidation.

Connect with us:

Duncan Mapes

Jason Ehmke

DevGrid.io

DevGrid on LinkedIn

DevGrid on X

Every engineering team pays a tax. The question is: how much?

In this episode of Tech Council, Duncan Mapes and Jason Ehmke spotlight the unspoken, underestimated cost of audit prep, compliance checklists, and spreadsheet-driven project tracking - the administrative tax.

Administrative tax is the accumulation of compliance requirements, audit demands, spreadsheet sprawl, and redundant manual workflows that keep smart people from doing the work they were actually hired to do.

If you’re a CTO or engineering leader aiming to operationalize strategy while scaling cleanly, this episode offers a data-driven roadmap.

Top Takeaways:

• The administrative tax is a significant burden on organizations
• Regulatory pressures have intensified in recent years, impacting operational efficiency
• Perverse incentives can lead to inefficiencies and increased workload
• App managers are often the most affected by administrative tax
• Maintaining a clear inventory is crucial for effective management
• Automation can help alleviate the administrative tax burden
• Organizations need to measure their progress and define what 'good' looks like
• The Cobra effect illustrates how poorly designed incentives can worsen problems
• Effective governance is essential for managing administrative tax
• Smart people in organizations want to improve processes but face limitations

Mentioned in the Episode:

• Internal Tech Emails on X (Twitter) - https://x.com/TechEmails
• Internal Tech Emails post on X about Mark Zuckerberg’s memo about Strategy Tax - https://x.com/TechEmails/status/1944451283236303184

Connect with us:

Duncan Mapes

Jason Ehmke

DevGrid.io

DevGrid on LinkedIn

DevGrid on X

“10x engineers? Probably jerks.”

Jason and Duncan aren’t mincing words in this episode of Tech Council.

They’re calling BS on the myth of the superhuman engineer and making a case for the everyday professionals who care deeply, collaborate well, and raise the bar for everyone else.

This one’s for team leads, CTOs, and senior devs who want to build organizations where great work doesn’t depend on unicorns.

Hit play and rediscover the power of normal engineers.

Top Takeaways:

• The concept of the 10X engineer is often exaggerated and can be counterproductive
• Systems and teams are more important than individual talent
• Decentralizing responsibility can lead to a healthier team dynamic
• Caring about the right things can help shape a better engineering culture
• Designing an ecosystem for talent is crucial for organizational success
• AI tools are changing the expectations of engineering roles
• Specialization will still exist, but versatility will be increasingly important
• Creating an attractive work environment can help draw in top talent
• Great engineers are made through mentorship and support

Mentioned in the Episode:

In Praise of “Normal” Engineers by Charity Majors - https://charity.wtf/2025/06/19/in-praise-of-normal-engineers/

Charity Majors - https://charity.wtf/about/

Charity Majors on LinkedIn - https://www.linkedin.com/in/charity-majors

Connect with us:

Duncan Mapes

Jason Ehmke

DevGrid.io

DevGrid on LinkedIn

DevGrid on X

How do you go from launching apps to leading platforms?

This week on Tech Council, Duncan sits down with Chris Boyd—a mobile dev veteran turned platform engineering leader—to talk about what changes when your team grows, your stack evolves, and your priorities shift.

They talk React Native, metrics, AI, leadership, and what it takes to balance product demands with long-term engineering health.

Chris is also on the verge of launching something new—so you’ll get a peek behind the curtain of what’s next in agent development.

Hit play. This one’s packed.

Top Takeaways:

• Metrics are crucial for understanding app performance
• Leadership in platform engineering requires strong communication skills
• Addressing app quality issues can require drastic measures
• React Native is becoming the standard for mobile development
• Transitioning to a new tech stack should be gradual and strategic
• AI is reshaping the landscape of software development
• Personal development and growth are key in tech careers
• Building a strong team culture is essential for success
• Understanding the business impact of tech decisions is critical
• Continuous learning and adaptation are necessary in tech

Connect with Chris Boyd - https://chrisboyd.me/

Connect with us:

Duncan Mapes

Jason Ehmke

DevGrid.io

DevGrid on LinkedIn

DevGrid on X

When teams struggle with misalignment, vague responsibilities, or clashing priorities, it’s often not a talent issue—it’s a clarity issue. In this episode of Tech Council, Jason Ehmke and Duncan Mapes go deep into one powerful tool that solves these problems at the root: team charters.

They begin by breaking down what a team charter actually is—beyond the corporate buzzword—and why it’s more than just a document. It’s a living agreement that shapes team culture, defines roles, and holds people accountable.

From their own leadership experience, Jason and Duncan share the impact a well-defined charter can have on team dynamics, trust, and output. They unpack the process of building a team charter from scratch: who should be involved, how to navigate personalities and power plays, and how to evolve it as your team grows.

Whether you're leading an engineering org, onboarding new members, or trying to realign a project that's lost steam, this episode will help you build stronger foundations.

Top Takeaways:

• Team charters are often non-existent but crucial for team effectiveness
• A team charter serves as a mission statement or constitution for the team
• Creating a charter helps clarify team responsibilities and success criteria
• Engaging the team in the charter creation process fosters ownership and alignment
• Team charters should be revisited and updated regularly to remain relevant
• Resistance to change can be managed through open communication and understanding
• Stakeholder engagement is vital for gaining buy-in for the team charter
• Success criteria should be clearly defined to measure team effectiveness
• Team charters can help defend the team's purpose and funding during budget cycles
• The process of creating a charter can lead to valuable conversations and insights

Connect with us:

Duncan Mapes

Jason Ehmke

DevGrid.io

DevGrid on LinkedIn

DevGrid on X