Organization and roles
How teams and companies change once agents write the code: operating models, roles and mandates, and where the bottleneck moves when engineering speeds up.
- 15 posts, newest first
- Agents finished the portal, then it waited in a queue An agent-built portal was ready to ship and waited on a gateway, a firewall rule, a certificate and QA. A factory shortens the build, and only a self-service platform shortens the wait around it.
- When agents write the code, judgment should outrank titles Career ladders reward scope because writing good code at volume used to be scarce. Agents moved the scarcity to judgment, and hiring, leveling, the ladder and pay all need to follow.
- Double throughput needs a mandate, not another pilot A pilot asks a team to prove agentic engineering works here. A mandate states the outcome and makes the boring blockers somebody's problem, which puts the uncertainty on the organization.
- Coding agents are an organizational-design problem Cheaper local generation pushes the coding-agent constraint into team practice, the shared platform, governance, and learning. One practitioner's four-level model of that shift, held up against what DORA can and cannot support.
- When engineering speeds up, the bottleneck moves to product A workshop mapped a full SDLC against agents. Almost every step compressed, except deciding what to build next, and most organizations are not staffed for that shift.
- Your org chart is the context architecture An agent asking a question routes through the same knowledge layers a new hire would. Federated context follows the org chart, with a neutral mediator for the deadlocks.
- When the factory dispatches the work, the manager runs the line When the factory handles assignment and status, the engineering manager's job moves from dispatcher to line operator. Five responsibilities now define the role.
- Delegate, review, own: the operating model of AI-native teams A model lab's playbook for AI-native engineering teams repeats one pattern across seven SDLC phases. The hard part is the review, where the engineer decides which agent findings matter.
- Moving faster with AI only happens when it is a goal A software factory gives you output speed. Outcome speed needs the organization to change around it, and a change that isn't a goal loses to every change that is.
- Teams that rebuilt their org chart got more out of AI McKinsey surveyed about 300 enterprises on AI adoption. Top performers were 7x likelier to run AI-native workflows, while 70 percent have not changed roles at all. Pod restructuring is an upstream investment.
- AI adoption is a leadership problem Teams with every AI tool available still drop them within weeks. Three leadership responsibilities decide whether adoption sticks: unblock usage, make adoption visible, reduce fear.
- If agents can run a company, what is a company for? A panel on responsible agentic development ended on a question it could not answer: follow the efficiency logic all the way to zero employees, and what is left of a company?
- The gap between AI-fast developers and AI-slow companies Individual developers report large gains with AI while whole companies report 5 to 15%. The gap is a management problem: companies added tools without reorganizing how they work.
- AI helps teams build waste faster unless they fix the root causes Teams use the speed of AI agents to ship more features instead of better ones. Four problems teams claim to solve with AI are symptoms of root causes AI does not fix.
- AI makes a feature factory faster, not better Automating the system you already have makes teams more efficient at building things nobody needs. The difference lies in where you invest the time AI saves: validation or more features.