--- title: Reorganise Your Team in the Agentic Era --- [![Aicadium](https://landing.aicadium.ai/hubfs/Aicadium_blue_logo.svg)](https://landing.aicadium.ai/?hsLang=en) [Get in touch](https://landing.aicadium.ai/contact?hsLang=en) Agentic Product Development 15 min read What we believe [What we believe 1](https://landing.aicadium.ai/reorganise-your-team-in-the-agentic-era#what-we-believe) [The findings 2](https://landing.aicadium.ai/reorganise-your-team-in-the-agentic-era#measured) [Organisation change 3](https://landing.aicadium.ai/reorganise-your-team-in-the-agentic-era#change) [The new team 4](https://landing.aicadium.ai/reorganise-your-team-in-the-agentic-era#new-team) [Our experience 5](https://landing.aicadium.ai/reorganise-your-team-in-the-agentic-era#we-ran-this) [Run your own 6](https://landing.aicadium.ai/reorganise-your-team-in-the-agentic-era#run-your-own) [The series 7](https://landing.aicadium.ai/reorganise-your-team-in-the-agentic-era#the-series) For leaders deciding what AI changes # How to reorganise your teams for the **agentic era.** AI agents can now carry most of the production work of building a product: the coding, the testing, the drafts. The question for a leader is what to do with that: how to organise the work, staff the team, and keep a person answerable for every result. We rebuilt our own teams to find out, on our own internal projects, and measured what happened. This page is what we learned, and how to run the change in your own organisation.   What we believe ## **Three convictions** our own work forced on us. We expected the main lesson to be about speed. It turned out to be about structure, accountability, and adoption. CONVICTION I ### Speed is the easy part; transformation is key. Most companies buy the tools, hand one to every person, and keep the process unchanged. That's AI enabled: the same handoffs, each step somewhat faster. AI native means redesigning the process around the agents: fewer handoffs, teams organised around decisions, agents doing the production work in between.  CONVICTION II ### Accountability never leaves a person. However fast the agents produce, they don't own the result. The person who assigned the work does. Enterprise software carries consequences that reach beyond any one builder: the brand, the regulator, the customer. So every piece of work in our teams has a person's name on it, the checks before release stay as strict as ever, and the agents answer to a reviewer, never the other way around. CONVICTION III ### Adoption is the measure that will matter. The math tells you what's possible. It doesn't move a single person to work differently. For a company that already exists, the real transformation is getting your people to genuinely take up new ways of working, and that happens from the ground up, through the work itself. The number to watch isn't licences bought. It's how many of your people have actually changed how they work. Where the work moved ## In our trial runs, the speed gains were real, but the more interesting finding is where the bottleneck shifts. 5-7x Faster to a working prototype Prototyping compresses dramatically: from two to three people over a week, to one person over one to two days. Where the work was clear and bounded, AI took the execution weight, and one person ran the loop end-to-end.   2-3x Faster on a major refactor It is estimated that a full refactor of an existing production application is faster, when the team that owns the codebase drives the AI loop, with the right harnesses around the agents. Increase in new tools needed Reviewing AI-generated output takes more time now.  Skills and harnesses are employed on the front end during code generation.  Companies need to invest in specialised tools to sift through AI-generated code. How the Organisation Changes ## The team composition shifts to people, agents, and a set of guardrails. Some companies hand everyone AI and keep the org chart: the same functions, the same handoffs, everything slightly faster. The map below shows the other path. Tasks that used to require many handoffs among individuals with specialised mandates now shift to reimagined teams using agents, while the wider functions build the tools and maintain the hard lines. Read it as a process map, because that's the decision it represents.   None of these forces a smaller headcount. The same structure runs the other way: keep all your people and take on several times the work by running more of these small teams in parallel. Prototyping and experimentation become faster and cheaper. The alignment cost collapses: three people to align means three lines of agreement between them, where six functions meant fifteen. Add a person only when there is a new set of decisions to own.  the Migration ## Getting from how you operate today to running as an **AI native company.** The starting point is how you operate today. The destination is running as an AI native company. The five steps between them are what you implement to get across: they work in order, and each one pays off on its own. What AI native looks like on an ordinary day A person writes the context and requirements into the team brain once. A planning skill chops the plan into build tasks and files them in the same tracking system the company already uses. A coding agent picks them up and works in a sandbox, and the work comes back as a pull request with a person's name on the review. The whole loop runs on tools your teams already know.   The roles ## The team that emerges When AI carries the production work, narrow specialist roles collapse into broader ones.  01 "Is this worth building?" The Product Owner Decides what should exist, shows working demonstrations instead of writing documents about them, and stays responsible for the product after it ships. 02 "Will this hold up?" The Tech Lead Answers for the build. Used to spend the day writing code. Now spends it directing AI agents, reviewing what they produce, and designing the structure the whole system rests on. 03 "What do the agents work on tonight, and is their output good enough?" The AI Engineer The converging point for software engineers and data scientists. Masters the agentic development process: defines the work for the agents, sets up the harnesses they run in, and brings the technical judgment to know when their output can be trusted. 04 "Does everything we ship look and behave like us?" The Design Steward Instead of designing individual screens, builds the design standards and automated checks that let every team ship work that looks and feels like the company's products, even when AI produced it. 05 "What Guardrails and Automations" The Tools and Standards Beyond the responsibilities of a typical platform engineering team, the role shifts to enabling the organisation to embed best practices and guardrails for every function into the tools the company uses. We ran this on ourselves ## We experimented with **one/two people teams** for our AI transformation projects. Our AI Transformation program had two goals: grow our capability in broader enterprise AI transformation work, and change how we work ourselves. One of the simplest changes was having AI engineers own and manage their projects, with leadership supporting program management and external communications. In most cases, two people carried the work of project scoping, discovery, planning, and proof-of-concept delivery. What emerged was rapid upskilling across the company to become fluent in agentic AI capabilities. When we removed the barriers of management defining "what needs to be done", imagination and creativity became the only limiting factor, and everyone learned how to pitch their ideas better. Getting agents working on greenfield projects was easy; making it work in our brownfield projects is just taking off. A [2026 research paper](https://arxiv.org/pdf/2605.18461) describes a single staff engineer delivering a brownfield initiative scoped for a four-person squad in half the planned time, but that depends on a well-defined product boundary, a legible codebase, and a knowledge base that agents can reach within governance guardrails. The model becomes untenable when a decision exceeds what one engineer can hold, and it becomes a business risk when only one person understands how those decisions were made. Any company can buy the same tools. What decides the outcome is whether your people change how they work. ![we ran this ourselves](https://landing.aicadium.ai/hs-fs/hubfs/engineers-own-project-1x1.png?width=3000&height=3000&name=engineers-own-project-1x1.png "we ran this ourselves") A simple rule for what to hand over ## What your people keep, and what you hand to the agents. A person leads When any of these is true - The scope is vague. Nobody has decided precisely what the job is yet. - The context is messy. The requirements or the existing systems are hard to read, even for a person. - The stakes are high. A mistake would reach a customer, a regulator, or the brand before anyone caught it. → AI leads When all three hold - The task has clear edges. The AI knows exactly where the job starts and stops, and has a test it can run against its own work. - The requirements and systems are readable. The AI can follow what exists and what's being asked. - Mistakes are cheap. An error stays bounded, in a sandbox or a pull request, and never reaches production on its own. Run your own ## Six weeks will teach you more than any presentation.  How to run yours ### Start small and stay accountable - 1**Pick one well-defined part of your business.**Use the rule above: clear edges, readable requirements, mistakes that are cheap to catch. - 2**Give one person real ownership of it.**The result carries their name, including everything the AI produces. Keep approvals lean: one owner, at most two informed reviewers. - 3**Run it properly for six weeks.**Normal systems, normal review standards, no special treatment. First two weeks produce speed and expose quality gaps. The next weeks build the checks that close them. The final weeks ship. When output falls short, fix the check that let it through. - 4**Measure adoption alongside output.**The lasting question is whether the new way of working holds after the six weeks end. ![](https://landing.aicadium.ai/hubfs/placeholder.png) The series ## An **ongoing programme** of research, frameworks, and field findings. ![Search isn't being optimised any more. It's being answered.](https://landing.aicadium.ai/hubfs/placeholder.png) Anchor essay · Vol 01 ### Search isn't being optimised any more. It's being answered. The full briefing: the shift, the framework, the field evidence, and the predictions. Download → ![What SEO leaders are saying about AI visibility](https://landing.aicadium.ai/hs-fs/hubfs/placeholder.png?width=400&height=200&name=placeholder.png) Field research ### What SEO leaders are saying about AI visibility Synthesised findings from our expert interviews with senior practitioners — including the key thesis that shaped this framework. Read the findings → ![How we score each of the five pillars](https://landing.aicadium.ai/hs-fs/hubfs/placeholder.png?width=400&height=200&name=placeholder.png) Methodology note ### How we score each of the five pillars The formulas, weights, and edge cases. Built for the reader who wants to interrogate the numbers, not just read the headline score. Open the methodology → ![A 20-minute briefing for non-technical leaders](https://landing.aicadium.ai/hs-fs/hubfs/placeholder.png?width=400&height=200&name=placeholder.png) Boardroom briefing ### A 20-minute briefing for non-technical leaders The thesis stripped to its boardroom essentials — what to know, what to ask, what to fund — without the practitioner-level detail. Open the briefing → Follow AI Projects ### Ideas like this shape how we work at Aicadium. Get updates about our latest AI Transformation projects. AICADIUM SINGAPORE PTE. LTD. · © 2026 Aicadium [Privacy Policy](https://landing.aicadium.ai/privacy?hsLang=en) | [Terms of Use](https://landing.aicadium.ai/terms?hsLang=en) ```json { "@context" : "https://schema.org", "@type" : "VideoObject", "contentUrl" : "https://4788637.fs1.hubspotusercontent-na1.net/hubfs/4788637/video_assets/220237723209/inherited/web_optimized.mp4", "dateModified" : "2026-08-25T04:20:12.998Z", "duration" : "PT33S", "height" : 1724, "name" : "Squad of One - Convergence video 90s - updated 25 aug", "thumbnailUrl" : "https://4788637.fs1.hubspotusercontent-na1.net/hubfs/4788637/Squad%20of%20One%20-%20Convergence%20video%2090s%20-%20updated%2025%20aug.mp4/medium.jpg", "uploadDate" : "2026-08-25T04:19:31.518Z", "width" : 2384 } ``` ```json { "@context" : "https://schema.org", "@type" : "VideoObject", "contentUrl" : "https://4788637.fs1.hubspotusercontent-na1.net/hubfs/4788637/video_assets/220238078305/inherited/web_optimized.mp4", "dateModified" : "2026-08-25T06:15:05.283Z", "duration" : "PT34S", "height" : 836, "name" : "migration-path-v21-30s-hold", "thumbnailUrl" : "https://4788637.fs1.hubspotusercontent-na1.net/hubfs/4788637/Squad%20of%20One-migration%20path%20-25Aug.mp4/medium.jpg", "uploadDate" : "2026-08-25T06:14:39.117Z", "width" : 2384 } ```