[al_borland]

I work in a large enterprise. On one hand, we’re being told we should think of ways to use AI more. On the other hand, to even start (beyond just using Copilot to develop what I’m already working on), I need to have an idea and sell it to some AI board to get their blessing. At that point, I will have a microscope on me, tracking everything, to watch if this wild experiment is a success or failure. No thanks.

If they really want me to try something new, they will give me the space to try things where I am free to fail quietly and privately, pivot, and continue trying things. Asking for ship dates on day one is no way to operate projects with so many unknown unknowns. No one wants to learn and fail with an audience.

[harran]

That’s hard with AI, because early efforts are exploratory by nature. You don’t really know the shape of the value until you’ve iterated. If experimentation immediately becomes a public performance review, the safest move is not to experiment. I think this is a big part of why so many enterprise initiatives stall. The org says it wants discovery, but the governance model assumes delivery. Your point about needing space to fail quietly is important.

[watwut]

That is kind of weird take, because whole my life, people WANTED to be part of initiatives like this and were jealous of people selected for initiatives like that.

[bravetraveler]

Some people sit in front of the classroom because they want, others because they must. Many more choose elsewhere. Reasoning is their own.

I don't find it strange, having routinely tanked my own chances/social credit for initiatives... because, like the parent, I don't want a target on my back. Somebody above thinks I do, though, apparently. Experience isn't conditioned on... that experience, if that makes sense. Unpleasant to say the least.

Where you see jealousy, which is a strange thing to invite, I see fear of missing out/rat-racing. Pass. Plenty of motivators and opportunity without the charade. Or, to put it charitably, noise/competition/advertising.

All to say, the initiatives are usually loaded with expectations, reasonable and not. Tread carefully.

[watwut]

There is difference between "this is why I do not want to be part of that" and "this is why the institution as such did not found a way to do it". The some peoples unwillingness to do that is not that much relevant, unless the company is in the "all qualified people are avoiding that task" situation.

> Where you see jealousy, which is a strange thing to invite,

Any desirable position invites slight jealousy. It is no different then when you have low pressure project, project that uses cool language, project with the good manager. I used the word in that sense, in the the "horrible they are going to dislike me" sense.

> I see fear of missing out/rat-racing. Pass. Plenty of motivators and opportunity without the charade.

This seems oddly out of place to me? These initiatives usually give you more freedom and "customer wants it now" kind of pressure.

[bravetraveler]

> There is difference between "this is why I do not want to be part of that" and "this is why the institution as such did not found a way to do it". The some peoples unwillingness to do that is not that much relevant, unless the company is in the "all qualified people are avoiding that task" situation.

Organizations are large, they gave us gifts like the Peter Principle. I'm sure that situation and plenty others exist. I provided my experience/anecdote, showing yours might not be encompassing. Apologies, meant no detraction. Point being, the initiatives are often overrated and rather easy to ignore. By no means am I saying everyone ignores them [or should].

> Any desirable position invites slight jealousy. It is no different then when you have low pressure project, project that uses cool language, project with the good manager. I used the word in that sense, in the the "horrible they are going to dislike me" sense.

Of course, that's why I call it a rat race. A group running towards the same things... to be disappointed, in my experience. The freedom is welcome, the 'customer [or peer] wants it now' pressure can be left behind. None of this requires going out of your way, however. Perhaps that is why organizations may struggle, regardless, I'm thankful for it.

edit: format and phrasing

[al_borland]

I found things go much better for me when I can work on a project on my own, then if it works well, show it off and let it go up the chain. I can then focus on the work, pivot as needed, or scrap the idea if it didn’t pan out.

A co-worker of mine had an idea recently (not AI related). He told our manager and sr director about it. I think now it’s gone up to the VP level. The whole project hinges on a very specific thing working that some other team needs to do with a vendor tool and is having a lot of trouble actually getting right. Meanwhile, he’s now been asked to make multiple presentations to justify and defend it, and there are 2 or 3 separate project managers trying to track it, each with their own set of weekly meetings, tracking spreadsheet, and other such things. All those PMs are also asking for timelines and dates for a lot of unknown unknowns. All our time is being engulfed by ceremony and bureaucracy, and we don’t even know if it will work yet. If that one piece doesn’t pan out, it will be a very public failure and we’ll then be expected to come up with some other option. My part of it also involves a vendor tool. When I POC’d my part, it worked fine. When I went to set it up with some real data later, the tool isn’t working, despite the POC still running and updating fine. I can’t even replicate the POC again, but it might randomly work next week. There are bugs in systems I don’t control. It’s not a total deal breaker, but it’s a risk and may require a pivot that would fundamentally change how parts of it work that have already been presented.

Had he waited a bit to see if it will actually work, it would be no big deal and wouldn’t have cost us much time. Instead, if the vendor tool falls through, or we need to pivot to work around a bug, we now need to show that to all these people, explain why it didn’t work, and get beat up about it. We also need to pretend to be busy with this and make progress on it, when we’re in a holding pattern waiting for our dependency that may or may not work. We also found out this week that if someone on that other team makes a small mistake, it wipes out everything and the house of cards crumbles. I personally think it’s a big enough risk to scrap the whole idea and find something else, but it’s too late for that now.

Of course, I tend to like to work in the background. I want the organization to function better and more smoothly. I’m not just seeking glory. I’ve still ended up being the one our team tapped when the CIO came knocking for some big project he wanted to see done quickly, despite trying to stay out of it. I don’t think anyone was jealous of me, they were all happy that they didn’t have to deal with all the uncertainty. The only good thing about that was because it was the CIO asking, it was very easy to ignore everything else and I was able to knock it out pretty fast.

Maybe you’ve worked in companies with less bureaucracy or cultures that can handle these types of projects better. For us, it feels like no good deed goes unpunished, so it’s just easier to keep your mouth shut and focus on the work until there is something actually worth showing. That is especially true for these grass roots projects vs big corporate sponsored projects that are happening no matter what.