Field Notes № 018

Value Delivery

In 2003, a focus group of IT practitioners spent a day naming the skills employers kept asking for that no program was teaching. They called them value-delivery skills. Twenty years later, those skills are the only ones AI cannot supply.

Dr. Keith Morneau · August 2026 · 9 min read

In 2003, a focus group convened to redesign the IT curriculum for Virginia's community colleges spent a full day trying to name the skills employers kept requesting that no program was teaching. They were not technical skills. They were the skills that made technical skills useful to another person: the ability to communicate a solution to someone who hadn't asked for a lecture, to negotiate what the deliverable should be, to understand the stakeholder's vision rather than the problem statement, to stand in the room and be accountable for the work. The group called them value-delivery skills. The name was practical and precise. The problem it named has not changed in twenty years. It has only become more urgent.

What employers said, repeatedly

Advisory boards across three institutions, quarterly for years, gave the same feedback: graduates needed better oral and written communication skills, teamwork skills, and work experience. The programs heard it. They wrote it into mission statements. They added a communications elective. They returned, the following quarter, to teaching routing protocols.

Why the message never landed

Value-delivery skills cannot be acquired through a lecture about value-delivery skills. The research was clear: behavioral skills must be experienced. There is no curriculum version of communication under pressure, or stakeholder negotiation, or accountability for a result someone else is paying for. The programs kept converting the request into a deliverable they could manage, which was always the wrong deliverable.

The technical-to-commodity shift

Most IT skills became commodities in a globalized economy. The construction phase of technical work — writing the code, configuring the system, generating the output — is increasingly performed offshore, automated, or both. What remains is the design work: understanding the problem, generating creative solutions, delivering them in a form the client can use and the organization can sustain. Design requires value delivery. Value delivery cannot be automated.

What AI has changed

AI can produce technically correct outputs. It cannot negotiate their scope with a stakeholder, explain them to a non-technical manager, or take responsibility when they fail. The value-delivery skills the focus group named in 2003 are not supplementary to the technical work. They are, increasingly, the entire remaining work. Everything the tool cannot do is what the professional now must.

The formation question

The same one it has always been: how do you produce a person who can deliver value — not just produce output? The answer in 2003 was the same as the answer now: through authentic experience, with real stakeholders, under real constraints, with real accountability for the result. Nothing in the last twenty years has changed the conditions under which that formation occurs.