DEV Community

Linhua Zhong
Linhua Zhong

Posted on

If your AI initiative is pending for 6 months, the bottleneck is probably not technology

If your AI initiative has been 'pending' for 6 months, the bottleneck is probably not technology. I've seen this pattern repeatedly across companies in both Asia and the US. The tools are accessible, the talent is available, and the use cases are clear. Yet nothing moves. The real constraints are organizational, not technical.

The first structural bottleneck I encounter is unclear data ownership. Who owns the customer database? The sales pipeline? The production logs? Without clear ownership, data remains trapped in departmental silos. Engineering teams can't access what they need, and business leaders won't prioritize cleanup. The tactical fix: assign a data custodian for each critical dataset this week. This isn't a full-time role—just a point person who can answer "Who can approve access to this data?" and "What's the current state of this dataset?" Make it someone who uses the data daily, not a C-level executive.

The second bottleneck is the absence of an operations sponsor. Many AI initiatives die in the "pilot purgatory" because no one is accountable for production deployment. The data science team builds something, the business leaders express interest, but no one owns the operational handoff. The tactical fix: identify an operations sponsor who will attend weekly implementation meetings. This person should have budget authority and decision-making power, not just advisory influence. Their first task is to define what "done" looks like—specific milestones with clear completion criteria.

The third bottleneck is the lack of success metrics. Without measurable outcomes, AI initiatives become abstract exercises. Teams build models without knowing what constitutes success, leading to endless revisions and scope creep. The tactical fix: define a single, measurable success metric this week. Not "improve customer experience" but "reduce average handle time by 15% for Tier 1 support tickets." Not "optimize inventory" but "reduce stockouts for top 10 SKUs by 20%." The metric should be business-focused, not technical.

Technology is rarely the constraint. I've worked with companies using open-source tools to solve problems that others couldn't address with enterprise solutions. The difference wasn't the tools—it was the organizational clarity. When data ownership is clear, when someone owns operations, and when success is measured, AI initiatives move forward regardless of the technology stack.

The tactical fixes I've outlined—assigning data custodians, identifying operations sponsors, defining success metrics—can be implemented by any non-technical leader this week. They don't require technical expertise or budget approval. They require clarity and accountability.

What's the single organizational constraint holding back your AI initiative right now?


This piece is from our notes on helping SMBs (10-100 people) build their first in-house AI teams. If your team is exploring this — quick feedback and questions welcome in the comments.

Top comments (0)