惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

S
SegmentFault 最新的问题
博客园 - 三生石上(FineUI控件)
爱范儿
爱范儿
博客园 - 聂微东
V
Visual Studio Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
M
MIT News - Artificial intelligence
The GitHub Blog
The GitHub Blog
Recent Announcements
Recent Announcements
有赞技术团队
有赞技术团队
L
LangChain Blog
I
InfoQ
T
Tailwind CSS Blog
博客园 - 【当耐特】
V
V2EX
博客园_首页
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
GbyAI
GbyAI
Vercel News
Vercel News
雷峰网
雷峰网
量子位
A
About on SuperTechFans
Martin Fowler
Martin Fowler
H
Help Net Security

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
If your AI initiative is pending for 6 months, the bottle...
Linhua Zhong · 2026-05-21 · via DEV Community

Linhua Zhong

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.