AI is Changing the Tools. The House Holds.

I've been talking with a lot of R&D leaders about how they're building software with AI. Some have strong opinions. Some are overwhelmed. No one has really figured it out. Teams commit fully to an approach, and two months later they've pivoted to the next one. For every success story there's an equally convincing counterexample.

I don't expect anyone to find the one right answer. There are many, many, many imperfect ways. So the more useful question for a leader in the middle of it: what holds steady while everything else moves?

I created the House of Software Value Delivery to diagnose where an organization will get the most from new structure.

Valuable software rests on three pillars of needs: Business, Technical, and User. Each is described by Attributes, like Timely, Secure, or Intuitive. Underneath sits the foundation, a well-functioning ecosystem, with Attributes like Collaboration and Learning & Growth. You can't change an Attribute directly. You change the Tools: the practices, technologies, and rituals that move it.

Every AI practice I've seen teams adopt is a Tool, and each one lands in one of the House's three Tool layers.

Below the foundation, AI meeting notes and drafted status updates aim at Collaboration and Ease.

Between the foundation and the pillars, coding assistants, agents, and AI-drafted specs aim at the software itself: Functional, Maintainable, Timely.

Above the pillars, AI code review and generated tests check whether the software is Functional and Secure before it reaches users.

The roof, the pillars, and the foundation haven't moved. Customers still need software that is Timely and Intuitive. It still has to be Secure and Maintainable, whether a person or an agent wrote the code. And teams still need to plan together and grow the next generation of engineers.

AI is changing the Tools. The House holds.

That gives every AI practice the same test as any other Tool: which Attribute is it supposed to move, and did it move? If you can't name the Attribute, you've made a Change. Name the Attribute and measure it, and the Change becomes an experiment.