Tech Council

Tech Council

By Duncan MapesNewsTechnologyTech News
Download on the App Store

Tech Council episodes

  • Workplace Politics in 2025: How Engineers Can Win Without Playing Games | Episode 18

    Engineering teams in 2025 look different.

    Hybrid work, distributed leadership, and constant change. But one thing hasn’t changed: navigating workplace politics is tricky.

    In this episode, Duncan Mapes and Jason Ehmke get real about how engineers can build influence without playing power games. From handling peer dynamics to understanding leadership intent, they share frameworks that help you stay effective and aligned.

    This conversation started with a listener’s question, and it sparked insights every individual contributor and engineering leader should hear. Whether you’re trying to give feedback, manage relationships, or earn trust on your team, this episode will change how you think about workplace dynamics.

    Top Insights:

    • There are appropriate times to push back against leadership decisions.
    • Understanding the reasoning behind leadership decisions is crucial.
    • Taking ownership in projects can lead to greater influence and responsibility.
    • Building relationships with peers and managers is essential for effective communication.
    • Constructive feedback should focus on helping others succeed, not criticizing them.
    • Examine your intent before providing feedback to ensure it's constructive.
    • Curiosity and humility are key when challenging leadership decisions.
    • Alignment within teams is necessary for fast and effective decision-making.
    • Navigating peer relationships requires transparency and communication.
    • Encouraging audience engagement can lead to valuable discussions.


    Connect with us:

    Duncan Mapes

    DevGrid.io

    DevGrid on LinkedIn

    DevGrid on X

    41 min
  • Blameless Postmortems: The Secret to Better Engineering Teams | Episode 17

    A critical incident hits. Systems go down. Deadlines slip. Fingers point. Sound familiar?

    In this episode, Duncan and Jason break down how high-performing engineering teams recover differently. Instead of assigning blame, they focus on learning, adapting, and improving.

    Through stories and insights, they explore how leadership sets the tone for accountability, why feedback loops are essential for growth, and how creating psychological safety helps engineers move faster without fear.

    If you’ve ever been in the middle of a postmortem wondering how to make your team stronger, this conversation will change the way you think about engineering culture.


    Top Takeaways:

    • Building a resilient engineering culture requires overcoming fear and blame.
    • Incident responses reveal the underlying culture of an organization.
    • Blameless postmortems focus on accountability, not punishment.
    • Leaders must model accountability to foster a healthy culture.
    • Creating a culture of trust involves open communication and vulnerability.
    • Accountability should be balanced with support and understanding.
    • Influencing culture starts with individual actions and leadership.
    • Navigating niceness in leadership requires setting clear expectations.
    • High standards lead to better team dynamics and accountability.
    • Low accountability results in wasted resources and ineffective teams.


    Connect with us:

    Duncan Mapes

    DevGrid.io

    DevGrid on LinkedIn

    DevGrid on X

    33 min
  • Freedom vs. Centralization: Engineering’s Biggest Dilemma | Episode 16

     Every engineering leader has been there.

    Your team wants the freedom to try new tools, adopt new frameworks, and build in ways that make sense to them. But leadership needs consistency, security, and cost control. So… who’s right?

    In this episode of Tech Council, Duncan Mapes and Jason Ehmke unpack how to balance developer autonomy with organizational alignment. It’s not about locking everything down, nor is it about letting every team go rogue. It’s about knowing where freedom fuels innovation and where centralization prevents chaos.

    Whether you’re managing three engineers or three hundred, this episode delivers actionable insights for engineering leaders looking to optimize for both speed and stability.


    Top Takeaways: 

    • Freedom in engineering can lead to significant efficiency gains.
    • Centralization can improve decision-making and reduce costs.
    • A standardized stack allows for quicker onboarding of developers.
    • Decentralization can lead to increased operational risk and inefficiencies.
    • The balance between freedom and centralization is context-dependent.
    • Quick decision-making is crucial for organizational efficiency.
    • Too much freedom can result in stagnation and missed deadlines.
    • Centralized decision-making can help maintain security and compliance.
    • Empowering developers with context can lead to better decision-making.
    • Finding a middle ground is essential for effective engineering management.


    Connect with us:

    Duncan Mapes

    DevGrid.io

    DevGrid on LinkedIn

    DevGrid on X

    46 min
  • Surviving Your First Leadership Transition in Technology | Episode 15

    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

    DevGrid.io

    DevGrid on LinkedIn

    DevGrid on X

    36 min
  • Metrics in Software Engineering: Friend or Foe? | Episode 14

    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

    DevGrid.io

    DevGrid on LinkedIn

    DevGrid on X

    40 min
  • How AI Is Changing Engineering Management | Episode 13

    “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

    DevGrid.io

    DevGrid on LinkedIn

    DevGrid on X

    46 min
  • Monoliths or Microservices: Making the Right Call for Your Context | Episode 12

    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

    DevGrid.io

    DevGrid on LinkedIn

    DevGrid on X

    35 min
  • Admin Tax is Killing Your Engineering Team | Episode 11

     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

    DevGrid.io

    DevGrid on LinkedIn

    DevGrid on X

    45 min
  • 10x Engineers Are Overrated | Episode 10

    “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

    DevGrid.io

    DevGrid on LinkedIn

    DevGrid on X

    42 min
  • How to Think Like a Platform Engineer | Episode 09

    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

    DevGrid.io

    DevGrid on LinkedIn

    DevGrid on X

    1 hr 5 min

About Tech Council

From the publisher's feed

Are you a tech leader, architect, or engineer navigating the intricacies of building within the enterprise? Tech Council delivers the strategies and insights you need to succeed. Hosted by Duncan…