Sonatafy CEO Steve Taplin has a new piece out with the Forbes Technology Council, and it starts with a lesson he learned the hard way.
"One lesson keeps showing up: companies are usually quicker to add people, tools and activity than to clarify who owns the result," he writes.
Generative AI, he argues, is creating a new version of that same problem. Faster code does not fix unclear ownership. It just makes the gap harder to see.
Read the full article here: Read the full column on Forbes.com
Busy Is Not the Same as Delivering
Steve doesn't tell this story from the outside. Inside Sonatafy, he faced what looked like a capacity problem. The backlog was full, tickets were moving and releases were going out. The obvious answer was more engineers.
Before approving the hires, he asked harder questions. What was each team responsible for improving? Who owned that result end to end? How would anyone know if a release made things better?
The answers were far less clear than the activity suggested. "Plenty of people are doing the work, but no one person clearly owns the outcome all the way through," he writes.
That is the Ownership Gap, one of the diagnostic frameworks we use at Sonatafy. In plain terms: nobody owns the date. For technical teams, it means accountability dissolves at handoffs.
The fix inside Sonatafy was not headcount. It was opening up infrastructure so more teams could build, test and deploy on their own, and tightening the handoff from product to engineering so work arrived closer to ready. Only after that did adding people make sense.
AI Moves the Bottleneck
Executives watching developers produce code faster are right to ask what that means for team size. Steve grants that AI creates real leverage on repetitive work. But code production is only one part of software delivery.
"If developers can produce code faster but only a few people can approve environments or deployments, the bottleneck has not disappeared. It has just moved."
Someone still has to decide whether a problem is worth solving. Someone still has to own reliability, security and maintenance once the software is in production. AI does not answer those questions. People with clear ownership do.
Three Questions Before You Add Capacity
Steve's advice is to fix the system first. Look at whether teams can build, test and deploy without waiting on the same few people, and whether each step in the process still earns its place. Then ask three questions.
- What are we actually trying to improve? Teams tend to start with the solution: three more engineers, a new AI tool, a new platform. Start with the result the business wants and work backward.
- Who owns that result? "I want one person whose name is on it, not five people who share it." Shared responsibility sounds collaborative until something slips.
- How will we know whether it worked? Pick the measure before implementation. Cycle time, defect rates, uptime, cost or retention all work. What matters is agreeing in advance and naming who reviews it.
Ask the Same of Any Partner
Steve applies the same test to outside software partners. Skip the hourly rates and headcount questions. Ask whether they will examine how your teams work before recommending people. Ask who will own the outcome. Ask how they will show the work improved something in production.
"If the answer comes back mainly in hours, resources and tickets, they are still selling capacity."
We hold ourselves to that standard. Our answer is Your Team. Our Team. One Scoreboard. We put our own delivery performance on the same board as the client's, measured against the outcomes we recommended. Sometimes the right recommendation is to hire us. Sometimes it is to adjust internally, or to do nothing yet.
Read the Full Article
Steve closes on the point that matters most for any leader weighing AI investments: "The companies that figure that out will get much more from AI than the ones that mainly use it to produce more code."
Read the full piece on Forbes: AI Won't Close The Ownership Gap In Software Delivery (Forbes Technology Council, October 23, 2026).
If your teams are busy and the results are not showing up, a good first step is a complimentary Software Delivery Snapshot. It is a 30 minute executive session with a senior US based Sonatafy leader, followed by a one page written read within two business days.
About Steve Taplin and Sonatafy
Steve Taplin is CEO and founder of Sonatafy Technology. He has founded 30+ companies over 25+ years, published 248+ articles in Forbes, Entrepreneur, CIO and Inc., and hosts Software Leaders Uncensored, now at 215+ episodes.
Sonatafy finds what's really holding your product and engineering teams back, then brings the velocity, efficiency, and visibility to get your software to market faster. The company is headquartered in Scottsdale, Arizona, with senior engineers across the US and Latin America.

