u/Dry_Broccoli_7526

▲ 2 r/EngineeringManagers+1 crossposts

I’ve been thinking about something fairly simple based on what I’ve seen across a few orgs working on AI Enablement.

There’s usually a lot of focus on better models, better tooling, and hiring stronger engineers. That all makes sense.

In practice, those things rarely determine whether anything actually ships or changes how the business runs. Prioritisation tends to matter more. If it’s weak, even strong models don’t lead very far.

Every new idea has to compete with work already in progress, teams that are already allocated, and priorities that have already been agreed on. The question shifts from “Is this a good idea?” to “Is this worth replacing what we’re already doing?”

Most of the time, the answer is no. Changing direction is expensive, so teams stick with existing plans and keep moving.

Curious if others have seen the same thing, or if this has just been specific to where I’ve worked.

I wrote an in depth post about this as well.

u/Dry_Broccoli_7526 — 9 days ago

I’ve been noticing a pattern across teams trying to use AI internally, and I’m trying to sanity check if others are seeing the same.

In most cases, the technical side is… fine.

Models work and outputs are usually good enough. You can demo something useful pretty quickly.

But when you look at what actually changes:

  • decisions don’t consistently follow from those outputs
  • workflows don’t really change
  • outcomes don’t improve in a meaningful way

So you end up with something that works in isolation, but doesn’t translate into impact.

What it feels like is that the system stops at “producing answers,” and everything after that (decisions → actions → outcomes) is kind of undefined or left to existing processes.

I’ve started thinking of this as an “incomplete value chain” — where the front half (data, model, output) is strong enough, but the back half isn’t really designed.

Curious if this resonates with others working on AI in production:

  • Is this what you’re seeing?
  • Where does it actually break in your org?
  • Is it mostly a workflow issue, or something deeper (ownership, incentives, etc.)?

I wrote a slightly more structured version of this here if helpful:

u/Dry_Broccoli_7526 — 13 days ago