AI changes the development team. Responsibility still needs names.

Code arrives faster. Decisions still matter.

AI can help a development team explore options and produce working code quickly. That makes the surrounding judgment more consequential: whether the team is solving the right problem, whether the output is dependable, and whether anyone will use and support it. The amount of code produced is a poor substitute for those answers.

Start with a Principal

The Principal connects the business objective to the delivery decisions. They keep the roadmap, scope, and acceptance criteria visible and make sure the project has the right skills at the right time. The client should know who is responsible for the engagement when the work becomes ambiguous.

Bring five talents to the work

Sketch defines the problem and tests it through prototypes. Ship builds the application and integrations. Simplify reduces complexity and operating friction. Signal supports adoption and measures what changes. Steady maintains the agreed system after launch. These are responsibilities, with familiar professional roles behind them.

Change the mix as the project changes

Early work may need more discovery and architecture. A build may need more engineering. A rollout needs training, measurement, and support. Five talents does not mean five people assigned full time to every project. It means the responsibilities stay visible as the team changes.

Fund the work in a form that fits

Committed development capacity gives a team a standing roadmap, Principal oversight, and room to improve a system over time. A bounded build can use fixed scope and clear acceptance. Both need explicit decisions when major new work appears. Strategic advice and Workspace management have their own scope because they serve different responsibilities.

Ask what happens after the demonstration

A useful review goes beyond what the software can do on screen. Ask how it handles errors, who can access it, how it will be supported, and whether the people expected to use it helped shape the work. The future development team should make those answers easier to see.