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

Ownership and leadership are more than buzzwords—they're the backbone of successful software teams. In this episode, Duncan Mapes and Jason Ehmke examine how to foster responsibility without micromanagement and lead with purpose in tech.

Expect insights into managing trade-offs, building trust, and creating systems where autonomy thrives. The conversation covers leadership transitions, empowering teams, and ensuring standards don’t slip in the name of speed.

If you're striving for balance between freedom and structure in your team, this is the conversation you need.

Top Takeaways:

• Ownership is crucial in application development
• Leaders must empower their teams without micromanaging
• Transitioning from team member to leader requires unlearning old habits
• Encouraging feedback is essential for growth
• Balancing autonomy and standardization is a leadership challenge
• Technology decisions should be made with long-term outcomes in mind
• Managing technical debt is a shared responsibility
• Clear roles and responsibilities prevent chaos in teams
• Data-driven decision-making enhances accountability
• Building a culture of ownership leads to better outcomes

Connect with us:

Duncan Mapes

Jason Ehmke

DevGrid.io

DevGrid on LinkedIn

DevGrid on X

Software development is rarely straightforward. Even with experienced teams and the best intentions, projects still miss deadlines, fail to meet expectations, or get abandoned altogether.

In this episode of Tech Council, Duncan Mapes and Jason Ehmke explore why that happens—and what teams can do differently. They dig into the importance of real-time feedback, managing scope, and maintaining healthy communication between engineering and business units.

Learn how to align vision, reduce cognitive overload, and create urgency without panic. Whether you're leading software projects or embedded in the code, these insights will help you understand where things go wrong—and how to fix them before it’s too late.

Top Takeaways:

• Incremental value delivery is essential in software development
• Understanding cognitive overhead helps in prioritization
• Smaller feature sets reduce team burden and improve focus
• Iterative development allows for better market feedback
• Trade-offs are inherent in software project management
• Real data is necessary for effective decision-making
• Waterfall methods can be limiting in fast-paced environments
• Customer relationships can tolerate imperfect products
• Empathy between business and engineering teams enhances collaboration
• Understanding change management involves recognizing the complexities behind seemingly simple requests
• Building trust and relationships is crucial for effective change management
• Setting clear expectations can help manage the impact of changes on project timelines
• Communication is key to ensuring all parties are aligned on project goals and change.
• Hitting 100% of deadlines can indicate a lack of ambition in project planning
• Maintaining a record of agreements and changes is essential for accountability
• Teams need to understand the importance of their work to foster intrinsic motivation
• Creating a sense of urgency can help teams stay focused and effective
• It's important to have open conversations about project scope and timelines
• Leaders should strive to reconcile team vision with organizational objectives

Connect with us:

Duncan Mapes

Jason Ehmke

DevGrid.io

DevGrid on LinkedIn

DevGrid on X

AI has moved from hype to habit, but at what cost?

In this episode of Tech Council, Duncan Mapes and Jason Ehmke break down the ethical, technical, and human implications of AI in software development. From workflow automation to code generation and performance tracking, AI is changing the landscape—but not always in the ways you’d expect.

The conversation explores the hidden pressures AI introduces: the erosion of organic team communication, the complexity of evaluating performance fairly, and the risk of turning development into a surveillance-heavy space. Through it all, Duncan and Jason emphasize the need for thoughtful leadership that balances innovation with intention.

Tune in and get a fresh, honest look at how to lead tech teams through the AI revolution.

Top Takeaways:

• AI ethics is a complex and evolving topic.
• The integration of AI tools can streamline workflows.
• Different AI models have varying levels of effectiveness.
• Cognitive load in code reviews can be significantly reduced with AI.
• AI can change the dynamics of communication in teams.
• Surveillance capabilities in development environments raise ethical concerns.
• The debate on task execution is shifting towards action-oriented approaches.
• AI tools can help clarify and optimize developer tasks.
• The role of software engineers is evolving with AI advancements.
• AI's impact on the industry is largely positive, despite short-term challenges. Developer efficiency can be indicated by various metrics.
• The origin of DevGrid is rooted in optimizing data and processes.
• Sales outcomes are easier to measure than engineering outcomes.
• Incentives play a crucial role in performance evaluation.
• Surveillance tools can help identify blind spots for developers.
• Critical feedback is essential for growth in any profession.
• Management tools should empower rather than alienate developers.
• AI agents are transforming the coding landscape.
• Leadership requires continuous learning and adaptation.
• Maintaining a balance between oversight and trust is vital.

Connect with us:

Duncan Mapes

Jason Ehmke

DevGrid.io

DevGrid on LinkedIn

DevGrid on X

What kind of season is your organization in—wartime or peacetime?

In this episode of Tech Council, Duncan Mapes and Jason Ehmke dig into the organizational cycle and how it shapes everything from decision-making to developer priorities. Whether your team is scaling fast, navigating a downturn, or recalibrating after a sprint-heavy phase, understanding the moment your company is in is critical to doing the right work at the right time.

This conversation moves beyond theory to give tactical insight into how engineers, managers, and technical leaders can adapt to different phases of organizational life. From maintaining operational stability to responding to layoffs, Jason and Duncan explore how visibility, communication, and standard-setting influence the success of both the team and the business.

Top Takeaways:

• Understanding the cycle your organization is in is crucial.
• Balancing wartime and peacetime strategies is essential for success.
• Feature delivery should be balanced with maintenance to avoid technical debt.
• Leaders must communicate the value of their teams effectively.
• Situational awareness is key in navigating organizational challenges.
• Business outcomes should drive technical decisions and priorities.
• Negotiation is a vital skill for technology leaders.
• Predictability in project management can be more valuable than velocity.
• Visibility of team contributions is important for organizational success.
• The future of coding will increasingly involve AI integration.

Connect with us:

Duncan Mapes

Jason Ehmke

DevGrid.io

DevGrid on LinkedIn

DevGrid on X