Remix.run Logo
▲ adriand 3 hours ago

> The real question is how many people haven't figured out how to use AI to make their job easier/more productive.

I think the answer, to a reasonable approximation, is “everyone”. Outside software engineering most people aren’t using it for anything useful, and I keep encountering technical people including programmers who don’t use it either, which never fails to surprise me.

One of my projects is a transportation management system (TMS) and of course I have added a lot of features to it including a very capable chat-based UI that can automate a lot of tedious data entry and other tasks for dispatchers and accounting and so on. It gets used but really not very much. I’m starting to realize that I’ve probably taken updates as far as they can go in terms of the ability of people to absorb change. Most people just carry on doing things the way they always have.

We had one person on the admin team who started using Cowork to automate all kinds of stuff. She loved it. Then she left. It hasn’t caught on with anyone else.

This is not to say that things won’t change but I think it will take a while.

▲mariofdistrust 3 hours ago | parent | next [-]

my brother uses it to do ocr on his books but, lately, claude has been refusing because of copyright or whatever so i've had to do it for him (using ai, yes, but not anthropic's)

▲scottyah 3 hours ago | parent | prev | next [-]

I know firefighters and machinists heavily using it, the only places I see slower adoption is purely because of bad leadership- exclusivity contracts with certain providers or just plain fear.

▲calebkaiser 3 hours ago | parent | prev [-]

I think this dynamic is underappreciated. Another thing I see in working with different companies (consulting) and discussing with colleagues at different jobs is that we as humans tend to do a pretty bad job of modeling business outcomes and the dynamics that govern them. There are lots of outcomes where you can identify one contributing role, increase the productivity for that role by a significant factor, and still ultimately not move the needle much, because the constraints span multiple functions.

As an example outside of software engineering, a lot of people in marketing roles have found agents to be incredibly useful for particular tasks. I've talked to multiple people who wouldn't standardly be classified as "technical hires" who are using Claude to manage things like digital advertising. It's valuable here because managing campaigns on a platform like Google or LinkedIn involves a ton of granular tweaking and analysis. Every performance marketer makes tradeoffs around what they're realistically able to spend time doing, and what makes the biggest impact. So if you have 250 campaigns that you manage solo, you likely don't have the time to really manually optimize the bidding and budget for each campaign every couple of days based on new data. You can only try so many new angles, because creating new media is time consuming. You don't have time to construct custom experiences on-page for every particular campaign. There's a whole industry of tools that turn a tidy profit automating parts of this for this reason. And agents are really good at it, because a lot of it is just applying the same analysis over and over again.

But for a lot of startups, increasing traffic from ads 20% while decreasing spend is a good outcome, but it doesn't actually turn into revenue. The product itself might just be limited, and already being discovered by the narrow segment of potential users who find it valuable enough to pay. Or the sales process might be kind of busted, meaning the team will really only close a certain volume of new deals in a given month, no matter how much inbound they have. Or some combination of all of the above.

If it's just one marketer using an agent to optimize their advertising, there's not a lot they can do about the other constraints. And so what you end up with is one employee who feels really productive and sings the praises of Claude, but not a meaningful lift in the higher level outcomes you care about, and the analysis gets messy. In an ideal world, everyone realizes where the other bottlenecks are, but that's a genuinely hard thing to do and people have complicating incentives.

I don't think this is a particularly new problem. It feels identical to any other situation where a department asks for a tool, loves it, and it doesn't really make a difference to the bottom line or make anyone else's life easier in noticeable ways.