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

推荐订阅源

H
Help Net Security
G
Google Developers Blog
aimingoo的专栏
aimingoo的专栏
博客园 - 聂微东
酷 壳 – CoolShell
酷 壳 – CoolShell
小众软件
小众软件
Stack Overflow Blog
Stack Overflow Blog
美团技术团队
博客园_首页
T
Tailwind CSS Blog
博客园 - 三生石上(FineUI控件)
B
Blog
D
DataBreaches.Net
腾讯CDC
C
Check Point Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
U
Unit 42
月光博客
月光博客
V
V2EX
Vercel News
Vercel News
T
The Blog of Author Tim Ferriss
The Cloudflare Blog
博客园 - 叶小钗
Y
Y Combinator Blog

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
AI isn't a software upgrade. It's an organizational redes...
Dimitris Kyrkos · 2026-06-22 · via DEV Community

Dimitris Kyrkos

The framing most companies get wrong

There's a pattern I keep seeing in how companies talk about adopting AI. They treat it like upgrading a tool. Swap in the new thing, keep everything else the same, move faster.

That framing misses what actually happens.

What changes when AI enters a workflow

Once AI starts generating code, drafting decisions, or automating steps that humans used to own, four things shift simultaneously.

Decision speed changes. AI produces output in seconds. But the review, approval, and validation structures around that output were designed for human-speed delivery. You now have a team that can generate a week's worth of code in a day, running into a review process that was built to handle a week's worth of code in a week. Something has to give, and usually what gives is review quality.

Accountability gets blurry. When a human writes code, you know who made every decision. When AI generates code and a human approves it, accountability lives in a grey zone. Who owns the architectural choice the AI made? Who's responsible when a generated function introduces a security vulnerability? Most orgs haven't answered these questions explicitly, so they get answered implicitly by whoever is on call when something breaks.

Escalation paths break. Traditional escalation assumes a human-made decision that can be explained and traced. AI-generated output often can't be traced the same way. "Why was it built this way?" gets answered with "that's what the AI produced, and it looked right." That's not an escalation path. That's a dead end.

Operational expectations shift faster than operations do. Leadership sees the speed of generation and expects the speed of delivery to match. But delivery includes review, testing, integration, deployment, and monitoring. None of those got faster just because the first step did. The expectation gap creates pressure that compresses everything downstream.

Why this creates tension

The tension isn't about the technology. The technology works. The tension is that AI evolves faster than the organizational structures around it.

Teams adopt AI tools in weeks. Changing how decisions get made, who's accountable for what, how reviews work, and what "done" means takes months. In that gap, you get teams generating more output than their processes can absorb, accountability questions that nobody has answered, and escalation paths that quietly stopped working.

Most of the AI adoption failures I've watched weren't technical failures. They were alignment failures. The tool changed. The org didn't.

The alignment problem nobody talks about

The challenge for most companies is no longer access to AI. Everyone has access. The challenge is alignment.

  • Aligning the speed of AI output with the capacity of the review process.

  • Aligning accountability structures to account for AI-generated decisions.

  • Aligning operational expectations with the reality that generation is only one step in a much longer delivery chain.

The teams that get this right don't just adopt AI tools. They redesign how work flows through the organization to account for what those tools actually change. That's not a software upgrade. That's an organizational redesign.

Has your company actually changed its processes since adopting AI tools, or did the tools change and everything else stayed the same?