Skip to content
, ,

The Engineers Who Can’t Use AI Agents Don’t Have a Tools Problem

Your engineers struggling with AI agents don’t need better tools or training. They need permission to work differently and the organizational barriers removed that punish speed.

·

Executive DeckListen

Let your agent read this

Executive briefClick to expand

The efficacy of new engineering capabilities depends upon the organization's existing intellectual capital and its ability to externalize that knowledge.

Invest in explicit knowledge, or new tools will fail.

  • Organizational knowledge, often assumed and implicit, becomes a critical constraint when integrating novel tooling such as agent-driven development. These tools demand explicit, structured input.
  • The ability to articulate context, system behavior, and design rationale is a core competency, distinct from pattern-matching or operational proficiency within an existing system.
  • Practices like pair programming, architecture review, and structured learning foster the externalization of knowledge and the development of deep system understanding.
  • Investing in explicit knowledge directly addresses the underlying capability gaps that new technologies illuminate, rather than merely addressing tool-specific challenges.

The first question for any AI program: what does this organization measure, and what does the measurement reward?

Read the full executive package →

Pen doodle illustration for the-engineers-who-cant-use-ai-agents-dont-have-a-tools-problem

12 min read

The efficacy of new engineering capabilities depends upon the organization's existing intellectual capital and its ability to externalize that knowledge.

Invest in explicit knowledge, or new tools will fail.

  • Organizational knowledge, often assumed and implicit, becomes a critical constraint when integrating novel tooling such as agent-driven development. These tools demand explicit, structured input.
  • The ability to articulate context, system behavior, and design rationale is a core competency, distinct from pattern-matching or operational proficiency within an existing system.
  • Practices like pair programming, architecture review, and structured learning foster the externalization of knowledge and the development of deep system understanding.
  • Investing in explicit knowledge directly addresses the underlying capability gaps that new technologies illuminate, rather than merely addressing tool-specific challenges.

The first question for any AI program: what does this organization measure, and what does the measurement reward?

Companion

Most readers also read: We Kissed Specs and PRDs Goodbye. Product Managers Pass POCs Now.

Written by

The views and opinions expressed in this article are the author’s own and do not represent the positions of any employer, client, or affiliated organization.

Every article, narrated. Listen while you ship.
From the Author

Corporate fiction

Three books. One operating problem. No clean hero.

Read 2028, Meridian, and AgentDrivenDevelopment.com’s Survive free online.

Read free online →

Listen

2 min listenDownload

One useful note a week

Get one good email a week.

Short notes on AI-native software leadership. No launch sequence. No funnel theater.