Fewer People, Less Process: How AI Changes the Way Teams Ship
Linear says issue tracking is dead. They are half right.
Linear just declared issue tracking dead. Their CEO Karri Saarinen: "Complexity started to look like sophistication. Overhead kept growing, and the process became the work." They launched an AI agent that generates issues, triages automatically, and will soon write code. 75% of their enterprise workspaces already have coding agents installed. Agents now author nearly 25% of new issues.
Their pitch is "context over process." I think Saarinen is right about the diagnosis. But he's solving the wrong layer of the problem.
Process became the product a long time ago
If you've used Jira or Azure DevOps at a company with more than 50 engineers, you know what he's talking about. Jira's the one everyone loves to hate, but Azure DevOps is the quiet offender. Same disease in a Microsoft suit: work items linked to test plans linked to boards nobody opens, welded to your CI/CD so the process overhead becomes literally impossible to remove without breaking your builds.
Theo Browne talked about this — his Jira at Twitch took over two minutes to load. That's not a performance bug. That's what happens when every stakeholder gets to add a field.
I've lived both sides of this. For a stretch of my career I was a Jira admin at a 100-person company. It consumed about half my day. Not building. Not shipping. Tweaking workflows, fixing broken automations, cleaning up schemes that had drifted into nonsense. Half my working hours maintaining a tool whose purpose was supposed to be helping other people work. I also spent time as a product owner on a large enterprise team, basically living in Azure DevOps. Grooming backlogs, writing acceptance criteria, sitting in sprint ceremonies, managing boards. The work was real, but it wasn't building. It was managing the process around building.
At my core I'm a builder. I went back to building. Those process management roles no longer provide value in the ways we need to work today. The future belongs to builders, not process managers.
The Agile Manifesto said "working software over comprehensive documentation" in 2001. Then an industry of consultants, certification bodies, and framework vendors built a multi-billion-dollar empire around the ceremony of being agile. SAFe. Scrum certifications. "Agile transformations" led by people who haven't shipped code in a decade. Microsoft built an entire product around it. Atlassian built an entire company around it. The tools designed to make teams agile became the heaviest things in the building.
The agile industrial complex is real. The principles were never the problem. The industry that grew around them was.
What AI actually changes
Theo's approach at Twitch was to skip the spec and build a rough prototype to discover requirements. Before AI, that worked if you had the right engineer. But in the AI era, I think you actually need the spec more, not less. Not the 20-page Google Doc. A markdown file produced by the subject matter experts. What you're building, who it's for, what done looks like. Enough context to hand an agent and get a useful first pass.
You can't "skip the spec" when your builder is an LLM. The prompt IS the spec. The question is whether you write a thoughtful one that gets a working prototype on the first pass, or wing it and spend three hours course-correcting.
Write the spec, prompt the agent, get a prototype, refine. That's the loop. The cost of a first pass is approaching zero. When it costs an afternoon and a good prompt, you iterate faster than any sprint cycle could keep up with.
A new type of team is emerging
A solo founder with AI agents can ship what used to take 15 engineers. A team of three can operate at the scale of thirty. The leverage is compounding fast, and it changes what tools you need.
Jira and Azure DevOps exist because large teams need coordination overhead. Tickets, workflows, sprint boards, estimation rituals — all coordination tax. The cost of having a lot of humans in the same codebase. But the teams forming now don't look like that. They don't need sprint boards because there's no sprint. They don't need estimation because one person holds the whole context.
Smaller doesn't mean solo, though. There are unicorns who can design, code, manage product, and test. They exist. But they're rare, and even the best of them usually can't match the quality a small team of specialists produces. The unicorn gets you to market. The team gets you to quality.
The roles haven't gone away. You still need a designer's eye, an engineer's instinct for what breaks at scale, a PM who manages the project and works with clients, a QA engineer who thinks adversarially. What changes is headcount and throughput. A designer with AI explores ten directions in the time it used to take to mock up two. An engineer ships in a day what used to take a sprint. AI is a productivity accelerator, not a role eliminator. A team of five with the right specializations can operate like fifty used to.
That's the market Linear is actually chasing. Not better issue tracking for big teams. Lighter tools for smaller teams that punch above their weight.
The business model is breaking too
This isn't just a team structure problem. It's a pricing problem.
Software projects used to be measured in developer hours. Entire sales organizations were built around scoping engagements at X hours times Y rate. That math is collapsing. The honest unit of work is shifting from hours to tokens, and while nobody has a clean way to estimate token cost for a project yet, the direction is obvious: it's a lot less. That's all that matters.
Software can't be sold at the prices it was even two years ago. A project that a consultancy would have quoted at six months and half a million dollars can now be built by a small team in weeks for a fraction of the cost. The buyers are figuring this out. The sellers, a lot of them, haven't.
Large firms that only chase big deals are going to get their lunch taken by smaller indie dev shops that move faster, charge less, and ship better work with leaner teams. The overhead that justified premium pricing, the project managers, the Jira admins, the sprint ceremonies, the 30-person delivery teams, none of that scales the way it used to. It's just cost now.
Offshoring is facing the same math. The whole model was built on labor cost arbitrage: cheaper hourly rates in other markets. But when the unit of work shifts from hours to tokens, that gap shrinks fast. Tokens cost the same no matter where the developer sits. Meanwhile, the coordination costs haven't changed. Time zone gaps, communication overhead, context getting lost across languages and cultures, losing direct control over the taste and style of the output, the quality variance that comes from managing work at a distance. Those tradeoffs used to be worth it because the savings were significant. When a small local team with AI tools can compete on price, the economic case for offshoring gets a lot harder to make.
Sales teams are struggling and a lot of them don't understand why. The pipeline looks the same. The pitch decks look the same. But the deals aren't closing because the buyers can see the math changing. The teams that adapt, that price for the new reality and sell speed and quality instead of headcount, will win. The ones still quoting based on 2023 economics are going to have a rough year.
What AI doesn't change
You still don't know what your users want. Inflectra put it well: "If code shows up faster than requirements learning, you can ship the wrong thing even sooner."
AI makes shipping faster. It does not make learning faster. Skip the feedback loops and you just automate failure. The Agile principle of "optimize for learning" matters more now than it did in 2001. Short feedback loops aren't optional when your agent can ship a feature before lunch.
What actually dies is the handoff model. Not the roles, but the assembly line where each role produces an artifact for the next to consume. When your team is small enough that everyone shares context directly, you don't need the proxy. The teams that win will be the ones with taste — who know what's worth building and can spot "this is wrong" before users have to tell them.
When building is cheap, judgment becomes the bottleneck.
The manifesto was right
Issue tracking isn't dead. Bad issue tracking deserved to die. The bloated Jira instances, the Azure DevOps boards nobody opens, the velocity charts that measured activity instead of outcomes.
What survives is what the Agile Manifesto said 25 years ago. Build working software. Collaborate with your users. Respond to change. Value people over process. We buried those principles under dashboards and certifications and two-week rituals. AI is digging them back out.
The future isn't post-Agile. It's Agile without the industry that grew around it.
Build something. Learn from it. Do it again.